public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58789] [4.8 Regression] "internal compiler error: Segmentation fault" with external definition
Date: Mon, 21 Oct 2013 08:48:00 -0000 [thread overview]
Message-ID: <bug-58789-4-xPS3tpcQQy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58789-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58789
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jamborm at gcc dot gnu.org
Component|c++ |middle-end
Known to work| |4.7.3
Target Milestone|--- |4.8.3
Summary|"internal compiler error: |[4.8 Regression] "internal
|Segmentation fault" with |compiler error:
|external definition |Segmentation fault" with
| |external definition
Known to fail| |4.8.2
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
ICEs with -O2 -fipa-cp-clone on the 4.8 branch:
main.cpp:16:1: error: inlined_to pointer set for noninline callers
main.cpp:16:1: error: multiple inline callers
_ZN5ArrayI11edge_structE26delete_and_nullify_entriesEii/25 (void
Array<Type>::delete_and_nullify_entries(int, int) [with Type = edge_struct])
@0x7eff9b99acb8
Type: function
Visibility: public weak comdat
comdat_group:_ZN5ArrayI11edge_structE26delete_and_nullify_entriesEii one_only
virtual
References:
Referring:
Function void Array<Type>::delete_and_nullify_entries(int, int) [with Type =
edge_struct]/25 is inline copy in int main(int, char**)/3
Availability: local
Function flags: analyzed body local finalized
Called by: _ZN5ArrayI11edge_structE4growEib.constprop.2/21 (1.19 per call)
_ZN5ArrayI11edge_structE5clearEb/10 (0.30 per call) (inlined)
(indirect_inlining) (can throw external)
Calls:
main.cpp:16:1: internal compiler error: verify_cgraph_node failed
a regression from 4.7.x. Eventually the bug was fixed on trunk but the fix
not backported.
Martin?
next prev parent reply other threads:[~2013-10-21 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 16:03 [Bug c++/58789] New: " phe.bugzilla at gmail dot com
2013-10-18 16:05 ` [Bug c++/58789] " phe.bugzilla at gmail dot com
2013-10-18 16:05 ` phe.bugzilla at gmail dot com
2013-10-18 16:35 ` paolo.carlini at oracle dot com
2013-10-21 8:48 ` rguenth at gcc dot gnu.org [this message]
2013-10-24 17:22 ` [Bug middle-end/58789] [4.8 Regression] " jamborm at gcc dot gnu.org
2013-10-29 14:32 ` jamborm at gcc dot gnu.org
2013-10-29 14:43 ` 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-58789-4-xPS3tpcQQy@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).