-
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
Standard library not linked in single file compilation #581
Comments
#602 has been resolved and work on this has been resumed. Unfortunately, this does not work out of the box. Now I am trying to include The problem is that, even if that works, the name of the function appears not to be the same. For example, if I take a look into the goto functions I can find a call to The problem may be that the version built using |
Yesterday I was able to link in the standard library in a small piece of code which just prints a value. I did so by setting up a library project, using a public function named "public" in However, when I run CBMC in the
I believe this is due to an incomplete code generation on our end, but this is the first time I am seeing this message so I am not sure. |
@adpaco-aws the print issue has been addressed in #825. Should we keep this issue open? |
Document this limitation and change "bug" label to "feature". |
Relevant discussion: #576 (comment) |
This has been fixed as part of the MIR Linker work. #1588 |
The number of verification failures in the dashboard increased significantly this week. The most common reason is this single failure:
We are now failing to verify any example with print macros on it. This is due to the changes in #535 and the fact that the standard library is not linked in during single file compilation.
The text was updated successfully, but these errors were encountered: