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

Support for ARM64 environments #86

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Support for ARM64 environments #86

wants to merge 12 commits into from

Conversation

msprotz
Copy link
Member

@msprotz msprotz commented Jan 7, 2022

This PR essentially aims to make the everest script suitable for building (and verifying) on a Linux/arm64 environment.

  • Since Z3 does not distribute aarch64 binaries, we offer to clone and build Z3 from source.
  • Unfortunately, Z3 4.8.5 segfaults. We fallback to a different revision of Z3, should that happen. (But it's not great for proofs... since proofs are only known to work with 4.8.5.)
  • This does not take into account Apple M1 chips, for which we are happy to rely on emulation of the x64 OSX binary build of Z3.

FYI, the segfault is as follows, seen from gdb:

Program received signal SIGSEGV, Segmentation fault.
smt::mam_impl::insert (this=this@entry=0xaaaaf0f93968, t=0x5, p=p@entry=0xaaaaf0fadd40, qa=qa@entry=0xaaaaf0fda1c8, mp=mp@entry=0xaaaaf0fe45c8) at /home/everest/everest/z3-source/src/smt/mam.cpp:3265
3265	                if (t->m_label == p->m_label) {

Z3 4.8.14 seems to have a different output because F* complains
(although rarely!):

```
Unexpected error; please file a bug report, ideally with a minimized version of the source program that triggered the error.
(Failure "Parse error: </result> not found"
```

I ran a `git bisect` to find the first commit after z3-4.8.5 that does
*not* segfault on the query that's part of this PR.
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.

1 participant