Skip to content

Enable printing of traces for arrays in new SMT backend #7066

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

Closed

Conversation

NlightNFotis
Copy link
Contributor

This PR enables us to request CBMC to print traces of arrays in certain cases.

  • Each commit message has a non-empty body, explaining why the change was made.
  • Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • 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).
  • My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@NlightNFotis NlightNFotis force-pushed the tas/smt_array_trace_printing branch from 6022444 to 88a4540 Compare August 11, 2022 09:05
@tautschnig
Copy link
Collaborator

How does this relate to #7078 @thomasspriggs @NlightNFotis ? Should this one just be closed?

@thomasspriggs
Copy link
Contributor

This other PR has been merged instead - #7078

@thomasspriggs
Copy link
Contributor

How does this relate to #7078 @thomasspriggs @NlightNFotis ? Should this one just be closed?

Yes this PR is now closed. There were two PRs due to the responsibility for getting this finished and merged being passed back and forth between myself and Fotis.

@NlightNFotis NlightNFotis deleted the tas/smt_array_trace_printing branch September 5, 2022 09:13
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.

3 participants