-
-
Notifications
You must be signed in to change notification settings - Fork 33.6k
gh-142168: Initalize may be used but uninitialized stack_array. #142192
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
This comment was marked as resolved.
This comment was marked as resolved.
|
See my comment on the issue. There is prior art and initializing in this hot path to silence a false positive warning is not (my) preferred solution. |
|
Initialization in a hot path is not desired and it's also a false positive. I'm going to close this PR, sorry. |
|
IMO this change is a reasonable fix for the warnings. |
|
I think we should have checked the produced assembly to see whether this introduces a true overhead in an optimized build. Personally, I think the pragmas are fine (we do this elsewhere) but we could disable them in |
|
Well, we can check and then we know for this compiler and version we've checked. And are at the mercy of all compilers and versions that they hopefully behave the same - i.e. do not produce needless initialization code we've put in to silence a false positive warning. |
I think so, too. It is good to have less warnings. It is even better to have less false positive warnings :) |
|
OTOH, Footnotes
|
To stop the warning.
Reproduce steps: