Skip to content

byte_extract lowering of unions [blocks: #2068] #4187

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 6 commits into from
Feb 14, 2019

Conversation

tautschnig
Copy link
Collaborator

We previously handled unions like PODs.

Only the last commit is new, the rest is borrowed from #4124.

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a 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.

Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

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

✔️
Passed Diffblue compatibility checks (cbmc commit: 19b8b80).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/100912495

@tautschnig tautschnig self-assigned this Feb 14, 2019
Refactor the code used for arrays to make it re-usable for vectors and arrays.
We already limited extraction at an uppper bound, but when we know the offset we
can also start as late as possible. For structs, for example, we now do not
expand components that will be irrelevant to the final result.
No need to construct index_exprt when we can just pick the operand out of a
vector.
This makes the unit of measurement explicit and thus should help avoid
bits/bytes confusion.
This makes the interface much more explicit about what is or isn't supported at
moment.
We previously handled unions like PODs.
tautschnig added a commit that referenced this pull request Feb 14, 2019
Byte extract lowering for vectors and array cleanup [blocks: #2068, #4187]
@tautschnig tautschnig changed the title byte_extract lowering of unions [depends-on: #4124, blocks: #2068] byte_extract lowering of unions [blocks: #2068] Feb 14, 2019
Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

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

✔️
Passed Diffblue compatibility checks (cbmc commit: 761ad8a).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/100979304

@tautschnig tautschnig merged commit 7632d02 into diffblue:develop Feb 14, 2019
@tautschnig tautschnig deleted the byte-op-union branch February 14, 2019 20:49
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