]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.14] gh-148535: Don't use gcc -fprofile-update=atomic flag on i686 (GH-148554)...
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Thu, 16 Apr 2026 17:46:06 +0000 (19:46 +0200)
committerGitHub <noreply@github.com>
Thu, 16 Apr 2026 17:46:06 +0000 (17:46 +0000)
commit2fdccb3f88603cb72d311ca304ab7fcf9df12d00
tree1f1c6a054414cf6ad2bf238b56c6cc227fcc484e
parent1c9de6bbaab9d909a5f0de7fe6eb19dcce00b305
[3.14] gh-148535: Don't use gcc -fprofile-update=atomic flag on i686 (GH-148554) (#148655)

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

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 2faceeec5c0fb06498a9654d429180ac4610c65a)

Co-authored-by: Victor Stinner <vstinner@python.org>
Misc/NEWS.d/next/Build/2026-04-14-15-20-29.gh-issue-148535.JjKiaa.rst [new file with mode: 0644]
configure
configure.ac