Skip to content
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

change z3 version to 4.13.3 #510

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

change z3 version to 4.13.3 #510

wants to merge 1 commit into from

Conversation

karthikbhargavan
Copy link
Contributor

I am sure there may be a better place to put the --z3version but with this change, KaRaMeL works with the latest F* and Z3 4.13.3

@msprotz
Copy link
Contributor

msprotz commented Dec 26, 2024

@mtzguido can you remind me what's up with using the most recent z3 version?

what I'd like to understand is what happens to people like @R1kM and I for whom z3 is z3 4.8.5 and who presumably don't have z3 4.13.3 installed -- can everything be handled with ./everest z3? just want to make sure before merging this in!

@prosecco
Copy link

prosecco commented Dec 26, 2024 via email

@mtzguido
Copy link
Member

Yes running ./everest z3 should install both versions as z3-4.8.5 and z3-4.13.3 so F* can find them automatically. project-everest/everest#119

@msprotz
Copy link
Contributor

msprotz commented Dec 26, 2024

@karthikbhargavan can you recall if you upgraded something else in your setup then? could it be that you now have z3 resolve to 4.13.3 instead of the old 4.8.5? F* expects 4.8.5 by default

@mtzguido
Copy link
Member

(btw, I think karamel should work as it is now with 4.8.5 as long as F* can find it, but the idea is to gradually move to 4.13.3, so I'd be happy seeing this PR merged if it works for everyone)

@msprotz
Copy link
Contributor

msprotz commented Dec 26, 2024

yeah I'm roughly in favor of merging (modulo putting the flag directly in $(FSTAR)), with the caveat that some users may not realize that the right thing to do is to create aliases, and thus will end up with z3 being 4.13.3 which will then make their build of HACL* fail (which is what I suspect happened to Karthik)

maybe the error message should clearly say "please create an alias" (if it doesn't already?)

@mtzguido
Copy link
Member

mtzguido commented Dec 26, 2024

The error should be something like this:

$ ./bin/fstar.exe ulib/Prims.fst -f
* Error 357 at ulib/Prims.fst(498,0-498,68):
  - Unexpected Z3 version for 'z3': expected '4.8.5', got '4.13.3'.
  - Please download version 4.8.5 of Z3 from
        https://github.com/Z3Prover/z3/releases
    and install it into your $PATH as 'z3-4.8.5'.

1 error was reported (see above)

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.

4 participants