-
Notifications
You must be signed in to change notification settings - Fork 273
Remove Throwing-NULL check from goto_check_ct #6685
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
Remove Throwing-NULL check from goto_check_ct #6685
Conversation
This check was introduced in d2713b2, with no particular reason that it should be enabled unconditionally. The test included in that commit has --pointer-check set, suggesting that this always was the desired behaviour. It was, however, only intended for the Java front-end: for the C language, "throw" is not relevant, and C++ permits throwing NULL. Therefore, remove this check from goto_check_ct.
bae7653
to
fe903fd
Compare
@@ -2170,27 +2170,6 @@ void goto_check_ct::goto_check( | |||
} | |||
else if(i.is_throw()) | |||
{ | |||
if( |
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.
Shouldn't that go into java_bytecode/goto_check_java
then?
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.
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.
And then also goto_check_java
actually has this code. I previously made it conditional on --pointer-check
in there, just to realise that it actually is dead code.
Codecov Report
@@ Coverage Diff @@
## develop #6685 +/- ##
========================================
Coverage 76.82% 76.82%
========================================
Files 1582 1582
Lines 182767 182758 -9
========================================
Hits 140403 140403
+ Misses 42364 42355 -9
Continue to review full report at Codecov.
|
This check was introduced in d2713b2, with no particular reason that
it should be enabled unconditionally. The test included in that commit
has --pointer-check set, suggesting that this always was the desired
behaviour. It was, however, only intended for the Java front-end: for
the C language, "throw" is not relevant, and C++ permits throwing NULL.
Therefore, remove this check from goto_check_ct.