Fix GCC -Wmaybe-uninitialized warnings
#80615
Merged
Conversation
This file contains 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
akien-mga
added
bug
topic:core
topic:buildsystem
cherrypick:4.1
akien-mga
changed the title
Wmaybe-uninitialized warnings
akien-mga
changed the title
Wmaybe-uninitialized warnings-Wmaybe-uninitialized warnings
akien-mga
force-pushed
the
gcc-fix-Wmaybe-uninitialized-warnings
branch
from
a35804f to
efdff9c
Compare
lawnjelly
approved these changes
Aug 14, 2023
|
Cherry-picked for 4.1.2 (except for the navigation tests which aren't present in 4.1). |
YuriSizov
removed
the
cherrypick:4.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Raised while working on #80612, not sure if it's because disabling exception handling lets GCC find different warnings, or if it's just due to trigger a full codebase rebuild from scratch and thus not reusing already compiled objects.