Skip to content

Use fieldref exprt #3915

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 1 commit into from
Jan 30, 2019
Merged

Use fieldref exprt #3915

merged 1 commit into from
Jan 30, 2019

Conversation

thk123
Copy link
Contributor

@thk123 thk123 commented Jan 24, 2019

  • 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/
  • [n/a] 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.
  • White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@@ -341,6 +341,22 @@ class fieldref_exprt : public exprt
set(ID_class, class_name);
set(ID_component_name, component_name);
}

irep_idt field_of_class() const
Copy link
Contributor

Choose a reason for hiding this comment

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

this suggests this yields a field -- how about just class_name?

/// components if necessary.
static member_exprt to_member(
const exprt &pointer,
const fieldref_exprt &field_instruction,
Copy link
Contributor

Choose a reason for hiding this comment

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

This isn't the instruction, rather it's its argument, so field_reference or just fieldref?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed in previous PR.

@thk123 thk123 force-pushed the use-fieldref-exprt branch from a654adb to 60553c1 Compare January 29, 2019 17:16
@thk123
Copy link
Contributor Author

thk123 commented Jan 29, 2019

@smowton comments addressed.

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.

🚫
This PR failed Diffblue compatibility checks (cbmc commit: a654adb).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99010646
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.

Common spurious failures:

  • the cbmc commit has disappeared in the mean time (e.g. in a force-push)
  • the author is not in the list of contributors (e.g. first-time contributors).

The incompatibility may have been introduced by an earlier PR. In that case merging this
PR should be avoided unless it fixes the current incompatibility.

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: 60553c1).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/99011453

@tautschnig tautschnig merged commit f3db3f0 into diffblue:develop Jan 30, 2019
@thk123 thk123 deleted the use-fieldref-exprt branch January 30, 2019 10:07
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.

4 participants