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/112766] [14 regression] spurious -Wmaybe-uninitialized with array new
Date: Wed, 29 Nov 2023 17:04:00 +0000 [thread overview]
Message-ID: <bug-112766-4-1VGS2dIWUV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112766-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112766
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.0
Status|UNCONFIRMED |NEW
Keywords| |diagnostic
CC| |mpolacek at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
Component|c++ |tree-optimization
Last reconfirmed| |2023-11-29
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r14-4089:
commit d45ddc2c04e471d0dcee016b6edacc00b8341b16
Author: Richard Biener <rguenther@suse.de>
Date: Thu Sep 14 13:06:51 2023 +0200
tree-optimization/111294 - backwards threader PHI costing
next prev parent reply other threads:[~2023-11-29 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 16:54 [Bug c++/112766] New: " sss@li-snyder.org
2023-11-29 17:04 ` mpolacek at gcc dot gnu.org [this message]
2023-11-30 9:01 ` [Bug tree-optimization/112766] [14 regression] spurious -Wmaybe-uninitialized with array new since r14-4089 rguenth at gcc dot gnu.org
2023-11-30 9:50 ` rguenth at gcc dot gnu.org
2023-11-30 12:35 ` cvs-commit at gcc dot gnu.org
2023-11-30 12:35 ` rguenth 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-112766-4-1VGS2dIWUV@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).