public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88897] [10/11/12 Regression] Bogus maybe-uninitialized warning on class field (missed CSE)
Date: Sun, 20 Nov 2022 04:29:22 +0000 [thread overview]
Message-ID: <bug-88897-4-pcP7x10JIR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88897-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88897
Jeffrey A. Law <law at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at gcc dot gnu.org
Summary|[10/11/12/13 Regression] |[10/11/12 Regression] Bogus
|Bogus maybe-uninitialized |maybe-uninitialized warning
|warning on class field |on class field (missed CSE)
|(missed CSE) |
--- Comment #12 from Jeffrey A. Law <law at gcc dot gnu.org> ---
We're catching the previously missed CSE opportunity in fre1 now, and (of
course) we no longer get the bogus warning. Removing the 13 regression marker.
Finding and backporting the specific change seems like it's not worth it, but
leaving open with the other regression markers for now.
next prev parent reply other threads:[~2022-11-20 4:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-88897-4@http.gcc.gnu.org/bugzilla/>
2021-04-06 20:35 ` [Bug middle-end/88897] " msebor at gcc dot gnu.org
2021-04-06 20:47 ` [Bug middle-end/88897] [9/10/11 Regression] " msebor at gcc dot gnu.org
2021-04-08 14:25 ` rguenth at gcc dot gnu.org
2021-04-30 7:48 ` [Bug middle-end/88897] [9/10/11/12 " rguenth at gcc dot gnu.org
2021-06-01 8:12 ` rguenth at gcc dot gnu.org
2022-05-27 9:40 ` [Bug tree-optimization/88897] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:36 ` jakub at gcc dot gnu.org
2022-11-20 4:29 ` law at gcc dot gnu.org [this message]
2023-07-07 10:34 ` [Bug tree-optimization/88897] [11/12 " 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-88897-4-pcP7x10JIR@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).