Skip to content

gh-148535: Don't use gcc -fprofile-update=atomic flag on i686#148554

Open
vstinner wants to merge 1 commit intopython:mainfrom
vstinner:i686_profile_atomic
Open

gh-148535: Don't use gcc -fprofile-update=atomic flag on i686#148554
vstinner wants to merge 1 commit intopython:mainfrom
vstinner:i686_profile_atomic

Conversation

@vstinner
Copy link
Copy Markdown
Member

@vstinner vstinner commented Apr 14, 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.

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.
],[ac_cv_i686=no],[ac_cv_i686=yes])
])

PGO_PROF_GEN_FLAG="-fprofile-generate"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to do PGO_PROF_GEN_FLAG="PGO_PROF_GEN_FLAG -fprofile-generate" (i forgot the proper substitution) or is this something that won't be set by user?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants