-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Initial support for LLVM 20 #57352
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
Initial support for LLVM 20 #57352
Conversation
81383ed
to
c39401d
Compare
c39401d
to
2aef440
Compare
…leSlotTracker (#100310)" llvm/llvm-project@9a25866
…EP call backs (#114547)" llvm/llvm-project@dc45ff1
…teSymbols.h header. NFC."
… methods (#102608)"
…ineModuleSlotTracker (#100310)"
… methods (#102608)"
…sertion methods (#102608)"
686ae06
to
b73126e
Compare
Is this PR good to go for the time being? Further improvements could be done in follow up PRs. |
Yes |
Does this include any of the fixes in #56130? My initial impression is that those are missing here |
No I don't think this includes any of them, do we want it to? |
Yeah, generally my strategy was always to merge the fixes ahead of time in seperate PRs, and then only have the "flip the switch" PR without any code changes. |
Is this in reference to adding llvm 19 or 20 support? This is what I intended for 19, but a bunch of issues only became apparent once we flipped the switch and I didn't think it was worth it to try and split those changes out. Anyways, the 19 pr should be merged in soon so moot point anyways. |
For LLVM 20, we still need to deal with #55844, #57021 and get the LLVM 19 PR in.