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/114787] [13/14 Regression] wrong code at -O1 on x86_64-linux-gnu (the generated code hangs)
Date: Sat, 20 Apr 2024 23:10:17 +0000 [thread overview]
Message-ID: <bug-114787-4-NkWH5YFpBR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114787-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
Known to work| |12.1.0
Target Milestone|14.0 |13.3
Known to fail| |13.1.0
Summary|[14 Regression] wrong code |[13/14 Regression] wrong
|at -O1 on x86_64-linux-gnu |code at -O1 on
|(the generated code hangs) |x86_64-linux-gnu (the
| |generated code hangs)
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So with GCC 13, with `-fdump-tree-all-all`, we get the same wrong code as on
the trunk.
This is why I was I misunderstood thinking it was a target issue as I was
comparing the dumps between GCC 13 and the trunk with -all enabled but it was
broken in GCC 13 too.
Anyways I tested GCC 12.3.0 and it looks to be working there.
It would be useful to get another bisect done this time with `-O1
-fdump-tree-all-all` .
next prev parent reply other threads:[~2024-04-20 23:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 10:53 [Bug tree-optimization/114787] New: " zhendong.su at inf dot ethz.ch
2024-04-20 10:59 ` [Bug tree-optimization/114787] [14 Regression] " jakub at gcc dot gnu.org
2024-04-20 14:22 ` law at gcc dot gnu.org
2024-04-20 22:03 ` [Bug target/114787] " pinskia at gcc dot gnu.org
2024-04-20 23:03 ` [Bug tree-optimization/114787] " pinskia at gcc dot gnu.org
2024-04-20 23:10 ` pinskia at gcc dot gnu.org [this message]
2024-04-20 23:37 ` [Bug tree-optimization/114787] [13/14 " pinskia at gcc dot gnu.org
2024-04-20 23:50 ` pinskia at gcc dot gnu.org
2024-04-22 7:39 ` jakub at gcc dot gnu.org
2024-04-22 7:49 ` jakub at gcc dot gnu.org
2024-04-22 8:08 ` jakub at gcc dot gnu.org
2024-04-22 8:24 ` pinskia at gcc dot gnu.org
2024-04-22 9:09 ` jakub at gcc dot gnu.org
2024-04-22 12:45 ` jakub at gcc dot gnu.org
2024-04-22 13:01 ` hubicka at gcc dot gnu.org
2024-04-24 6:12 ` rguenth at gcc dot gnu.org
2024-04-24 6:47 ` rguenth at gcc dot gnu.org
2024-04-24 8:13 ` cvs-commit at gcc dot gnu.org
2024-04-24 8:14 ` [Bug tree-optimization/114787] [13 " rguenth at gcc dot gnu.org
2024-04-24 14:38 ` hubicka at gcc dot gnu.org
2024-05-06 13:15 ` cvs-commit at gcc dot gnu.org
2024-05-06 13:15 ` 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-114787-4-NkWH5YFpBR@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).