public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17643] [3.3/3.4/4.0 Regression] ICE in propagate_one_insn, at flow.c:1582 Date: Mon, 20 Dec 2004 04:36:00 -0000 [thread overview] Message-ID: <20041220043614.24024.qmail@sourceware.org> (raw) In-Reply-To: <20040923220428.17643.markus@oberhumer.com> ------- Additional Comments From danglin at gcc dot gnu dot org 2004-12-20 04:36 ------- Hmmm, why "-mportable-runtime"? This was intended I believe for PA 1.0 chips in embedded applications and isn't used or tested much any more. I can only duplicate on linux. At the moment, I don't know how this can happen. We have the following insn when the ICE occurs: (insn 36 16 37 0 (set (reg:SI 2 %r2) (mem:SI (plus:SI (reg/f:SI 30 %r30) (const_int -20 [0xffffffec])) [0 S4 A32])) -1 (nil) (nil)) (insn 37 36 17 0 (unspec_volatile [ (const_int 2 [0x2]) ] 0) -1 (nil) (nil)) (call_insn/j 17 37 18 0 (parallel [ (set (reg:SI 28 %r28) (call (mem:SI (reg:SI 22 %r22) [0 S4 A32]) (const_int 16 [0x10]))) (clobber (reg:SI 1 %r1)) (clobber (reg:SI 2 %r2)) (use (const_int 1 [0x1])) ]) 207 {call_val_reg} (insn_list:REG_DEP_ANTI 13 (insn_list:REG_DEP_TRUE 16 (nil))) (expr_list:REG_DEAD (reg:SI 26 %r26 [ size ]) (expr_list:REG_DEAD (reg:SI 22 %r22) (expr_list:REG_UNUSED (reg:SI 2 %r2) (expr_list:REG_UNUSED (reg:SI 1 %r1) (nil))))) (expr_list:REG_DEP_TRUE (use (reg:SI 26 %r26 [ size ])) (nil))) (barrier 18 17 20) (note 20 18 33 NOTE_INSN_FUNCTION_END) (note 33 20 0 NOTE_INSN_DELETED) $5 = void Somehow, it looks as if the epilogue has been emitted in the wrong place (i.e., before insn 17 which is in the body of the function. It looks to me like this is caused by thread_prologue_and_epilogue_insns treating insn 17 as a sibling call. The hpux port doesn't allow sibcalls in the portable runtime. I think I see how to fix this but I'm still wonder why you would want to use -mportable-runtime on linux. The call sequences are much less efficient. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17643
next prev parent reply other threads:[~2004-12-20 4:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-23 22:04 [Bug target/17643] New: " markus at oberhumer dot com 2004-09-23 22:05 ` [Bug target/17643] " markus at oberhumer dot com 2004-11-30 19:56 ` markus at oberhumer dot com 2004-12-06 20:54 ` [Bug target/17643] [3.3/3.4/4.0 Regression] " belyshev at lubercy dot com 2004-12-20 1:09 ` steven at gcc dot gnu dot org 2004-12-20 4:36 ` danglin at gcc dot gnu dot org [this message] 2004-12-20 4:41 ` danglin at gcc dot gnu dot org 2004-12-20 4:49 ` [Bug target/17643] " pinskia at gcc dot gnu dot org 2004-12-20 5:27 ` belyshev at lubercy dot com 2004-12-20 5:28 ` [Bug target/17643] [3.3/3.4/4.0 Regression] " pinskia at gcc dot gnu dot org 2004-12-27 0:21 ` cvs-commit at gcc dot gnu dot org 2004-12-27 1:08 ` cvs-commit at gcc dot gnu dot org 2004-12-27 2:42 ` [Bug target/17643] [3.3 " pinskia at gcc dot gnu dot org 2004-12-27 2:56 ` cvs-commit at gcc dot gnu dot org 2004-12-28 5:05 ` pinskia at gcc dot gnu dot 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=20041220043614.24024.qmail@sourceware.org \ --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).