Skip to content

[3.13] gh-148535: Don't use gcc -fprofile-update=atomic flag on i686 (#148554)#148656

Merged
vstinner merged 1 commit intopython:3.13from
vstinner:i686_profile_atomic13
Apr 16, 2026
Merged

[3.13] gh-148535: Don't use gcc -fprofile-update=atomic flag on i686 (#148554)#148656
vstinner merged 1 commit intopython:3.13from
vstinner:i686_profile_atomic13

Conversation

@vstinner
Copy link
Copy Markdown
Member

@vstinner vstinner commented Apr 16, 2026

The -fprofile-update=atomic flag was added to fix a random GCC internal error on PGO build (gh-145801) caused by corruption of profile data (.gcda files). The problem is that it makes the PGO build way slower (up to 47x slower) on i686. Since the GCC internal error was not seen on i686 so far, don't use -fprofile-update=atomic on i686.

(cherry picked from commit 2faceee)

…ython#148554)

The -fprofile-update=atomic flag was added to fix a random GCC
internal error on PGO build (pythongh-145801) caused by corruption of
profile data (.gcda files). The problem is that it makes the PGO
build way slower (up to 47x slower) on i686. Since the GCC internal
error was not seen on i686 so far, don't use -fprofile-update=atomic
on i686.

(cherry picked from commit 2faceee)
@vstinner vstinner enabled auto-merge (squash) April 16, 2026 17:23
@vstinner vstinner merged commit 53e0725 into python:3.13 Apr 16, 2026
38 of 41 checks passed
@vstinner vstinner deleted the i686_profile_atomic13 branch April 16, 2026 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant