-
Notifications
You must be signed in to change notification settings - Fork 13.5k
16 byte Aligned load generated to load 32 byte wide AVX register from stack memory #98044
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
Comments
@llvm/issue-subscribers-backend-x86 Author: Manish Kausik H (Nirhar)
Problematic IR:
```
define i8 @foo(i64 %elemIdx, <32 x i1> %arr) {
entry:
br label %loop
loop: ; preds = %loop, %entry exit: ; preds = %loop
.LCPI0_0:
|
The |
@phoebewang sorry, I think I made a mistake during the IR reduction. I have updated the Bug description with the problematic IR. The problem is similar to #77730, except that the vector is now of <32 x i16> instead of <32 x i8> |
This patch ports the commit a6614ec to SelectionDAG TypeLegalization. Fixes llvm#98044
This patch ports the commit a6614ec to SelectionDAG TypeLegalization. Fixes llvm#98044
This patch sets the alignment of store instructions generated during type legalization of extractelement instruction, after considering stack alignment. Fixes llvm#98044
This patch sets the alignment of store instructions generated during type legalization of extractelement instruction, after considering stack alignment. Fixes llvm#98044
…ype when Stack is non-realignable This patch sets the alignment of store instructions generated during type legalization of extractelement instruction, after considering stack alignment, if the stack is not realignable. Fixes llvm#98044
Uh oh!
There was an error while loading. Please reload this page.
Problematic IR:
generates:
when run with
llc
. This leads to the generation of avmovdqa
instruction, which can lead to a General Protection Fault. Here is the link to the godbolt demo: https://godbolt.org/z/33h7YGc5KThe problem seems to be in instruction selection again, similar to #77730
The text was updated successfully, but these errors were encountered: