public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/64139] [4.9/5 Regression] ice in possible_polymorphic_call_targets, at ipa-devirt.c:2410
Date: Fri, 12 Dec 2014 11:04:00 -0000 [thread overview]
Message-ID: <bug-64139-4-1GnPxgXlmW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64139-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64139
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |trippels at gcc dot gnu.org
Summary|[5 Regression] ice in |[4.9/5 Regression] ice in
|possible_polymorphic_call_t |possible_polymorphic_call_t
|argets, at |argets, at
|ipa-devirt.c:2410 |ipa-devirt.c:2410
Known to fail| |4.9.1, 5.0
--- Comment #5 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
reduced test case:
class IObject {
public:
virtual ~IObject();
};
class A {
virtual int m_fn1();
};
class B {
public:
virtual int m_fn2(B) const;
};
class D : IObject, public virtual B {};
class G : public D, A {
public:
G(A);
};
class F : B {
friend class C;
};
class C {
void m_fn3(const IObject &, int &);
void m_fn4(const B &, int &);
};
A a;
void C::m_fn3(const IObject &, int &p2) {
G r(a);
m_fn4(r, p2);
}
void C::m_fn4(const B &p1, int &) {
F b;
p1.m_fn2(b);
}
Also ICEs with gcc-4.9:
trippels@gcc20 ~ % g++ -c -O2 bug178.cc
bug178.cc: In member function ‘void C::m_fn3(const IObject&, int&)’:
bug178.cc:32:1: internal compiler error: in possible_polymorphic_call_targets,
at ipa-devirt.c:1557
>From gcc-bugs-return-470389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Dec 12 11:13:50 2014
Return-Path: <gcc-bugs-return-470389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11831 invoked by alias); 12 Dec 2014 11:13:49 -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 11795 invoked by uid 48); 12 Dec 2014 11:13:45 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/64285] New: [5 Regression] During LTO: ICE segfault in ipa_polymorphic_call_context::get_dynamic_type
Date: Fri, 12 Dec 2014 11:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus 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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc
Message-ID: <bug-64285-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-12/txt/msg01396.txt.bz2
Content-length: 1545
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd285
Bug ID: 64285
Summary: [5 Regression] During LTO: ICE segfault in
ipa_polymorphic_call_context::get_dynamic_type
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org
I tried compiling the program again which gave the ICE of PR64043, motivated by
the patch https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01076.html which looks
vaguely related.
In any case, it now (r218661) fails with:
gcc-trunk/include/c++/5.0.0/bits/unique_ptr.h:70:0: internal compiler error:
Segmentation fault
operator()(_Tp* __ptr) const
^
0xa2576f crash_signal
../../gcc/toplev.c:358
0x878d2f tree_check(tree_node*, char const*, int, char const*, tree_code)
../../gcc/tree.h:2778
0x878d2f ipa_polymorphic_call_context::get_dynamic_type(tree_node*, tree_node*,
tree_node*, gimple_statement_base*)
../../gcc/ipa-polymorphic-call.c:1594
0xb9f23e eliminate_dom_walker::before_dom_children(basic_block_def*)
../../gcc/tree-ssa-pre.c:4334
0xfde647 dom_walker::walk(basic_block_def*)
../../gcc/domwalk.c:188
0xba0da0 eliminate
../../gcc/tree-ssa-pre.c:4491
0xba0ff5 execute
../../gcc/tree-ssa-pre.c:4910
Testcase reduction under way
next prev parent reply other threads:[~2014-12-12 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 17:10 [Bug c++/64139] New: " dcb314 at hotmail dot com
2014-12-01 17:35 ` [Bug ipa/64139] [5 Regression] " hjl.tools at gmail dot com
2014-12-01 18:11 ` jamborm at gcc dot gnu.org
2014-12-01 19:21 ` jamborm at gcc dot gnu.org
2014-12-01 19:39 ` hubicka at gcc dot gnu.org
2014-12-02 10:35 ` rguenth at gcc dot gnu.org
2014-12-12 11:04 ` trippels at gcc dot gnu.org [this message]
2014-12-15 3:57 ` [Bug ipa/64139] [4.9/5 " hubicka at gcc dot gnu.org
2015-01-26 23:54 ` hubicka at gcc dot gnu.org
2015-01-27 17:08 ` 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-64139-4-1GnPxgXlmW@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).