public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109636] [14 Regression] ICE: in paradoxical_subreg_p, at rtl.h:3205 with -O -mcpu=a64fx
Date: Thu, 27 Apr 2023 08:26:04 +0000 [thread overview]
Message-ID: <bug-109636-4-RgAnaDLHGq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109636-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109636
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-04-27
Status|UNCONFIRMED |NEW
CC| |rsandifo at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from ktkachov at gcc dot gnu.org ---
Confirmed. The operand that's blowing it up is:
(subreg:V2DI (reg/v:OI 97 [ w ]) 16)
at
rtx sve_op1 = simplify_gen_subreg (sve_mode, operands[1], <MODE>mode, 0);
simplify_gen_subreg, lowpart_subreg, copy_to_mode_reg and force_reg all ICE :(
next prev parent reply other threads:[~2023-04-27 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 17:28 [Bug target/109636] New: " zsojka at seznam dot cz
2023-04-26 19:08 ` [Bug target/109636] " pinskia at gcc dot gnu.org
2023-04-26 22:26 ` ktkachov at gcc dot gnu.org
2023-04-26 22:42 ` pinskia at gcc dot gnu.org
2023-04-27 8:26 ` ktkachov at gcc dot gnu.org [this message]
2023-04-28 8:17 ` ktkachov at gcc dot gnu.org
2023-04-28 8:25 ` rsandifo at gcc dot gnu.org
2023-04-28 14:41 ` ktkachov at gcc dot gnu.org
2024-01-10 8:01 ` [Bug target/109636] [14 Regression] ICE: in paradoxical_subreg_p, at rtl.h:3205 with -O -march=armv8.4-a+sve pinskia at gcc dot gnu.org
2024-01-10 8:03 ` pinskia at gcc dot gnu.org
2024-01-10 8:05 ` pinskia at gcc dot gnu.org
2024-01-12 17:55 ` tnfchris at gcc dot gnu.org
2024-01-24 15:58 ` cvs-commit at gcc dot gnu.org
2024-01-24 16:01 ` tnfchris 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-109636-4-RgAnaDLHGq@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).