[fix] mlir: specify the mtriple in llvm target - #144
Merged
guillon merged 1 commit intoSep 17, 2026
Merged
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
guillon
approved these changes
Sep 17, 2026
Member
|
Fixes issue #137 |
Member
|
Just to clarify, this does not fix the compile time issue #138 mentionned above. |
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.
Motivation
#137 and #138 Revealed a regression in the mlir performance. The regression was due to the llvm update from 21 to 22 now requiring us to specify --mtriple in llc, in order for the memset() for the
linalg.fillto lower optimally. With the old llvm, llc correctly lowered a large llvm.memset to a call to memset(). With the new llvm, the same input lowers to an inlined scalar byte-at-a-time store loop.Description
The fix is explicitly passing -mtriple to llc for the native case too, queried from the LLVM install itself via llvm-config --host-target.
Using the Example from the Issue #137:
tvm performance: (same for both)
mlir peformance before:
mlir performance after:
For the compile time example in #138
tvm:
mlir before:
mlir after: