Initialize the npf_format_spec_t struct to prevent a spurious warning #277
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
This prevents a `-Wmaybe-uninitialized` warning on GCC, where aggressive optimizations can make the `#pragma` to suppress the warnings not work. Remove the `#pragma` to suppress the warning as it should no longer occur.
|
Let me know if you'd prefer to limit the initialisation to only happen on recent GCC versions or anything like that - or if you'd prefer to look at the |
|
Closing in favour of #278 |
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.
addresses #276
This prevents a
-Wmaybe-uninitializedwarning on GCC, where aggressive optimizations can make the#pragmato suppress the warnings not work.Remove the
#pragmato suppress the warning as it should no longer occur.