-
Notifications
You must be signed in to change notification settings - Fork 264
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
aarch64: error: incompatible type for argument 1 of '__CPROVER_OBJECT_SIZE #8357
Labels
Comments
tautschnig
added a commit
to tautschnig/cbmc
that referenced
this issue
Jul 2, 2024
This extends 4d0164f to uses within `__CPROVER_OBJECT_SIZE`. Fixes: diffblue#8357
3 tasks
With #8366 applied, I still get following errors on
|
tautschnig
added a commit
to tautschnig/kani
that referenced
this issue
Aug 9, 2024
The default compiler on Amazon Linux 2 is GCC 7, which is not sufficiently recent for building CBMC v6+. Install and use GCC 10, adjust warnings to cope with the flex version provided by Amazon Linux 2, and handle the non-default std::filesystem support. Furthermore, apply a workaround until diffblue/cbmc#8357 has been fixed on the CBMC side.
github-merge-queue bot
pushed a commit
to model-checking/kani
that referenced
this issue
Aug 9, 2024
The default compiler on Amazon Linux 2 is GCC 7, which is not sufficiently recent for building CBMC v6+. Install and use GCC 10, adjust warnings to cope with the flex version provided by Amazon Linux 2, and handle the non-default std::filesystem support. Furthermore, apply a workaround until diffblue/cbmc#8357 has been fixed on the CBMC side. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CBMC version: 6.0.1
Operating system: ALT Linux
Exact command line resulting in the issue:
cmake --build aarch64-alt-linux --verbose --parallel 24
What behaviour did you expect: success
What happened instead:
Build failure on aarch64:
Noting that there was similar issue in 2023: #7862
The text was updated successfully, but these errors were encountered: