public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/45089] -Os -g -fwhopr dwarf2out ICE
Date: Tue, 27 Jul 2010 09:18:00 -0000	[thread overview]
Message-ID: <20100727091750.10178.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45089-176@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rguenth at gcc dot gnu dot org  2010-07-27 09:17 -------
Trying to reduce ... it happens only with whopr.

Program received signal SIGSEGV, Segmentation fault.
0x00000000005d33ba in prune_unused_types_mark (die=0x0, dokids=1)
    at /space/rguenther/src/svn/trunk/gcc/dwarf2out.c:21729
21729     if (die->die_mark == 0)

#1  0x00000000005d3349 in prune_unused_types_walk_attribs (die=0x7ffff5a12d68)
    at /space/rguenther/src/svn/trunk/gcc/dwarf2out.c:21711
21711               prune_unused_types_mark (a->dw_attr_val.v.val_die_ref.die,
1);
(gdb) p a->dw_attr_val.v.val_die_ref
$1 = {die = 0x0, external = 0}

so we created a dw_val_class_die_ref attr with a null DIE.  Which we do
here:

#1  0x00000000005c9c14 in add_pure_or_virtual_attribute (die=0x7ffff5a12d68, 
    func_decl=0x7ffff55cd300)
    at /space/rguenther/src/svn/trunk/gcc/dwarf2out.c:17409
17407         if (debug_info_level > DINFO_LEVEL_TERSE
17408             && DECL_CONTEXT (func_decl))
17409           add_AT_die_ref (die, DW_AT_containing_type,
17410                           lookup_type_die (DECL_CONTEXT (func_decl)));

where DECL_CONTEXT is a RECORD_TYPE.

Supposedly the type is unused and thus doesn't get output.

Note that we're arriving here via

#5  0x0000000000c74a47 in expand_call_inline (bb=0x7ffff54782d8, 
    stmt=0x7ffff52c89b0, id=0x7fffffffd970)
    at /space/rguenther/src/svn/trunk/gcc/tree-inline.c:4024
4024      (*debug_hooks->outlining_inline_function) (cg_edge->callee->decl);


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-07-27 09:17:50
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45089


  parent reply	other threads:[~2010-07-27  9:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 21:03 [Bug lto/45089] New: " hubicka at gcc dot gnu dot org
2010-07-26 21:04 ` [Bug lto/45089] " hubicka at gcc dot gnu dot org
2010-07-27  9:18 ` rguenth at gcc dot gnu dot org [this message]
2010-07-27  9:27 ` rguenth at gcc dot gnu dot org
2010-07-27  9:43 ` hubicka at ucw dot cz
2010-07-27  9:46 ` rguenth at gcc dot gnu dot org
2010-07-27 11:06 ` rguenth at gcc dot gnu dot org
     [not found] <bug-45089-4@http.gcc.gnu.org/bugzilla/>
2010-10-02 14:16 ` hubicka at gcc dot gnu.org
2010-10-11 13:02 ` rguenth at gcc dot gnu.org
2010-10-15  2:43 ` hubicka at gcc dot gnu.org
2010-10-15  8:32 ` rguenth at gcc dot gnu.org
2010-11-18 14:11 ` rguenth at gcc dot gnu.org
2010-11-18 14:24 ` rguenth at gcc dot gnu.org
2011-01-08 21:26 ` hubicka at gcc dot gnu.org
2012-01-03 11:58 ` rguenth at gcc dot gnu.org
2012-07-05 14:18 ` 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=20100727091750.10178.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: link
Be 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).