Bump LLVM to 3c53adec68b3e7be3d69bc4e24168e530097fce0. #9063
Conversation
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
mikeurbach
requested review from
andrewb1999,
cgyurgyik,
jiahanxie353,
mortbopet,
rachitnigam and
teqdruid
as code owners
Contributor
Author
|
Oops this appears to be out of date, let me rebase. |
mikeurbach
force-pushed
the
mikeurbach/bump-llvm
branch
from
7b15ce3 to
7856092
Compare
cgyurgyik
approved these changes
Oct 7, 2025
uenoku
approved these changes
Oct 11, 2025
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.
This picks up a few changes.
The minimum nanobind version was updated upstream in:
llvm/llvm-project@efd96af
The SCF
constantTripCountAPI changed in:llvm/llvm-project@75469bb
Finally, the DialectConversion framework no longer supports
replaceAllUsesWithfollowed byeraseOp; the replace APIs also markthe op erased. This is similar to the changes already landed in CIRCT
here: #8989.