public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/56131] [4.8 regression] gcc.dg/pr56035.c ICEs gcc on sparc-linux Date: Mon, 28 Jan 2013 23:16:00 -0000 [thread overview] Message-ID: <bug-56131-4-6AK9xz5N9d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56131-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56131 vries at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2013-01-28 Ever Confirmed|0 |1 --- Comment #2 from vries at gcc dot gnu.org 2013-01-28 23:15:32 UTC --- I can reproduce this on a x86_64-linux to sparc-linux cross-compiler. The segv is due to bb being null and dereferenced: ... Program received signal SIGSEGV, Segmentation fault. 0x000000000066145b in delete_insn (insn=0x7ffff6b1a480) at gcc/cfgrtl.c:150 150 BB_HEAD (bb) = bb_note; (gdb) p bb $4 = (basic_block) 0x0 ... the bb var is set here: ... 138 basic_block bb = BLOCK_FOR_INSN (insn); ... with insn being: ... (gdb) call debug_rtx (insn) (code_label 22 21 23 3 ("lbl1") [0 uses]) ...
next prev parent reply other threads:[~2013-01-28 23:16 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-28 17:42 [Bug regression/56131] New: " mikpe at it dot uu.se 2013-01-28 21:59 ` [Bug regression/56131] " mikpe at it dot uu.se 2013-01-28 23:16 ` vries at gcc dot gnu.org [this message] 2013-01-29 0:28 ` vries at gcc dot gnu.org 2013-01-29 10:12 ` [Bug rtl-optimization/56131] " rguenth at gcc dot gnu.org 2013-01-29 17:01 ` danglin at gcc dot gnu.org 2013-01-29 19:34 ` vries at gcc dot gnu.org 2013-01-30 22:20 ` mikpe at it dot uu.se 2013-02-04 13:08 ` ro at gcc dot gnu.org 2013-02-04 15:19 ` vries at gcc dot gnu.org 2013-02-04 15:39 ` mikpe at it dot uu.se 2013-02-04 17:35 ` vries at gcc dot gnu.org 2013-02-06 8:54 ` vries at gcc dot gnu.org 2013-02-06 12:24 ` vries at gcc dot gnu.org 2013-02-21 10:30 ` steven at gcc dot gnu.org 2013-02-22 10:30 ` vries at gcc dot gnu.org 2013-02-22 13:18 ` jakub at gcc dot gnu.org 2013-02-22 16:34 ` steven at gcc dot gnu.org 2013-02-22 22:37 ` vries at gcc dot gnu.org 2013-02-25 9:31 ` vries at gcc dot gnu.org 2013-02-25 10:34 ` jakub at gcc dot gnu.org 2013-02-25 11:50 ` vries at gcc dot gnu.org 2013-02-25 11:51 ` vries at gcc dot gnu.org 2013-02-25 19:55 ` stevenb.gcc at gmail dot com 2013-02-25 19:59 ` stevenb.gcc at gmail dot com 2013-02-25 22:29 ` ebotcazou 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-56131-4-6AK9xz5N9d@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).