Repository navigation
Conversation
512ad23 to
9cc1f42
Compare
|
The new alt-ergo patch fixes a soundness problem with 2.6.4 that looks like it would've pervasive and affect pretty much all of our SMT calls. I would like to blacklist to force awareness in downstream users, but also admit we can only do this because the AE team was so transparent in disclosing it. @strub can you remind me where to find the blacklist? |
|
Search for |
9cc1f42 to
5f27329
Compare
|
Looks like Alt-Ergo 2.6.5 changed the way it reports its version in a way that's incompatible with why3's detection (like cvc5) and I will have to also merge in a process to patch up the why3.conf. |
|
And I can confirm that the proof goes through with 2.6.5 and a patched why3.conf. Now I just need to patch why3.conf in the docker... |
69be95b to
8aec2f6
Compare
z3 5.4.1 alt-ergo 2.6.4 -> 2.6.5 evict alt-ergo 2.6.4 include patch for why3.conf for configuration of recent cvc5, alt-ergo
8aec2f6 to
8c569ce
Compare
|
@strub this is now working, although I don't enjoy the fix I had to fold in there to accommodate the broken prover detection. I know it's marked yolo, but if you could give it some eyeballs and confirm there's not much else we can do short of a PR to Why3 (or all the provers that broke its detection, I guess ..), I'd be appreciative. |
No description provided.