-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
aarch64 llvm 14 regression with vectors: Assertion `mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match"' failed #56398
Comments
@llvm/issue-subscribers-bug |
@llvm/issue-subscribers-backend-aarch64 |
This starts from: $ git bisect good
ebc17a0d68208a967fe8e13e1874874228dda622 is the first bad commit
commit ebc17a0d68208a967fe8e13e1874874228dda622
Author: Matt Arsenault <Matthew.Arsenault@amd.com>
Date: Tue Jul 27 11:08:06 2021 -0400
GlobalISel: Scalarize unaligned vector stores
This has the same problems and limitations as the load path. |
Missing vector legalization rules for G_CTTZ and we end up trying to use a scalar rule instead. |
Thanks for the bug report. Should be fixed in 9cc1dd2 |
Thanks for the fix! Re-opening since this commit has not yet landed in the release/15.x branch. cc @tstellar |
/cherry-pick 9cc1dd2 |
/branch llvm/llvm-project-release-prs/issue56398 |
@tstellar https://github.com/llvm/llvm-project/runs/7537547137?check_suite_focus=true
There's two problems here:
|
/branch llvm/llvm-project-release-prs/issue56398 |
OK, I'll make this change.
I fixed this issue. |
Thanks! Unfortunately we get a new error now (https://github.com/llvm/llvm-project/runs/7549380969?check_suite_focus=true):
|
/branch llvm/llvm-project-release-prs/issue56398 |
/pull-request llvm/llvm-project-release-prs#25 |
I fixed this in b1dace6. |
Does not affect LLVM 13.0.1.
Tested with LLVM 14.0.6. Have not yet confirmed whether it affects trunk.
Reduced LLVM IR:
Reproduction:
Downstream issue: ziglang/zig#12013
Apologies for not catching this during the RC phase.
The text was updated successfully, but these errors were encountered: