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 tree-optimization/103281] [9/10/12 Regression] Dead Code Elimination Regression at -O3 (trunk vs 11.2.0)
Date: Tue, 16 Nov 2021 20:52:18 +0000 [thread overview]
Message-ID: <bug-103281-4-W4nU6dixuo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103281-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103281
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/12 Regression] Dead Code |[9/10/12 Regression] Dead
|Elimination Regression at |Code Elimination Regression
|-O3 (trunk vs 11.2.0) |at -O3 (trunk vs 11.2.0)
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I want to say we should defer this until after GCC 12 because this was only
> being optimized on accident. phiopt1
As you can see by this used to work between 4.9-8.0 and then regressed in GCC 9
and 10.
next prev parent reply other threads:[~2021-11-16 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 18:31 [Bug tree-optimization/103281] New: [12 " theodort at inf dot ethz.ch
2021-11-16 20:51 ` [Bug tree-optimization/103281] [9/12 " pinskia at gcc dot gnu.org
2021-11-16 20:52 ` pinskia at gcc dot gnu.org [this message]
2021-11-16 21:03 ` [Bug tree-optimization/103281] [9/10/12 " pinskia at gcc dot gnu.org
2021-11-16 21:16 ` pinskia at gcc dot gnu.org
2021-11-18 10:31 ` marxin at gcc dot gnu.org
2022-01-18 14:28 ` rguenth at gcc dot gnu.org
2022-05-27 9:46 ` [Bug tree-optimization/103281] [10/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:46 ` jakub at gcc dot gnu.org
2023-05-01 23:49 ` [Bug tree-optimization/103281] [10/12/13/14 " pinskia at gcc dot gnu.org
2023-08-07 5:47 ` [Bug tree-optimization/103281] [12/13/14 " pinskia at gcc dot gnu.org
2023-08-07 6:34 ` pinskia at gcc dot gnu.org
2023-08-07 6:34 ` pinskia at gcc dot gnu.org
2023-08-08 15:42 ` cvs-commit at gcc dot gnu.org
2023-08-08 15:43 ` pinskia at gcc dot gnu.org
2023-08-08 15:46 ` pinskia 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-103281-4-W4nU6dixuo@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).