Skip to content

Add warning about unsound simplification in goto-analyzer #7163

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

Conversation

thomasspriggs
Copy link
Contributor

At the time of raising this PR, this simplification is known to return unsound/erroneous results for input programs featuring recursion. This warning should be remove once the known issues have been fixed. See #7041

@martin-cs I am not yet that familiar with the goto-analyzer entry point yet. Can you confirm whether the location I have placed this message accurately covers the scope of the issue?

  • 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.

At the time of adding this commit, this simplification is known to
return unsound/erroneous results for input programs featuring recursion.
This warning should be remove once the known issues have been fixed. See
diffblue#7041
@codecov
Copy link

codecov bot commented Sep 28, 2022

Codecov Report

Base: 77.88% // Head: 77.88% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (5598615) compared to base (6d6319f).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #7163   +/-   ##
========================================
  Coverage    77.88%   77.88%           
========================================
  Files         1576     1576           
  Lines       181859   181861    +2     
========================================
+ Hits        141648   141650    +2     
  Misses       40211    40211           
Impacted Files Coverage Δ
src/ansi-c/ansi_c_entry_point.cpp 89.57% <100.00%> (ø)
src/goto-analyzer/static_simplifier.cpp 87.65% <100.00%> (+0.31%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@feliperodri feliperodri added aws Bugs or features of importance to AWS CBMC users aws-high labels Sep 30, 2022
@thomasspriggs thomasspriggs merged commit cf00a53 into diffblue:develop Oct 5, 2022
@thomasspriggs thomasspriggs deleted the tas/goto-analyzer-warning branch October 5, 2022 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws Bugs or features of importance to AWS CBMC users aws-high
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants