public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pangbw at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/48826] ICE in dwarf2out_var_location, at dwarf2out.c:22013 Date: Thu, 11 Sep 2014 21:44:00 -0000 [thread overview] Message-ID: <bug-48826-4-fnYJXpZnSa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48826-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48826 baoshan <pangbw at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pangbw at gmail dot com --- Comment #10 from baoshan <pangbw at gmail dot com> --- The code is broken in the latest code because beside NOTE instruction there could be BARRIER too, for instance the RTX list I am seeing: (call_insn 32 35 33 (parallel [ (set (reg:SI 2 $2) (call (mem:SI (reg:SI 25 $25 [198]) [0 S4 A32]) (const_int 16 [0x10]))) (clobber (reg:SI 31 $31)) (clobber (reg:SI 28 $28)) ]) min.c:20 603 {call_value_split} (nil) (expr_list (use (reg:SI 79 $fakec)) (expr_list (use (reg:SI 28 $28)) (expr_list:SI (use (reg:SI 5 $5)) (expr_list:SI (use (reg:SI 4 $4)) (nil)))))) (insn 33 32 34 (set (reg:SI 28 $28) (mem/c:SI (plus:SI (reg/f:SI 29 $sp) (const_int 16 [0x10])) [0 S4 A32])) min.c:20 288 {*movsi_internal} (nil)) (barrier 34 33 18) (barrier 18 34 30) (note 30 18 21 (expr_list:REG_DEP_TRUE (concat:SI (pc) (unspec:SI [ (reg:SI 28 $28) (const:SI (unspec:SI [ (symbol_ref:SI ("signal") [flags 0x41] <function_decl 0xb71f6700 signal>) ] 227)) (reg:SI 79 $fakec) ] UNSPEC_LOAD_CALL)) (expr_list:REG_DEP_TRUE (concat:SI (reg:SI 5 $5) (const_int 0 [0])) (expr_list:REG_DEP_TRUE (concat:SI (reg:SI 4 $4) (const_int 2 [0x2])) (nil)))) NOTE_INSN_CALL_ARG_LOCATION) (note 21 30 0 NOTE_INSN_DELETED)
next prev parent reply other threads:[~2014-09-11 21:44 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-29 16:30 [Bug debug/48826] New: " rmansfield at qnx dot com 2011-05-04 13:04 ` [Bug debug/48826] " rmansfield at qnx dot com 2011-05-04 14:26 ` rmansfield at qnx dot com 2011-05-04 14:44 ` jakub at gcc dot gnu.org 2011-05-05 13:22 ` rmansfield at qnx dot com 2011-05-22 21:41 ` [Bug rtl-optimization/48826] " rsandifo at gcc dot gnu.org 2011-05-23 18:37 ` rsandifo at gcc dot gnu.org 2011-05-23 18:44 ` rsandifo at gcc dot gnu.org 2011-05-23 18:57 ` rsandifo at gcc dot gnu.org 2011-05-26 14:32 ` rmansfield at qnx dot com 2014-09-11 21:44 ` pangbw at gmail dot com [this message] 2014-09-11 21:50 ` pangbw at gmail dot com
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-48826-4-fnYJXpZnSa@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).