Skip to content

Program table symbol type consistency #3128

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

Closed

Conversation

xbauch
Copy link
Contributor

@xbauch xbauch commented Oct 9, 2018

The first commit is just PR #3118 to reuse the common structure of checking this kind of consistency. The second looks up the symbol id in symbol table and calls base_type_eq on every symbol
expression in guard and code whenever relevant. Then prints out all inconsistencies.

  • Each commit message has a non-empty body, explaining why the change was made.
  • My contribution is formatted in line with CODING_STANDARD.md.
  • Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • 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.

Petr Bauch added 2 commits October 9, 2018 13:46
This first commit is just PR diffblue#3118 to reuse the common structure of checking
this kind of consistency.
Look up the symbol id in symbol table and call base_type_eq on every symbol
expression in guard and code whenever relevant. Print out all inconsistencies.
@xbauch xbauch force-pushed the program_table_symbol_type_consistency branch from c5ee238 to 40f038a Compare October 9, 2018 12:54
danpoe and others added 2 commits October 9, 2018 14:02
…e#3123

The condition to be checked is the same. Interface function name was changed to
follow the above PR. Also the check is now optional via command line.
Copy link
Contributor

@danpoe danpoe left a comment

Choose a reason for hiding this comment

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

LGTM

Builds a goto program with one assertion and checks that: 1) with the right type
in the table the validation succeeds, 2) with the wrong type the validation
fails.
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: 786e3b8).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/87658951

@xbauch
Copy link
Contributor Author

xbauch commented Nov 12, 2018

Moved to #3118.

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.

4 participants