Fix CI failure on maybe-uninitialized compiler warning #205
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.
Some GCC versions warn:
These are false positives. However, in combination with the
-Werror
compiler option, they cause a CI failure on GCC 14 / Ubuntu.Commits 8d8d752 and 714f210 attempted to fix the failure by providing the
-Wno-error=maybe-uninitialized
compiler option. However, they did not fix the failure on Ubuntu, and they caused another failure on clang 18 on macOS:This pull request solves the issue in a different way: by moving the initialization of
y2_start
andy2_end
closer to where they are used (within the sameif
statement), the warning goes away. Then, the compiler option-Wno-error=maybe-uninitialized
is not needed anymore.