Skip to content

C/C++ front-end: do not accept void-typed objects or members #5676

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
Dec 21, 2020

Conversation

tautschnig
Copy link
Collaborator

We silently accepted these, as many cases would work fine in goto
programs. The included regression test, however, demonstrates where this
would fail an invariant during Boolean flattening (if run with
--pointer-check). GCC refuses void typed variables, and so should we.

Test originates from an SV-COMP task, reduced to this minimal example
using C-Reduce.

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

@codecov
Copy link

codecov bot commented Dec 17, 2020

Codecov Report

Merging #5676 (9018306) into develop (4c2b413) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #5676   +/-   ##
========================================
  Coverage    69.45%   69.46%           
========================================
  Files         1243     1243           
  Lines       100620   100635   +15     
========================================
+ Hits         69887    69902   +15     
  Misses       30733    30733           
Flag Coverage Δ
cproversmt2 43.13% <13.33%> (-0.01%) ⬇️
regression 66.35% <100.00%> (+<0.01%) ⬆️
unit 32.27% <13.33%> (-0.01%) ⬇️

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

Impacted Files Coverage Δ
src/ansi-c/c_typecheck_base.cpp 81.52% <100.00%> (+0.20%) ⬆️
src/ansi-c/c_typecheck_type.cpp 77.19% <100.00%> (+0.10%) ⬆️
src/cpp/cpp_typecheck_code.cpp 72.47% <100.00%> (+0.47%) ⬆️
src/cpp/cpp_typecheck_compound_type.cpp 85.57% <100.00%> (+0.07%) ⬆️
src/cpp/cpp_typecheck_declaration.cpp 73.84% <100.00%> (+1.26%) ⬆️

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 4c2b413...9018306. 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.

If you added copies of the test to regression/cpp/ then you could get 100% diff coverage.

@tautschnig
Copy link
Collaborator Author

If you added copies of the test to regression/cpp/ then you could get 100% diff coverage.

Indeed, done! (Which of course required me expanding my changes in the C++ front-end - testing does help, after all ;-) )

@tautschnig
Copy link
Collaborator Author

#5679 needs to be merged first to make CI happy again.

We silently accepted these, as many cases would work fine in goto
programs. The included regression test, however, demonstrates where this
would fail an invariant during Boolean flattening (if run with
--pointer-check). GCC refuses void typed variables, and so should we.

Test originates from an SV-COMP task, reduced to this minimal example
using C-Reduce.
@tautschnig tautschnig merged commit cc16a46 into diffblue:develop Dec 21, 2020
@tautschnig tautschnig deleted the void branch December 21, 2020 16:45
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