Skip to content

Quantifier scoping #6189

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 4 commits into from
Jun 19, 2021
Merged

Quantifier scoping #6189

merged 4 commits into from
Jun 19, 2021

Conversation

kroening
Copy link
Member

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

@codecov
Copy link

codecov bot commented Jun 18, 2021

Codecov Report

Merging #6189 (62e04e4) into develop (0002950) will increase coverage by 7.67%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #6189      +/-   ##
===========================================
+ Coverage    67.40%   75.08%   +7.67%     
===========================================
  Files         1157     1454     +297     
  Lines        95236   160943   +65707     
===========================================
+ Hits         64197   120840   +56643     
- Misses       31039    40103    +9064     
Flag Coverage Δ
cproversmt2 ?
regression ?
unit ?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/util/mathematical_expr.cpp 17.02% <0.00%> (-82.98%) ⬇️
src/util/string_container.cpp 52.94% <0.00%> (-47.06%) ⬇️
src/solvers/prop/prop.cpp 42.85% <0.00%> (-41.76%) ⬇️
src/solvers/flattening/boolbv_member.cpp 53.65% <0.00%> (-38.65%) ⬇️
src/cpp/cpp_storage_spec.cpp 65.00% <0.00%> (-35.00%) ⬇️
src/util/cmdline.h 66.66% <0.00%> (-33.34%) ⬇️
src/solvers/strings/array_pool.h 66.66% <0.00%> (-33.34%) ⬇️
src/solvers/strings/string_refinement.h 66.66% <0.00%> (-33.34%) ⬇️
...rs/strings/string_concatenation_builtin_function.h 0.00% <0.00%> (-33.34%) ⬇️
src/cbmc/c_test_input_generator.cpp 60.00% <0.00%> (-30.33%) ⬇️
... and 1433 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 523622a...62e04e4. Read the comment docs.

kroening added 4 commits June 19, 2021 13:43
The boolbv backend now introduces new names for the bound symbols.  This
matches the new behavior for let expressions.
The backend is now assumed to take care of scoping, which means that the
front-end no longer has to generate fresh identifiers.
This refactoring avoids repeating the code for creating fresh bound
identifiers.
This changes the mechanism for preserving identifiers hidden by function
parameters to use stack-local storage.  The class-level data structure for
renaming can then be removed.
@kroening kroening force-pushed the quantifier_scoping branch from 3dfbcab to 62e04e4 Compare June 19, 2021 12:45
@kroening kroening merged commit d52022d into develop Jun 19, 2021
@kroening kroening deleted the quantifier_scoping branch June 19, 2021 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants