public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58252] New: ice in gimple_get_virt_method_for_binfo with -O2
Date: Tue, 27 Aug 2013 15:11:00 -0000	[thread overview]
Message-ID: <bug-58252-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 58252
           Summary: ice in gimple_get_virt_method_for_binfo with -O2
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com

Created attachment 30705
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30705&action=edit
gzipped C++ source code

I just tried to compile package omniORB-4.1.6-5.fc20 with gcc 4.9 trunk dated
20130826. It said

In file included from irstub.cc:37:0:
../omniORB4/irSK.cc:13580:59: internal compiler error: in
gimple_get_virt_method_for_binfo, at gimple-fold.c:3142
 POA_CORBA::AbstractInterfaceDef::~AbstractInterfaceDef() {}
                                                           ^
0x92e140 gimple_get_virt_method_for_binfo(long, tree_node*)
    ../../src/trunk/gcc/gimple-fold.c:3141
0x96aed4 record_binfo
    ../../src/trunk/gcc/ipa-devirt.c:439
0x96ae72 record_binfo
    ../../src/trunk/gcc/ipa-devirt.c:454
0x96ae72 record_binfo
    ../../src/trunk/gcc/ipa-devirt.c:454
0x96b0e4 possible_polymorphic_call_targets_1
    ../../src/trunk/gcc/ipa-devirt.c:474
0x96b123 possible_polymorphic_call_targets_1
    ../../src/trunk/gcc/ipa-devirt.c:480
0x96c098 possible_polymorphic_call_targets(tree_node*, long, bool*, void**)
    ../../src/trunk/gcc/ipa-devirt.c:652
0x7de330 possible_polymorphic_call_targets
    ../../src/trunk/gcc/ipa-utils.h:82
0x7de330 analyze_functions
    ../../src/trunk/gcc/cgraphunit.c:936
0x7dfa85 finalize_compilation_unit()
    ../../src/trunk/gcc/cgraphunit.c:2200
0x5f3900 cp_write_global_declarations()
    ../../src/trunk/gcc/cp/decl2.c:4364
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

Preprocessed source code attached. Flag -O2 required.


             reply	other threads:[~2013-08-27 15:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27 15:11 dcb314 at hotmail dot com [this message]
2013-08-27 15:20 ` [Bug c++/58252] " paolo.carlini at oracle dot com
2013-08-29 11:36 ` jamborm at gcc dot gnu.org
2013-08-29 15:37 ` jamborm at gcc dot gnu.org
2013-09-03 19:56 ` [Bug c++/58252] [4.9 Regression] " paolo.carlini at oracle dot com
2013-09-05 17:25 ` hubicka at gcc dot gnu.org
2013-09-06 11:27 ` rguenth at gcc dot gnu.org
2013-09-09  9:02 ` hubicka at gcc dot gnu.org
2013-10-30 13:32 ` rguenth at gcc dot gnu.org
2013-12-17  9:42 ` trippels at gcc dot gnu.org
2013-12-24 13:53 ` trippels at gcc dot gnu.org
2014-01-02  9:29 ` dcb314 at hotmail dot com
2014-01-06 15:58 ` hubicka at gcc dot gnu.org
2014-01-07  9:34 ` hubicka at gcc dot gnu.org
2014-01-10  9:34 ` hubicka at gcc dot gnu.org
2014-01-10  9:34 ` hubicka at gcc dot gnu.org
2014-01-10  9:36 ` hubicka at gcc dot gnu.org
2014-01-11 11:01 ` hubicka 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-58252-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).