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/110116] [12/13/14 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: verify_gimple failed
Date: Sun, 04 Jun 2023 22:17:12 +0000 [thread overview]
Message-ID: <bug-110116-4-FDxjbkvMqN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110116-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110116
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ICE on valid code at -O3 on |[12/13/14 Regression] ICE
|x86_64-linux-gnu: |on valid code at -O3 on
|verify_gimple failed |x86_64-linux-gnu:
| |verify_gimple failed
Last reconfirmed| |2023-06-04
Keywords| |ice-checking,
| |ice-on-valid-code,
| |needs-bisection
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Target Milestone|--- |12.4
Known to fail| |12.1.0, 12.2.0, 12.3.0,
| |13.1.0
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> It appears to be a recent regression.
It is not. `-O3 -fchecking=2` ICEs all the way back to GCC 12.1.0
Confirmed.
next prev parent reply other threads:[~2023-06-04 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 21:24 [Bug tree-optimization/110116] New: " zhendong.su at inf dot ethz.ch
2023-06-04 22:17 ` pinskia at gcc dot gnu.org [this message]
2023-06-05 6:51 ` [Bug tree-optimization/110116] [12/13/14 Regression] " rguenth at gcc dot gnu.org
2023-11-01 19:22 ` tkoenig at gcc dot gnu.org
2023-11-02 18:29 ` [Bug tree-optimization/110116] [12/13 " tkoenig at gcc dot gnu.org
2023-12-15 12:23 ` rguenth at gcc dot gnu.org
2024-05-08 11:56 ` 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-110116-4-FDxjbkvMqN@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).