Skip to content

Warn on usage of goto-instrument --constant-propagator #7111

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

According to the doxygen in analyses/constant_propagator.h, this is "A simple, unsound constant propagator." It is worth warning users so that it is not accidentally applied to use cases where soundness is important.

This PR relates to the following issue - #7041

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

According to the doxygen in `analyses/constant_propagator.h`, this is "A
simple, unsound constant propagator." It is worth warning users so that
it is not accidentally applied to use cases where soundness is
important.
@codecov
Copy link

codecov bot commented Sep 9, 2022

Codecov Report

Merging #7111 (d91d678) into develop (e35425e) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop    #7111   +/-   ##
========================================
  Coverage    77.91%   77.92%           
========================================
  Files         1576     1576           
  Lines       181611   181647   +36     
========================================
+ Hits        141511   141543   +32     
- Misses       40100    40104    +4     
Impacted Files Coverage Δ
src/util/xml.cpp 73.88% <ø> (ø)
.../goto-instrument/goto_instrument_parse_options.cpp 71.14% <100.00%> (+0.06%) ⬆️
src/cpp/cpp_convert_type.cpp 72.72% <0.00%> (-0.69%) ⬇️
src/cpp/cpp_typecheck_code.cpp 80.41% <0.00%> (-0.26%) ⬇️
src/cpp/cpp_typecheck_conversions.cpp 84.95% <0.00%> (-0.05%) ⬇️
src/cpp/template_map.cpp 57.85% <0.00%> (ø)
src/ansi-c/ansi_c_declaration.cpp 74.07% <0.00%> (ø)
src/cpp/parse.cpp 68.80% <0.00%> (+0.01%) ⬆️
src/cpp/cpp_typecheck_compound_type.cpp 86.87% <0.00%> (+0.03%) ⬆️
src/cpp/cpp_typecheck_constructor.cpp 89.18% <0.00%> (+0.08%) ⬆️
... and 5 more

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

Copy link
Collaborator

@martin-cs martin-cs left a comment

Choose a reason for hiding this comment

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

Yes but please look at #7120 which has a rather more radical take.

( Also cross referencing #6480 )

@thomasspriggs thomasspriggs merged commit d3b72f2 into diffblue:develop Sep 12, 2022
@thomasspriggs thomasspriggs deleted the tas/const_prop_unsound branch September 12, 2022 11:12
@thomasspriggs
Copy link
Contributor Author

I have merged this PR now in order to provide a warning to users ASAP. I am happy for the warning to be removed along with the option when we are ready to merge a more comprehensive solution. Hopefully I won't have caused you too many rebasing issues.

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.

2 participants