[BACKEND] Update llvm to llvm/llvm-project@56152fa377 #4625
Conversation
This file contains 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
This contains the two commit we want to have for AMD backend: * llvm/llvm-project#102869 * llvm/llvm-project#104598 This needs to update `visitOperation` signature following llvm/llvm-project@15e915a44f Also added `mlir::LLVM::registerInlinerInterface` to address LLVM ERROR: checking for an interface (`mlir::DialectInlinerInterface`) that was promised by dialect 'llvm' but never implemented.
ThomasRaoux
approved these changes
Aug 31, 2024
bertmaher
pushed a commit
to bertmaher/triton
that referenced
this pull request
Dec 10, 2024
This bumps to llvm/llvm-project@56152fa377 to further include the following fix * llvm/llvm-project#105871 Which was fixing issues in a previous LLVM bump * triton-lang#4624
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 bumps to llvm/llvm-project@56152fa377 to further
include the following fix
Which was fixing issues in a previous LLVM bump