public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329-g4f6bc28fc7dd86bd
Date: Tue, 01 Mar 2022 15:26:15 +0000 [thread overview]
Message-ID: <bug-103984-4-nGvyW3eCXc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103984-4@http.gcc.gnu.org/bugzilla/>
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 <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:ad66b03b3c84786e73e73f09be19977b8f3c4ea3
commit r12-7434-gad66b03b3c84786e73e73f09be19977b8f3c4ea3
Author: Jonathan Wakely <jwakely@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.
next prev parent reply other threads:[~2022-03-01 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 22:18 [Bug c++/103984] New: [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 slyfox at gcc dot gnu.org
2022-01-11 22:31 ` [Bug c++/103984] " pinskia at gcc dot gnu.org
2022-01-11 22:34 ` pinskia at gcc dot gnu.org
2022-01-12 7:39 ` rguenth at gcc dot gnu.org
2022-01-12 8:29 ` jakub at gcc dot gnu.org
2022-01-26 17:48 ` [Bug c++/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329 jason at gcc dot gnu.org
2022-01-26 18:35 ` jason at gcc dot gnu.org
2022-01-26 19:03 ` jason at gcc dot gnu.org
2022-01-26 19:25 ` [Bug middle-end/103984] " jason at gcc dot gnu.org
2022-03-01 15:04 ` marxin at gcc dot gnu.org
2022-03-01 15:26 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-15 14:22 ` [Bug middle-end/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329-g4f6bc28fc7dd86bd jakub at gcc dot gnu.org
2022-03-15 15:06 ` jakub at gcc dot gnu.org
2022-03-15 15:16 ` jakub at gcc dot gnu.org
2022-03-15 15:55 ` jakub at gcc dot gnu.org
2022-03-15 16:55 ` jakub at gcc dot gnu.org
2022-03-15 18:00 ` jakub at gcc dot gnu.org
2022-03-16 8:47 ` jakub at gcc dot gnu.org
2022-03-16 8:58 ` jakub at gcc dot gnu.org
2022-03-17 8:26 ` cvs-commit at gcc dot gnu.org
2022-03-17 8:46 ` jakub at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-103984-4-nGvyW3eCXc@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).