public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97528] [9/10/11 Regression] ICE in decompose_automod_address, at rtlanal.c:6298 (arm-linux-gnueabihf) Date: Wed, 18 Nov 2020 16:12:01 +0000 [thread overview] Message-ID: <bug-97528-4-HqtkI1JSFK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97528-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97528 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- We have: (insn 7 6 9 2 (set (reg:SI 114 [ _3 ]) (ashift:SI (reg:SI 122 [ d ]) (const_int 1 [0x1]))) "pr97528-2.c":14:9 147 {*arm_shiftsi3} (expr_list:REG_DEAD (reg:SI 122 [ d ]) (nil))) ... (insn 12 25 24 2 (set (mem/c:V4HI (post_modify:SI (reg/v/f:SI 118 [ dst ]) (plus:SI (reg/v/f:SI 118 [ dst ]) (reg:SI 114 [ _3 ]))) [0 MEM[(short int[4] *)&c]+0 S8 A16]) (unspec:V4HI [ (reg:V4HI 117 [ _14 ]) ] UNSPEC_VST1)) "pr97528-2.c":13:5 2508 {neon_vst1v4hi} (expr_list:REG_INC (reg/v/f:SI 118 [ dst ]) (nil))) and combine attempts to propagate the shift into the insn: (insn 12 25 24 2 (set (mem/c:V4HI (post_modify:SI (reg/v/f:SI 118 [ dst ]) (plus:SI (mult:SI (reg:SI 122 [ d ]) (const_int 2 [0x2])) (reg/v/f:SI 118 [ dst ]))) [0 MEM[(short int[4] *)&c]+0 S8 A16]) (unspec:V4HI [ (reg:V4HI 117 [ _14 ]) ] UNSPEC_VST1)) "pr97528-2.c":13:5 2508 {neon_vst1v4hi} (expr_list:REG_INC (reg/v/f:SI 118 [ dst ]) (nil))) That is not valid RTL, as documented: Currently, the compiler can only handle second operands of the form (plus (reg) (reg)) and (plus (reg) (const_int)), where the first operand of the PLUS has to be the same register as the first operand of the *_MODIFY.
next prev parent reply other threads:[~2020-11-18 16:12 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-22 11:42 [Bug target/97528] New: [10/11 " doko at debian dot org 2020-10-22 11:52 ` [Bug target/97528] " rguenth at gcc dot gnu.org 2020-10-23 11:25 ` ktkachov at gcc dot gnu.org 2020-11-18 16:12 ` jakub at gcc dot gnu.org [this message] 2020-11-18 16:14 ` [Bug target/97528] [9/10/11 " jakub at gcc dot gnu.org 2020-11-20 11:27 ` cvs-commit at gcc dot gnu.org 2020-11-20 11:42 ` [Bug target/97528] [9/10 " jakub at gcc dot gnu.org 2020-11-25 11:56 ` cvs-commit at gcc dot gnu.org 2021-02-01 13:28 ` avieira at gcc dot gnu.org 2021-02-01 13:30 ` ktkachov at gcc dot gnu.org 2021-02-01 13:36 ` jakub at gcc dot gnu.org 2021-02-03 10:03 ` cvs-commit at gcc dot gnu.org 2021-02-03 18:32 ` cvs-commit at gcc dot gnu.org 2021-02-03 18:33 ` avieira at gcc dot gnu.org 2021-02-03 18:37 ` jakub 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-97528-4-HqtkI1JSFK@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).