Skip to content

Store pointer encoding configuration in boolbv_widtht #5822

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 3 commits into from
Feb 16, 2021

Conversation

tautschnig
Copy link
Collaborator

Rather than handling the object/offset bit width in multiple places,
make boolbv_widtht the only place to provide this information.

  • 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 Feb 12, 2021

Codecov Report

Merging #5822 (5cf2b07) into develop (9778868) will increase coverage by 0.00%.
The diff coverage is 83.62%.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #5822   +/-   ##
========================================
  Coverage    72.85%   72.85%           
========================================
  Files         1423     1421    -2     
  Lines       154072   154130   +58     
========================================
+ Hits        112244   112292   +48     
- Misses       41828    41838   +10     
Impacted Files Coverage Δ
src/solvers/flattening/boolbv_union.cpp 57.14% <0.00%> (ø)
src/solvers/flattening/boolbv_with.cpp 65.30% <0.00%> (ø)
src/solvers/flattening/boolbv.h 69.56% <50.00%> (-4.12%) ⬇️
src/solvers/flattening/bv_pointers.cpp 82.93% <86.02%> (+0.52%) ⬆️
src/solvers/flattening/boolbv_byte_extract.cpp 70.00% <100.00%> (ø)
src/solvers/flattening/boolbv_byte_update.cpp 100.00% <100.00%> (ø)
src/solvers/flattening/boolbv_width.cpp 76.69% <100.00%> (-0.23%) ⬇️
src/solvers/flattening/boolbv_width.h 100.00% <100.00%> (ø)
src/solvers/flattening/bv_pointers.h 100.00% <100.00%> (ø)
src/util/endianness_map.h 100.00% <0.00%> (ø)

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 c408367...5cf2b07. Read the comment docs.

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.

Makes sense to centralise this functionality.

@tautschnig tautschnig force-pushed the pointer-encoding-width branch from e94bdbb to cb5bef5 Compare February 15, 2021 22:49
The special-casing of the endianness encoding handled by
bv_endianness_mapt is really specific to bv_pointerst, not boolbvt in
general. Thus, move this data structure to bv_pointers.cpp and enable
overriding the endianness map from boolbvt.

This commit is refactoring only, no changes in behaviour intended.
With upcoming changes to pointer encoding it will be necessary to enable
children of boolbvt to define their own bit encoding width of data
types.

This commit is refactoring only, no changes in behaviour intended.
In preparation of tweaking the propositional encoding, place all knowledge of
the bit width of encoded pointers in bv_pointerst. Also, do not hard-code the
width just once, but really look at each type.
@tautschnig tautschnig merged commit 92659b5 into diffblue:develop Feb 16, 2021
@tautschnig tautschnig deleted the pointer-encoding-width branch February 16, 2021 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants