-
Notifications
You must be signed in to change notification settings - Fork 274
C front-end/KnR: generate nondet for missing arguments #5692
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
Conversation
Codecov ReportBase: 78.34% // Head: 78.34% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #5692 +/- ##
========================================
Coverage 78.34% 78.34%
========================================
Files 1644 1645 +1
Lines 190313 190359 +46
========================================
+ Hits 149097 149135 +38
- Misses 41216 41224 +8
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
This deviates quite a lot from the usual pattern: this would be the only place in the front-end where we pick nondeterministic semantics. |
Should we instead handle this case in goto-symex, translating |
5175c29
to
49db2a7
Compare
49db2a7
to
13b643c
Compare
The back-end does not know how to handle `nil`, and symex would also generate nondet in such cases, so do the same in the front-end.
13b643c
to
302d06a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At some point it needs to be replaced (frontend, goto, or symex). Having nil in the goto model doesn't seem right, and symex is certainly too late, IMO.
The back-end does not know how to handle
nil
, and symex would alsogenerate nondet in such cases, so do the same in the front-end.