public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107751] [11/12/13 regression] False positive -Wmaybe-uninitialized at -O0
Date: Fri, 18 Nov 2022 20:06:02 +0000 [thread overview]
Message-ID: <bug-107751-4-ZpW5fDLfye@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
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
CC| |mpolacek at gcc dot gnu.org
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r11-959-gb825a22890740f:
commit b825a22890740f341eae566af27e18e528cd29a7
Author: Martin Sebor <msebor@redhat.com>
Date: Thu Jun 4 16:06:10 2020 -0600
Implement a solution for PR middle-end/10138 and PR middle-end/95136.
PR middle-end/10138 - warn for uninitialized arrays passed as const
arguments
PR middle-end/95136 - missing -Wuninitialized on an array access with a
variable offset
next prev parent reply other threads:[~2022-11-18 20:06 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 ` [Bug c++/107751] [11/12/13 regression] False positive -Wmaybe-uninitialized at -O0 pinskia at gcc dot gnu.org
2022-11-18 20:03 ` pinskia at gcc dot gnu.org
2022-11-18 20:06 ` mpolacek at gcc dot gnu.org [this message]
2022-12-20 15:56 ` [Bug tree-optimization/107751] " 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-ZpW5fDLfye@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).