-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
downloads: upgrade LLVM 18.0.8 -> 19.1.0 #420
Conversation
9c5748b
to
62883a6
Compare
LLVM 19 yields a compile error without these patches. Strictly speaking we may only need the final one. However there are conflicts unless we take all patches to `src/aarch64/sysv.S`. So we just take the 3 of them.
62883a6
to
2b08be0
Compare
This looks to be passing CI. So asking for review. |
It looks like two builds failed here -- possible that those are new failures? |
(Only asking because they're also failing on main and on my own PRs now :)) |
Uh what. I merged on my phone and I only saw green. Feel free to revert I guess. |
I reproduced the failure locally and reverted. This looks like upstream issue python/cpython#124948. I was going to say it was strange it only reproduced on 3.12. But we currently only have BOLT enabled on 3.12. So looks like a general BOLT regression on LLVM 19.1.0. |
Well, not the same symbol as the upstream CPython issue. But same failure mode of unable to locate an address. My best guess is BOLT isn't able to follow a rewrite performed by PGO or itself. |
This is a redo of #420, which was merged prematurely. With the BOLT changes from #463 merged, LLVM 19 _just works_. As part of this we also modernize the BOLT apply settings to follow the recommendations at https://llvm.org/devmtg/2024-03/slides/practical-use-of-bolt.pdf. This includes enabling support for loading hot code from a huge page at runtime. This should _just work_ and could result in perf wins via improved iTLB hit rate, etc.
No description provided.