-
Notifications
You must be signed in to change notification settings - Fork 14.3k
[mlir] Align num elements type to LLVM ArrayType #93230
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
374f6a1
[mlir] Align num elements type to LLVM ArrayType
clementval e9a6eed
Use ConstantAggregateZero when we deal with zero constant
clementval d6237ab
Use std::vector to enable large constant
clementval 8cc0977
Add comment
clementval 66ecd8d
Move check line above code line
clementval 280e9ef
Attempt to use ConstantDataArray for i32
clementval 8d56848
clang-format
clementval e2c3e5d
Support all int types
clementval a26ad9b
Address comments
clementval File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -632,8 +632,43 @@ llvm::Constant *mlir::LLVM::detail::getLLVMConstant( | |
llvm::ElementCount::get(numElements, /*Scalable=*/isScalable), child); | ||
if (llvmType->isArrayTy()) { | ||
auto *arrayType = llvm::ArrayType::get(elementType, numElements); | ||
SmallVector<llvm::Constant *, 8> constants(numElements, child); | ||
return llvm::ConstantArray::get(arrayType, constants); | ||
if (child->isZeroValue()) { | ||
return llvm::ConstantAggregateZero::get(arrayType); | ||
} else { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: can you drop the else since there is a return in the if body? That should save one indention for the else body. |
||
if (llvm::ConstantDataSequential::isElementTypeCompatible( | ||
elementType)) { | ||
// TODO: Handle all compatible types. This code only handles integer. | ||
if (llvm::IntegerType *iTy = | ||
dyn_cast<llvm::IntegerType>(elementType)) { | ||
if (llvm::ConstantInt *ci = dyn_cast<llvm::ConstantInt>(child)) { | ||
if (ci->getBitWidth() == 8) { | ||
SmallVector<int8_t> constants(numElements, ci->getZExtValue()); | ||
return llvm::ConstantDataArray::get(elementType->getContext(), | ||
constants); | ||
} | ||
if (ci->getBitWidth() == 16) { | ||
SmallVector<int16_t> constants(numElements, ci->getZExtValue()); | ||
return llvm::ConstantDataArray::get(elementType->getContext(), | ||
constants); | ||
} | ||
if (ci->getBitWidth() == 32) { | ||
SmallVector<int32_t> constants(numElements, ci->getZExtValue()); | ||
return llvm::ConstantDataArray::get(elementType->getContext(), | ||
constants); | ||
} | ||
if (ci->getBitWidth() == 64) { | ||
SmallVector<int64_t> constants(numElements, ci->getZExtValue()); | ||
return llvm::ConstantDataArray::get(elementType->getContext(), | ||
constants); | ||
} | ||
} | ||
} | ||
} | ||
// std::vector is used here to accomodate large number of elements that | ||
// exceed SmallVector capacity. | ||
std::vector<llvm::Constant *> constants(numElements, child); | ||
joker-eph marked this conversation as resolved.
Show resolved
Hide resolved
|
||
return llvm::ConstantArray::get(arrayType, constants); | ||
} | ||
} | ||
} | ||
|
||
|
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also have a zero operation for zero initialized types that uses
llvm::Constant::getNullValue
during the lowering to LLVM. This should be efficient for any kind of zero initialized values:Note: that your change to the constant lowering still makes sense since there are multiple ways of expressing a zero constant and ideally all of them are efficient in the lowering.