public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107751] [11/12/13 regression] False positive -Wmaybe-uninitialized at -O0
Date: Fri, 18 Nov 2022 20:01:18 +0000 [thread overview]
Message-ID: <bug-107751-4-1qCGD64LDQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107751-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107751
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |11.4
Last reconfirmed| |2022-11-18
Summary|[11/12 regression] False |[11/12/13 regression] False
|positive |positive
|-Wmaybe-uninitialized at |-Wmaybe-uninitialized at
|-O0 |-O0
Ever confirmed|0 |1
Known to fail| |11.1.0, 12.2.0, 13.0
Status|UNCONFIRMED |NEW
Known to work| |10.4.0
Keywords| |needs-bisection
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.
next prev parent reply other threads:[~2022-11-18 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 13:31 [Bug c++/107751] New: [11/12 regression] False positive -Wmaybe-uninitialized alvinhochun at gmail dot com
2022-11-18 20:01 ` pinskia at gcc dot gnu.org [this message]
2022-11-18 20:03 ` [Bug c++/107751] [11/12/13 regression] False positive -Wmaybe-uninitialized at -O0 pinskia at gcc dot gnu.org
2022-11-18 20:06 ` [Bug tree-optimization/107751] " mpolacek at gcc dot gnu.org
2022-12-20 15:56 ` rguenth at gcc dot gnu.org
2023-05-29 10:07 ` [Bug tree-optimization/107751] [11/12/13/14 " 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-107751-4-1qCGD64LDQ@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).