Skip to content

Conversation

@dtcxzyw
Copy link
Contributor

@dtcxzyw dtcxzyw commented Oct 15, 2024

@dtcxzyw dtcxzyw marked this pull request as ready for review October 15, 2024 09:12
@dtcxzyw
Copy link
Contributor Author

dtcxzyw commented Oct 15, 2024

What? @nunoplopes Can you check the CI configuration? I don't think this patch can be compiled as llvm/llvm-project#111419 was just landed.

@nunoplopes
Copy link
Member

What? @nunoplopes Can you check the CI configuration? I don't think this patch can be compiled as llvm/llvm-project#111419 was just landed.

The CI doesn't link against LLVM. It builds just the 'alive' tool (because we need LLVM built with RTTI, and thus we would need to either build LLVM from scratch or cache an image somewhere)

@nunoplopes nunoplopes merged commit faf59b5 into AliveToolkit:master Oct 16, 2024
12 checks passed
dtcxzyw added a commit to llvm/llvm-project that referenced this pull request 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.
jmciver added a commit to jmciver/alive2 that referenced this pull request Jan 2, 2025
jmciver added a commit to jmciver/alive2 that referenced this pull request Jan 15, 2025
jmciver added a commit to jmciver/alive2 that referenced this pull request Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants