public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/66334] cleanup block fails to initialize EBX Date: Fri, 29 May 2015 20:37:00 -0000 [thread overview] Message-ID: <bug-66334-4-frTiDYG9Ge@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66334-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66334 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-05-29 CC| |vmakarov at redhat dot com Ever confirmed|0 |1 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> --- After IRA, (insn 34 33 35 5 (set (reg:SI 3 bx) (reg:SI 87)) 86 {*movsi_internal} (expr_list:REG_DEAD (reg:SI 87) (nil))) (call_insn 35 34 36 5 (call (mem:QI (symbol_ref:SI ("_Unwind_Resume") [flags 0x41] <function_decl 0x7f1f9f3005e8 __builtin_unwind_resume>) [0 __builtin_unwind_resume S1 A8]) (const_int 16 [0x10])) 649 {*call} (expr_list:REG_DEAD (reg:SI 3 bx) (expr_list:REG_CALL_DECL (symbol_ref:SI ("_Unwind_Resume") [flags 0x41] <function_decl 0x7f1f9f3005e8 __builtin_unwind_resume>) (expr_list:REG_ARGS_SIZE (const_int 16 [0x10]) (expr_list:REG_NORETURN (const_int 0 [0]) (nil))))) (expr_list (use (reg:SI 3 bx)) (nil))) LRA removed: (insn 34 33 35 5 (set (reg:SI 3 bx) (reg:SI 87)) 86 {*movsi_internal} (expr_list:REG_DEAD (reg:SI 87) (nil))) LRA should recognize that BUILT_IN_UNWIND_RESUME and initialize EBX.
next prev parent reply other threads:[~2015-05-29 20:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-29 2:50 [Bug middle-end/66334] New: " hjl.tools at gmail dot com 2015-05-29 2:56 ` [Bug middle-end/66334] " hjl.tools at gmail dot com 2015-05-29 20:37 ` hjl.tools at gmail dot com [this message] 2015-05-29 21:54 ` hjl.tools at gmail dot com 2015-05-29 21:55 ` hjl.tools at gmail dot com 2015-05-31 13:16 ` hjl.tools at gmail dot com 2015-06-01 14:21 ` hjl.tools at gmail dot com 2015-07-03 17:25 ` vmakarov at gcc dot gnu.org 2015-07-03 18:42 ` hjl.tools at gmail dot com 2015-07-03 21:04 ` vmakarov at gcc dot gnu.org 2015-07-04 13:57 ` hjl.tools at gmail dot com 2015-07-07 19:35 ` vmakarov at gcc dot gnu.org 2015-07-08 15:05 ` vmakarov 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-66334-4-frTiDYG9Ge@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).