public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66358] [5/6 Regression] [SH] ICE: in extract_constrain_insn, at recog.c:2232 Date: Thu, 18 Jun 2015 04:21:00 -0000 [thread overview] Message-ID: <bug-66358-4-L0jvcJX8VC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66358-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66358 --- Comment #14 from Oleg Endo <olegendo at gcc dot gnu.org> --- It seems the problem is adjacent insns that need R0: (insn 10503 2627 2628 402 (set (reg:SI 2424) (sign_extend:SI (mem:QI (plus:SI (reg/v/f:SI 243 [ p2 ]) (const_int 2 [0x2])) [0 MEM[(unsigned char *)p2_97 + 2B]+0 S1 A8]))) ../../ORIG/trunk/libiberty/regex.c:7109 232 {*extendqisi2_compact_mem_disp} (nil)) (note 2628 10503 10505 402 NOTE_INSN_DELETED) (insn 10505 2628 2629 402 (set (reg:SI 2425) (sign_extend:SI (mem:QI (plus:SI (reg/f:SI 774 [ D.8751 ]) (const_int 5 [0x5])) [0 MEM[(unsigned char *)_1000 + 5B]+0 S1 A8]))) ../../ORIG/trunk/libiberty/regex.c:7109 232 {*extendqisi2_compact_mem_disp} (nil)) (note 2629 10505 2631 402 NOTE_INSN_DELETED) (note 2631 2629 10507 402 NOTE_INSN_DELETED) (insn 10507 2631 2633 402 (set (reg:SI 147 t) (eq:SI (and:SI (reg:SI 2424) (reg:SI 2425)) (const_int 0 [0]))) ../../ORIG/trunk/libiberty/regex.c:7109 1 {tstsi_t} (expr_list:REG_DEAD (reg:SI 2425) (expr_list:REG_DEAD (reg:SI 2424) (nil)))) In insn 10503 reg 2424 will be allocated to R0 and will remain live until insn 10507. Reload then fails to insert a move insn R0 -> other reg after insn 10503 and R0 allocation for insn 10505 becomes impossible. I've observed this issue already a while ago. I think this condition can be improved using some sort of linear register allocator for R0-insns.
next prev parent reply other threads:[~2015-06-18 4:21 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-01 7:41 [Bug target/66358] New: " kkojima at gcc dot gnu.org 2015-06-01 7:46 ` [Bug target/66358] " kkojima at gcc dot gnu.org 2015-06-01 12:50 ` olegendo at gcc dot gnu.org 2015-06-01 13:24 ` kkojima at gcc dot gnu.org 2015-06-01 14:01 ` rguenth at gcc dot gnu.org 2015-06-01 18:35 ` olegendo at gcc dot gnu.org 2015-06-01 22:44 ` kkojima at gcc dot gnu.org 2015-06-02 21:00 ` olegendo at gcc dot gnu.org 2015-06-02 23:55 ` kkojima at gcc dot gnu.org 2015-06-03 9:04 ` olegendo at gcc dot gnu.org 2015-06-03 11:29 ` olegendo at gcc dot gnu.org 2015-06-03 23:27 ` kkojima at gcc dot gnu.org 2015-06-15 11:48 ` glaubitz at physik dot fu-berlin.de 2015-06-18 4:21 ` olegendo at gcc dot gnu.org [this message] 2015-06-22 12:07 ` rguenth at gcc dot gnu.org 2015-07-16 9:25 ` rguenth at gcc dot gnu.org 2015-08-11 7:39 ` dcb314 at hotmail dot com 2015-08-11 7:42 ` dcb314 at hotmail dot com 2021-05-14 9:47 ` [Bug target/66358] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:06 ` rguenth at gcc dot gnu.org 2022-05-27 9:35 ` [Bug target/66358] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:31 ` jakub at gcc dot gnu.org 2023-07-07 10:30 ` [Bug target/66358] [11/12/13/14 " 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-66358-4-L0jvcJX8VC@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).