[Bug middle-end/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329-g4f6bc28fc7dd86bd

[cvs-commit at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103984

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <r...@gcc.gnu.org>:

https://gcc.gnu.org/g:ad66b03b3c84786e73e73f09be19977b8f3c4ea3

commit r12-7434-gad66b03b3c84786e73e73f09be19977b8f3c4ea3
Author: Jonathan Wakely <jwak...@redhat.com>
Date:   Tue Mar 1 09:33:21 2022 +0000

    libstdc++: Fix -Wmaybe-uninitialized false positive [PR103984]

    This fixes a false positive warning seen with LTO:

    12/bits/regex_compiler.tcc:443:32: error: '__last_char._M_char' may be used
uninitialized [-Werror=maybe-uninitialized]

    Given that the std::regex code is not very efficient anyway, the
    overhead of initializing this byte should be minimal.

    libstdc++-v3/ChangeLog:

            PR middle-end/103984
            * include/bits/regex_compiler.h (_BracketMatcher::_M_char): Use
            default member initializer.