public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roger at nextmovesoftware dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106303] [13 Regression] ICE on valid code at -O3 with -fno-inline-small-functions on x86_64-linux-gnu: in extract_insn, at recog.cc:2791 since r13-1607-gc3ed9e0d6e96d869
Date: Fri, 22 Jul 2022 08:23:52 +0000 [thread overview]
Message-ID: <bug-106303-4-hxu37hdgtk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106303-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106303
Roger Sayle <roger at nextmovesoftware dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zsojka at seznam dot cz
--- Comment #7 from Roger Sayle <roger at nextmovesoftware dot com> ---
*** Bug 106404 has been marked as a duplicate of this bug. ***
next prev parent reply other threads:[~2022-07-22 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 16:34 [Bug rtl-optimization/106303] New: ICE on valid code at -O3 with -fno-inline-small-functions on x86_64-linux-gnu: in extract_insn, at recog.cc:2791 zhendong.su at inf dot ethz.ch
2022-07-14 16:42 ` [Bug target/106303] [13 Regression] " pinskia at gcc dot gnu.org
2022-07-15 7:43 ` [Bug target/106303] [13 Regression] ICE on valid code at -O3 with -fno-inline-small-functions on x86_64-linux-gnu: in extract_insn, at recog.cc:2791 since r13-1607-gc3ed9e0d6e96d869 marxin at gcc dot gnu.org
2022-07-15 14:47 ` roger at nextmovesoftware dot com
2022-07-15 15:20 ` roger at nextmovesoftware dot com
2022-07-17 21:49 ` zhendong.su at inf dot ethz.ch
2022-07-20 16:31 ` roger at nextmovesoftware dot com
2022-07-20 17:41 ` hjl.tools at gmail dot com
2022-07-20 17:44 ` hjl.tools at gmail dot com
2022-07-22 8:23 ` roger at nextmovesoftware dot com [this message]
2022-07-22 13:27 ` roger at nextmovesoftware dot com
2022-07-24 11:24 ` cvs-commit at gcc dot gnu.org
2022-07-25 16:58 ` roger at nextmovesoftware dot com
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-106303-4-hxu37hdgtk@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).