public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/65059] New: [5 Regression] Chrome LTO: lto1: internal compiler error: in ipa_comdats, at ipa-comdats.c:360
Date: Fri, 13 Feb 2015 21:43:00 -0000	[thread overview]
Message-ID: <bug-65059-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65059

            Bug ID: 65059
           Summary: [5 Regression] Chrome LTO: lto1: internal compiler
                    error: in ipa_comdats, at ipa-comdats.c:360
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org

Latest GCC produces ICE in:

lto1: internal compiler error: in ipa_comdats, at ipa-comdats.c:360
0xe58435 ipa_comdats
    ../../gcc/ipa-comdats.c:360
0xe585be execute
    ../../gcc/ipa-comdats.c:414

Problematic symbol:
_ZThn8_NK12_GLOBAL__N_116PanelStackWindow9GetWidgetEv/94300622
(_ZThn8_NK12_GLOBAL__N_116PanelStackWindow9GetWidgetEv) @0x7f557e1927a8
  Type: function definition analyzed
  Visibility: prevailing_def_ironly virtual artificial
  References: 
  Referring: 
  Read from file:
obj/chrome/browser/ui/views/panels/browser_ui.panel_stack_view.o
  Availability: available
  First run: 0
  Function flags:
  Thunk fixed offset -8 virtual value 0 has virtual offset 0)
  Called by: 
  Calls: *.LTHUNK22/94300621 (1.00 per call) 

If I see ipa-devirt correctly, this symbol should be probably removed as dead
as it has no calls, am I right? How could I debug if the symbol is considered
to be removed?

Thanks,
Martin


             reply	other threads:[~2015-02-13 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 21:43 marxin at gcc dot gnu.org [this message]
2015-02-15 19:18 ` [Bug ipa/65059] " hubicka at gcc dot gnu.org
2015-02-15 20:00 ` marxin at gcc dot gnu.org
2015-02-16  9:43 ` rguenth at gcc dot gnu.org
2015-02-16 12:29 ` marxin at gcc dot gnu.org
2015-02-16 15:03 ` mpolacek at gcc dot gnu.org
2015-02-16 15:29 ` marxin 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-65059-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).