public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/52605] New: LTO -g ICE when looking up context of VMTs of classes defined within functions
Date: Fri, 16 Mar 2012 16:49:00 -0000	[thread overview]
Message-ID: <bug-52605-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52605
           Summary: LTO -g ICE when looking up context of VMTs of classes
                    defined within functions
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jamborm@gcc.gnu.org
              Host: x86_64-linux-gnu
            Target: x86_64-linux-gnu


Created attachment 26905
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26905
Testcase

When compiling the attached testcase with -flto and -g, I get the
following ICE:

lto1: internal compiler error: tree check: expected tree that contains ‘decl
minimal’ structure, have ‘record_type’ in lookup_decl_die, at dwarf2out.c:5118

This is the same problem I first encountered when LTOing Firefox and
which I reported in the mailing list a while ago
(http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00551.html) but this
testcase is close to minimal.

The reason why we do not hit this wrong use of decl_function_context
without LTO is that the function dwarf2out_decl is never called on
VMTs when not doing LTO.


             reply	other threads:[~2012-03-16 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 16:49 jamborm at gcc dot gnu.org [this message]
2012-04-23 17:05 ` [Bug lto/52605] " jamborm at gcc dot gnu.org
2012-05-02 19:51 ` jamborm at gcc dot gnu.org
2012-05-03 17:01 ` jamborm at gcc dot gnu.org
2012-05-03 17:02 ` jamborm 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-52605-4@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: 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).