Skip to content

Conversation

@thk123
Copy link
Contributor

@thk123 thk123 commented May 6, 2020

  • 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).
  • [na] 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.

Ideally there should be documentation for the incremental feature in the docs, but it doesn't seem to be present. @peterschrammel are you aware of any that can be imported in?


#include <util/source_location.h>
#include <util/xml.h>
#include <iostream>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

spurious change

" but before solving that iteration. If for \n" \
" example it is 1, then the loop will be \n" \
" unwound once, and immediately checked. \n" \
" Note: this means min-unwind 1 or \n"\
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
" Note: this means min-unwind 1 or \n"\
" Note: this means for min-unwind 1 or \n"\

?

Thomas Kiley added 2 commits May 6, 2020 14:02
It is agreed that if --unwind N can find an error, that unwind-min N
should find the same error. That is, we start checking immediately after
doing N unwinds, rather than after doing N increments of the incremental
unwinding (i.e. unwind + solve)
@thk123 thk123 force-pushed the make-min-unwind-consistent-with-unwind branch 2 times, most recently from 565ee5c to 50bdc60 Compare May 6, 2020 13:04
It was somewhat ambiguous whether the checking started after N unwinds,
or after N incremental solves. This documentation clarifies the checking
is enabled after the Nth unwind, before the Nth solve.
@thk123 thk123 force-pushed the make-min-unwind-consistent-with-unwind branch from 50bdc60 to 293d469 Compare May 6, 2020 13:10
@thk123
Copy link
Contributor Author

thk123 commented May 6, 2020

@peterschrammel ready for rereview

@thk123 thk123 merged commit 319a06c into diffblue:develop May 7, 2020
@thk123 thk123 deleted the make-min-unwind-consistent-with-unwind branch May 7, 2020 09:19
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