Skip to content

gh-124948: Reject explicit Cortex-A53 workaround flags with BOLT - #160337

Merged
corona10 merged 1 commit into
python:mainfrom
zanieb:bolt-cortex-a53-guard
Oct 22, 2026
Merged

corona10 merged 1 commit into
python:mainfrom
zanieb:bolt-cortex-a53-guard

Conversation

@zanieb

@zanieb zanieb commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Recent BOLT versions reject AArch64 binaries containing Cortex-A53 erratum 843419 workaround veneers by default. Report an earlier error from configure --enable-bolt when build flags explicitly request the workaround. The check only inspects explicit flags because recent BOLT already diagnoses veneers produced by compiler defaults.

Document that BOLT output must not run on affected processors and how to override GCC's default workaround with LDFLAGS_NODIST="-mno-fix-cortex-a53-843419" for builds confined to unaffected hardware. Explicit enabling flags must be removed separately.

@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 cpython-previews | 🛠️ Build #35336066 | 📁 Comparing edff69c against main (d6b77c8)

  🔍 Preview build  

2 files changed
± using/configure.html
± whatsnew/changelog.html

@corona10 corona10 left a comment

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.

lgtm

@corona10 corona10 changed the title Reject explicit Cortex-A53 workaround flags with BOLT gh-124948: Reject explicit Cortex-A53 workaround flags with BOLT Oct 22, 2026
@zanieb
zanieb marked this pull request as ready for review October 22, 2026 21:37

@itamaro itamaro left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

lgtm, but why skip issue?

@corona10
corona10 enabled auto-merge (squash) October 22, 2026 21:50
@corona10

Copy link
Copy Markdown
Member

@itamaro I think that user (who build CPython) should know the change, because it will affects all ARM users if the distribution pass the specific flag.

@corona10

Copy link
Copy Markdown
Member

lgtm, but why skip issue?

Oh I thought that skip news lol

@corona10 corona10 linked an issue Oct 22, 2026 that may be closed by this pull request
@corona10
corona10 merged commit c6661bd into python:main Oct 22, 2026
65 checks passed
@itamaro

itamaro commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

does this need backports?

@zanieb

zanieb commented Oct 22, 2026

Copy link
Copy Markdown
Contributor Author

Sorry why did we link this to #124948 ? That doesn't seem right?

@zanieb

zanieb commented Oct 22, 2026

Copy link
Copy Markdown
Contributor Author

I skipped the issue because this is just an informational convenience, BOLT will already fail if you are using this flag, this just makes the error a bit friendly in CPython's build system.

@zanieb

zanieb commented Oct 22, 2026

Copy link
Copy Markdown
Contributor Author

I don't think this needs backport, since it's not fixing a bug as described above.

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.

[BOLT] [3.12] Python 3.12.7 --enable bolt option not working

3 participants