We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “No 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? No Sign in to your account
This program:
@​useFlag = private global <4 x i1> <i1 true, i1 true, i1 true, i1 true> define i32 @​get(i32 %arg) { %ld = load <4 x i1>, <4 x i1>* @​useFlag %zx = zext <4 x i1> %ld to <4 x i32> %ee = extractelement <4 x i32> %zx, i32 %arg ret i32 %ee } define i32 @​main() { %g = call i32 @​get(i32 2) ret i32 %g }
will return 0. I'd expect it to return 1 since it should load i1 true and then zext that to i32 1.
Note that if you get(i32 0) then it returns 1 as expected. Also, with -O3 this returns 1 correctly since the load is optimized out.
get(i32 0)
Tested with:
$ clang-10 --version clang version 10.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin
Sorry if this is a duplicate! I found some related notes on lists.llvm.org, but not a bug report.
The text was updated successfully, but these errors were encountered:
696f536
@llvm/issue-subscribers-clang-codegen
Sorry, something went wrong.
[AsmPrinter] Fix bit pattern for i1 vectors.
1f623c0
Vectors are defined to be tightly packed, regardless of the element type. The AsmPrinter didn't realize this, and was allocating extra padding. Fixes llvm/llvm-project#49286 Fixes llvm/llvm-project#53246 Fixes llvm/llvm-project#55522 Differential Revision: https://reviews.llvm.org/D129164
No branches or pull requests
Extended Description
This program:
will return 0. I'd expect it to return 1 since it should load i1 true and then zext that to i32 1.
Note that if you
get(i32 0)
then it returns 1 as expected. Also, with -O3 this returns 1 correctly since the load is optimized out.Tested with:
Sorry if this is a duplicate! I found some related notes on lists.llvm.org, but not a bug report.
The text was updated successfully, but these errors were encountered: