public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106101] [12/13 Regression] ICE in reg_bitfield_target_p since r12-4428-g147ed0184f403b
Date: Tue, 19 Jul 2022 11:53:22 +0000 [thread overview]
Message-ID: <bug-106101-4-yixz0Bfc6J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106101-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106101
--- Comment #11 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
I've tried to change our movstrict backend patterns to use a predicate on the
dest operand which enforces a subreg. However, since reload strips the subreg
away when assigning hard regs we end up with a STRICT_LOW_PART of a reg again.
At least after reload something like this should be acceptable - right?
298r.ira:
(insn 8 16 17 3 (set (strict_low_part (subreg:SI (reg/v:DI 64 [ e ]) 4))
(const_int 0 [0])) "t.cc":37:17 1485 {movstrictsi}
(nil))
299r.reload:
(insn 8 16 17 3 (set (strict_low_part (reg:SI 11 %r11 [orig:64 e+4 ] [64]))
(mem/u/c:SI (symbol_ref/u:DI ("*.LC0") [flags 0x2]) [0 S4 A32]))
"t.cc":37:17 1485 {movstrictsi}
(nil))
next prev parent reply other threads:[~2022-07-19 11:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 9:22 [Bug rtl-optimization/106101] New: [12/13 Regression] ICE in reg_bitfield_target_p rguenth at gcc dot gnu.org
2022-06-27 9:22 ` [Bug rtl-optimization/106101] " rguenth at gcc dot gnu.org
2022-06-27 9:22 ` rguenth at gcc dot gnu.org
2022-06-27 9:26 ` rguenth at gcc dot gnu.org
2022-06-27 15:10 ` segher at gcc dot gnu.org
2022-06-28 6:57 ` [Bug target/106101] " rguenth at gcc dot gnu.org
2022-06-28 15:03 ` segher at gcc dot gnu.org
2022-06-28 16:58 ` segher at gcc dot gnu.org
2022-06-29 9:11 ` rguenth at gcc dot gnu.org
2022-06-29 15:48 ` segher at gcc dot gnu.org
2022-07-08 13:56 ` [Bug target/106101] [12/13 Regression] ICE in reg_bitfield_target_p since r12-4428-g147ed0184f403b marxin at gcc dot gnu.org
2022-07-14 10:02 ` krebbel at gcc dot gnu.org
2022-07-19 11:53 ` krebbel at gcc dot gnu.org [this message]
2022-08-24 6:46 ` krebbel at gcc dot gnu.org
2022-08-24 11:57 ` segher at gcc dot gnu.org
2022-08-25 12:40 ` cvs-commit at gcc dot gnu.org
2022-08-25 13:02 ` krebbel at gcc dot gnu.org
2022-08-25 13:55 ` krebbel at gcc dot gnu.org
2022-08-25 15:03 ` segher at gcc dot gnu.org
2023-01-17 15:25 ` [Bug target/106101] [12 " rguenth at gcc dot gnu.org
2023-01-17 15:26 ` rguenth at gcc dot gnu.org
2023-01-23 7:58 ` cvs-commit at gcc dot gnu.org
2023-03-01 13:28 ` rguenth at gcc dot gnu.org
2023-10-10 14:29 ` fw at gcc dot gnu.org
2023-10-10 17:36 ` pinskia at gcc dot gnu.org
2023-10-10 17:39 ` pinskia at gcc dot gnu.org
2023-10-11 6:46 ` fw 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-106101-4-yixz0Bfc6J@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).