public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100106] [10/11 Regression] ICE in gen_movdi, at config/arm/arm.md:6187 since r10-2840-g70cdb21e Date: Fri, 16 Apr 2021 07:09:09 +0000 [thread overview] Message-ID: <bug-100106-4-wcKqYomUlc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100106-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100106 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Priority|P3 |P2 Last reconfirmed| |2021-04-16 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. #1 0x0000000001d9f1c5 in gen_movdi (operand0=0x7ffff63ae390, operand1=0x7ffff63ae480) at /home/rguenther/src/trunk/gcc/config/arm/arm.md:6187 6187 gcc_checking_assert (aligned_operand (operands[1], DImode)); (gdb) p debug_rtx (operands[1]) (mem/u/c:DI (reg/f:SI 114) [0 S8 A32]) I think the bug is that /* Use the subreg machinery either to narrow OP0 to the required words or to cope with mode punning between equal-sized modes. In the latter case, use subreg on the rhs side, not lhs. */ rtx sub; HOST_WIDE_INT regnum; poly_uint64 regsize = REGMODE_NATURAL_SIZE (GET_MODE (op0)); if (known_eq (bitnum, 0U) && known_eq (bitsize, GET_MODE_BITSIZE (GET_MODE (op0)))) { sub = simplify_gen_subreg (GET_MODE (op0), value, fieldmode, 0); if (sub) { if (reverse) sub = flip_storage_order (GET_MODE (op0), sub); here simplify_gen_subreg simplifies (subreg:DI ((mem/u/c:SC (reg/f:SI 114) [0 S8 A32])) to (mem/u/c:DI (reg/f:SI 114) [0 S8 A32]) but SCmode has different alignment requirement than DImode.
next prev parent reply other threads:[~2021-04-16 7:09 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 21:06 [Bug target/100106] New: " acoplan at gcc dot gnu.org 2021-04-15 21:06 ` [Bug target/100106] " acoplan at gcc dot gnu.org 2021-04-16 7:09 ` rguenth at gcc dot gnu.org [this message] 2021-04-16 7:13 ` rguenth at gcc dot gnu.org 2021-04-20 6:00 ` bernd.edlinger at hotmail dot de 2021-04-27 15:48 ` [Bug target/100106] [10/11/12 " cvs-commit at gcc dot gnu.org 2021-04-27 15:51 ` [Bug target/100106] [10/11 " edlinger at gcc dot gnu.org 2021-07-19 11:59 ` rguenth at gcc dot gnu.org 2022-04-07 10:39 ` cvs-commit at gcc dot gnu.org 2022-04-08 10:20 ` [Bug target/100106] [10 " rearnsha at gcc dot gnu.org 2022-06-28 10:44 ` jakub at gcc dot gnu.org 2023-05-25 2:46 ` cvs-commit at gcc dot gnu.org 2023-07-07 9:35 ` rguenth 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-100106-4-wcKqYomUlc@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: linkBe 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).