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 target/106876] [13 Regression] ICE in extract_insn, at recog.cc:2791 since r13-465-g4df735e01e319997
Date: Thu, 08 Sep 2022 01:31:31 +0000 [thread overview]
Message-ID: <bug-106876-4-BKiCoAS5qy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106876-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106876
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |13.0
Keywords| |ice-on-valid-code
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #1)
> Started with r13-465-g4df735e01e319997.
That might just allowed the testcase to be accepted. I suspect there might be
another one which is accepted before that ...
next prev parent reply other threads:[~2022-09-08 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 17:19 [Bug c++/106876] New: [13 Regression] ICE in extract_insn, at recog.cc:2791 gscfq@t-online.de
2022-09-07 19:41 ` [Bug target/106876] [13 Regression] ICE in extract_insn, at recog.cc:2791 since r13-465-g4df735e01e319997 marxin at gcc dot gnu.org
2022-09-08 1:31 ` pinskia at gcc dot gnu.org [this message]
2022-09-08 1:34 ` [Bug target/106876] ICE in extract_insn with -mforce-indirect-call -fPIC -fprofile-generate pinskia at gcc dot gnu.org
2022-09-08 1:35 ` [Bug target/106876] ICE in extract_insn with -mforce-indirect-call -fPIC and TLS pinskia at gcc dot gnu.org
2022-09-08 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-106876-4-BKiCoAS5qy@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).