Skip to content

goto-synthesizer: ignore __CPROVER_-prefixed symbols #8348

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

Merged
merged 1 commit into from
Jun 19, 2024

Conversation

tautschnig
Copy link
Collaborator

Just like assign-instrumentation otherwise does, goto-synthesizer should filter out symbols with prefix __CPROVER_ from the assigns set that it generates. The __CPROVER_going_to variables have become such an example (seen when running Kani's regression tests).

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

Just like assign-instrumentation otherwise does, goto-synthesizer should
filter out symbols with prefix `__CPROVER_` from the assigns set that it
generates. The __CPROVER_going_to variables have become such an example
(seen when running Kani's regression tests).
@feliperodri feliperodri added the Code Contracts Function and loop contracts label Jun 19, 2024
@tautschnig tautschnig merged commit ff1fe63 into diffblue:develop Jun 19, 2024
37 of 38 checks passed
@tautschnig tautschnig deleted the goto-synthesizer-going-to branch June 19, 2024 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Code Contracts Function and loop contracts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants