-
Notifications
You must be signed in to change notification settings - Fork 22
Don't use switch fallthrough #423
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
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,16 +6,12 @@ RWStructuredBuffer<uint> Out : register(u1); | |
void main(uint3 threadID : SV_DispatchThreadID) { | ||
bool B1 = false; | ||
|
||
switch (value[threadID.x]) { | ||
case 0: // threads 0 and 1; result is number of active lanes (2) | ||
Out[threadID.x + 4] = WaveActiveCountBits(true); // threads 0 and 1 | ||
case 2: | ||
B1 = true; // set b1 to true for thread 3 | ||
break; | ||
default: | ||
Out[threadID.x + 4] = WaveActiveCountBits(false); // thread 2; expect 0 | ||
break; | ||
} | ||
if (value[threadID.x] == 0) | ||
Out[threadID.x + 4] = WaveActiveCountBits(true); // threads 0 and 1 | ||
if (value[threadID.x] == 0 || value[threadID.x] == 1) | ||
|
||
B1 = true; // set b1 to true for thread 3 | ||
|
||
else | ||
Out[threadID.x + 4] = WaveActiveCountBits(false); // thread 2; expect 0 | ||
|
||
// should be 3 because B1 set to true for threads 0,1, and 3. | ||
uint Count = WaveActiveCountBits(B1); | ||
Out[threadID.x] = Count; | ||
|
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.
While this matches the behavior of the replaced switch, the comment seemed to imply that thread
1
was meant to also go through this branch. The later comment also seems to assume this ("result for all threads is true because B1 is true for threads 0-2"). However thread numbers are translated through the LUTvalue
, which is[0, 0, 1, 2]
.Even accounting for this looked up value, the removed and remaining comments don't seem to align with the test's design and expected behavior. The test seems to be written in a way to make it a bit confusing on purpose.
I don't understand the intention behind these odd details of the test. Was this a mistake in the code or in the comments?
It would be nice to have an explanatory comment for the test design.
The second test has a similar issue.