-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[InstCombine] samesign
flag should be dropped
#112350
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
Labels
Comments
Don't we miss checking the flag in |
Yeah. I am preparing a patch. |
But adding support in |
I assume we may need to |
dtcxzyw
added a commit
that referenced
this issue
Oct 16, 2024
In #93591 we introduced `isKnownInversion` and assumes `X` is poison implies `Y` is poison because they share common operands. But after introducing `samesign` this assumption no longer hold if `X` is an icmp has `samesign` flag. Alive2 link: https://alive2.llvm.org/ce/z/rj3EwQ (Please run it locally with this patch and AliveToolkit/alive2#1098). This approach is the most conservative way in my mind to address this problem. If `X` has `samesign` flag, it will check if `Y` also has this flag and make sure constant RHS operands have the same sign. Fixes #112350.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproducer:
The text was updated successfully, but these errors were encountered: