public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lucdanton at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60600] New: ICE in ipa_get_indirect_edge_target_1
Date: Thu, 20 Mar 2014 13:03:00 -0000	[thread overview]
Message-ID: <bug-60600-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60600
           Summary: ICE in ipa_get_indirect_edge_target_1
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: lucdanton at free dot fr

Created attachment 32404
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32404&action=edit
Testcase

$ g++-trunk --version
g++-trunk (GCC) 4.9.0 20140319 (experimental)

$ cat main.cpp 
struct data {
    data(int);
};

struct top {
    virtual int topf();
};

struct intermediate: top {
    int topf() /* override */ { return 0; }
};

struct child1: top {
    void childf()
    {
        data d(topf());
    }
};

struct child2: intermediate {};

void test(top& t)
{
    child1& c = static_cast<child1&>(t);
    c.childf();
    child2 d;
    test(d);
}

$ g++-trunk main.cpp -O3
main.cpp:28:1: internal compiler error: in ipa_get_indirect_edge_target_1, at
ipa-cp.c:1645
 }
 ^
0x10ac52e ipa_get_indirect_edge_target_1
    ../../gcc/gcc/ipa-cp.c:1644
0xa1570c estimate_edge_devirt_benefit
    ../../gcc/gcc/ipa-inline-analysis.c:2955
0xa1570c estimate_edge_size_and_time
    ../../gcc/gcc/ipa-inline-analysis.c:2987
0xa1570c estimate_calls_size_and_time
    ../../gcc/gcc/ipa-inline-analysis.c:3040
0xa1602c estimate_node_size_and_time
    ../../gcc/gcc/ipa-inline-analysis.c:3127
0xa18016 estimate_ipcp_clone_size_and_time(cgraph_node*, vec<tree_node*,
va_heap, vl_ptr>, vec<tree_node*, va_heap, vl_ptr>, vec<ipa_agg_jump_function*,
va_heap, vl_ptr>, int*, int*, int*)
    ../../gcc/gcc/ipa-inline-analysis.c:3163
0x10b17fc estimate_local_effects
    ../../gcc/gcc/ipa-cp.c:2004
0x10b17fc propagate_constants_topo
    ../../gcc/gcc/ipa-cp.c:2229
0x10b17fc ipcp_propagate_stage
    ../../gcc/gcc/ipa-cp.c:2329
0x10b17fc ipcp_driver
    ../../gcc/gcc/ipa-cp.c:3707
0x10b17fc execute
    ../../gcc/gcc/ipa-cp.c:3806
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.

-------------------------------------

This only happens with -O3, in all C++ modes. This may be a regression – the
testcase was built from the preprocessed source of a third-party library, with
stock settings. Presumably it built at some point before shipping.
>From gcc-bugs-return-446985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Mar 20 13:40:57 2014
Return-Path: <gcc-bugs-return-446985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23577 invoked by alias); 20 Mar 2014 13:40:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23522 invoked by uid 48); 20 Mar 2014 13:40:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60580] aarch64 generates wrong code for __attribute__ ((optimize("no-omit-frame-pointer")))
Date: Thu, 20 Mar 2014 13:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.8.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60580-4-MNG19wjA7J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60580-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60580-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg01854.txt.bz2
Content-length: 233

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`580

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'm not going to hack on this any time soon, so if aarch64 maintainers could
take it over, it would be appreciated.


             reply	other threads:[~2014-03-20 13:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 13:03 lucdanton at free dot fr [this message]
2014-03-20 14:10 ` [Bug c++/60600] [4.9 Regression] " jakub at gcc dot gnu.org
2014-03-21 12:55 ` [Bug ipa/60600] " rguenth at gcc dot gnu.org
2014-03-21 14:41 ` jamborm at gcc dot gnu.org
2014-03-22 11:27 ` lucdanton at free dot fr
2014-03-25  0:29 ` hubicka at gcc dot gnu.org
2014-03-25 18:20 ` jamborm at gcc dot gnu.org
2014-03-25 18:23 ` jamborm at gcc dot gnu.org
2014-03-25 18:24 ` 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-60600-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).