-
Notifications
You must be signed in to change notification settings - Fork 14.9k
[Sema] Diagnose use of if/else-if condition variable inside else-if/else branch(s) #156436
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
Open
arrowten
wants to merge
1
commit into
llvm:main
Choose a base branch
from
arrowten:fix/145506-warn-conditional-scope
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+106
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,74 @@ | ||
// RUN: %clang_cc1 -fsyntax-only -verify -Wconditional-scope -DTEST_1 %s | ||
// RUN: %clang_cc1 -fsyntax-only -verify -Wconditional-scope -DTEST_2 %s | ||
// RUN: %clang_cc1 -fsyntax-only -verify -Wconditional-scope -DTEST_3 %s | ||
|
||
int *get_something(); | ||
int *get_something_else(); | ||
int *get_something_else_again(); | ||
int *get_something_else_again_now(); | ||
|
||
#ifdef TEST_1 | ||
|
||
int test() { | ||
if (int *ptr = get_something()) { | ||
return ptr[0] * ptr[0]; | ||
} | ||
// expected-warning@+1{{variable ptr declared in 'if' block is either false or null}} | ||
else if (int *ptr2 = get_something_else()) { | ||
return ptr[0] * ptr2[0]; | ||
} | ||
// expected-warning@+1{{variable ptr2 declared in 'if' block is either false or null}} | ||
else if (int* ptr3 = get_something_else_again()) { | ||
return ptr[0] * ptr2[0] * ptr3[0]; | ||
} | ||
// expected-warning@+1{{variable ptr3 declared in 'if' block is either false or null}} | ||
else if (int *ptr4 = get_something_else_again_now()) { | ||
return ptr[0] * ptr2[0] * ptr3[0] * ptr4[0]; | ||
} | ||
else { | ||
return -1; | ||
} | ||
} | ||
|
||
#endif | ||
|
||
#ifdef TEST_2 | ||
|
||
int test() { | ||
if (int *ptr = get_something()) { | ||
return ptr[0] * ptr[0]; | ||
} | ||
// expected-warning@+1{{variable ptr declared in 'if' block is either false or null}} | ||
else if (int *ptr2 = get_something_else()) { | ||
return ptr2[0] * ptr2[0]; | ||
} | ||
// expected-warning@+1{{variable ptr2 declared in 'if' block is either false or null}} | ||
else if (int* ptr3 = get_something_else_again()) { | ||
return ptr[0] * ptr2[0] * ptr3[0]; | ||
} | ||
else { | ||
return -1; | ||
} | ||
} | ||
|
||
#endif | ||
|
||
#ifdef TEST_3 | ||
|
||
int test() { | ||
if (int *ptr = get_something()) { | ||
return ptr[0] * ptr[0]; | ||
} | ||
else if (int *ptr2 = get_something_else()) { | ||
return ptr2[0] * ptr2[0]; | ||
} | ||
// expected-warning@+1{{variable ptr2 declared in 'if' block is either false or null}} | ||
else if (int* ptr3 = get_something_else_again()) { | ||
return ptr2[0] * ptr2[0] * ptr3[0]; | ||
} | ||
else { | ||
return -1; | ||
} | ||
} | ||
|
||
#endif |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Hmm.. This whole thing is a little too pattern matchy for me, and without a visitor is now going to just do this the 'hard' way.
I think
ActOnIfStmt
is probably the wrong place for this entirely, its too late at this point. We should probably do it somewhere inActOnVariableDeclarator
(or something like that?) and check the scope.Scope
itself doesn't do diagnostics, but will have the context that we are 'in' a for loop, and can store the condition variable.As this is written, an
if-else
chain ends up having the lastelse
body checked N times. In addition to everything else, thats just wrong.Instead, when we see a var-reference being created, we should be checking all the active
if
statements, and be variables that we've stored along the way.