public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/109676] [13/14 regression] ICE in simplify_subreg, at simplify-rtx.cc:7426 when building firefox with -O2 -march=alderlake -g since r13-3378-gf6c168f8c06047
Date: Sat, 29 Apr 2023 23:31:47 +0000 [thread overview]
Message-ID: <bug-109676-4-6DhEhXGptm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109676-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109676
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
Summary|[13/14 regression] ICE in |[13/14 regression] ICE in
|simplify_subreg, at |simplify_subreg, at
|simplify-rtx.cc:7426 when |simplify-rtx.cc:7426 when
|building firefox with -O2 |building firefox with -O2
|-march=alderlake -g |-march=alderlake -g since
| |r13-3378-gf6c168f8c06047
CC| |jamborm at gcc dot gnu.org
--- Comment #10 from Sam James <sjames at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #8)
> I suspect it was r13-1607-gc3ed9e0d6e96d8697e4bab994 which might have
> exposed this latent issue ...
Bisect says r13-3378-gf6c168f8c06047 and a revert on trunk works but probably
latent still
next prev parent reply other threads:[~2023-04-29 23:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 1:29 [Bug rtl-optimization/109676] New: [13/14 regression] ICE in simplify_subreg, at simplify-rtx.cc:7426 when building firefox with -O2 -march=alderlake -g sjames at gcc dot gnu.org
2023-04-29 2:33 ` [Bug debug/109676] " pinskia at gcc dot gnu.org
2023-04-29 2:48 ` pinskia at gcc dot gnu.org
2023-04-29 4:26 ` sjames at gcc dot gnu.org
2023-04-29 20:22 ` sjames at gcc dot gnu.org
2023-04-29 20:51 ` pinskia at gcc dot gnu.org
2023-04-29 20:51 ` pinskia at gcc dot gnu.org
2023-04-29 20:57 ` pinskia at gcc dot gnu.org
2023-04-29 21:05 ` pinskia at gcc dot gnu.org
2023-04-29 21:08 ` pinskia at gcc dot gnu.org
2023-04-29 21:56 ` pinskia at gcc dot gnu.org
2023-04-29 23:31 ` sjames at gcc dot gnu.org [this message]
2023-05-01 9:13 ` [Bug debug/109676] [13/14 regression] ICE in simplify_subreg, at simplify-rtx.cc:7426 when building firefox with -O2 -march=alderlake -g since r13-3378-gf6c168f8c06047 jakub at gcc dot gnu.org
2023-05-01 11:21 ` jakub at gcc dot gnu.org
2023-05-01 13:01 ` jakub at gcc dot gnu.org
2023-05-02 6:24 ` rguenth at gcc dot gnu.org
2023-05-04 7:37 ` cvs-commit at gcc dot gnu.org
2023-05-04 7:44 ` cvs-commit at gcc dot gnu.org
2023-07-27 9:25 ` rguenth at gcc dot gnu.org
2023-11-06 1:36 ` 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-109676-4-6DhEhXGptm@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).