-
Notifications
You must be signed in to change notification settings - Fork 88
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
Issues including algorithm with cpp 11 #1836
Comments
@rafaelsamenezes : You're using an old version of ESBMC. With the current version, you should get: $ esbmc alex3.cpp --std c++11
ESBMC version 7.6.0 64-bit x86_64 linux
Target: 64-bit little-endian x86_64-unknown-linux with esbmclibc
Parsing alex3.cpp
Converting
Generating GOTO Program
GOTO program creation time: 0.730s
GOTO program processing time: 0.002s
Starting Bounded Model Checking
Symex completed in: 0.003s (19 assignments)
Slicing time: 0.000s (removed 19 assignments)
Generated 0 VCC(s), 0 remaining after simplification (0 assignments)
BMC program time: 0.003s
VERIFICATION SUCCESSFUL |
There is an #if switch in the <algorithm> / <utility> header that conditionally defers to <type_traits> in order to provide std::swap for C++ >= 11. We don't provide our own <type_traits> (anymore). Thus, it might be that the installed header doesn't contain a std::swap definition. I'd need to know the package/version installed in order to fix this. Inquiry has been sent. |
Just got a confirmation that their GCC-12.1 is installed in a non-standard location. We might need to pass I actually would argue for a general pass-through option like |
Indeed, old version being selected, GCC-4.8 (note, this is ESBMC v7.6, see #1837):
|
… clang frontend directly This is meant to be used for non-standard options required by certain setups in order to, for instance in #1836, pass through options like --gcc-install-dir when a custom GCC installation in a non-standard path is being used.
… clang frontend directly This is meant to be used for non-standard options required by certain setups in order to, for instance in #1836, pass through options like --gcc-install-dir when a custom GCC installation in a non-standard path is being used.
… clang frontend directly This is meant to be used for non-standard options required by certain setups in order to, for instance in #1836, pass through options like --gcc-install-dir when a custom GCC installation in a non-standard path is being used.
… clang frontend directly This is meant to be used for non-standard options required by certain setups in order to, for instance in #1836, pass through options like --gcc-install-dir when a custom GCC installation in a non-standard path is being used.
|
… clang frontend directly This is meant to be used for non-standard options required by certain setups in order to, for instance in #1836, pass through options like --gcc-install-dir when a custom GCC installation in a non-standard path is being used.
I agree. Ubuntu 24.04 also has 14 up to 18 in their distribution. |
This issue was resolved by passing |
The following program is failing with
--cppstd 11
Fails with:
The text was updated successfully, but these errors were encountered: