-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
TypePromotion produces invalid IR (take 2) #59554
Comments
@llvm/issue-subscribers-backend-aarch64 |
cc @bcl5980, as you worked on the previous fix. |
Candidate patch: https://reviews.llvm.org/D140869 |
…ate type is not extend type If the src type is not extend type, after convert the truncate to and we need to truncate the and also to make sure the all user is legal. The old fix D137613 doesn't work when the truncate convert to and have the other users. So this time I try to add the truncate after and to avoid all these potential issues. Fix: llvm#59554 Reviewed By: samparker Differential Revision: https://reviews.llvm.org/D140869 (cherry picked from commit a0b470c)
/cherry-pick a0b470c |
/branch llvm/llvm-project-release-prs/issue59554 |
/pull-request llvm/llvm-project-release-prs#222 |
Adding this as a potential backport, as multiple people have hit this issue with Rust on AArch64. |
Is this a regression? |
It looks like the TypePromotion issue occurs with opt-14 as well, though we have only started seeing it in end-to-end compiles with LLVM 15. |
…ate type is not extend type If the src type is not extend type, after convert the truncate to and we need to truncate the and also to make sure the all user is legal. The old fix D137613 doesn't work when the truncate convert to and have the other users. So this time I try to add the truncate after and to avoid all these potential issues. Fix: #59554 Reviewed By: samparker Differential Revision: https://reviews.llvm.org/D140869 (cherry picked from commit a0b470c)
Results in a verifier error:
The produced IR looks as follows:
The symptoms here are similar to #58843, but the fix for that one did not fix this case.
The text was updated successfully, but these errors were encountered: