Conversation
joshuarli
marked this pull request as ready for review
September 24, 2026 04:43
Contributor
|
On a M5 Max I found almost no performance change with these setting using the Clang defaults to |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Make the macOS arm64 target's CPU policy explicit: retain the Apple Silicon-compatible M1 instruction baseline, while requesting generic scheduling instead of tuning the universal artifact to a particular M generation.
This keeps the existing
-arch arm64and macOS 11 deployment target. PGO and LTO settings are unchanged.Measurements
On an M1 Pro, I built CPython 3.14.6 with PGO and ThinLTO using LLVM 23.1.1 and compared the proposed flags against both plain
-arch arm64and explicit M1 tuning. Across five small workloads, the proposed flags were within measurement noise of plain-arch arm64; explicit M1 tuning was about 3–11% faster than the proposed generic scheduling policy. That is an intentional universal-target tradeoff, measured on one machine, not a broad hardware claim.Validation