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 lto/62026] [5 Regression] Crash in lto_get_decl_name_mapping
Date: Wed, 15 Oct 2014 17:00:00 -0000	[thread overview]
Message-ID: <bug-62026-4-DA89FLRNkI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62026-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Here's a new testcase that fails on ppc64 even with the patch from comment 15
applied to trunk.



trippels@gcc1-power7 genrb % cat timezone.ii
class UnicodeString
{
public:
  void m_fn1 ();
} a;
void
fn1 ()
{
  static int b = 0;
  a.m_fn1 ();
}

trippels@gcc1-power7 genrb % /home/trippels/gcc_test/usr/local/bin/c++ -flto=32
-ffunction-sections -fdata-sections -std=gnu++0x -g -O2 -r -nostdlib
timezone.ii
lto1: internal compiler error: Segmentation fault
0x1063d46b crash_signal
        ../../gcc/gcc/toplev.c:340
0x104ed8c4 lto_get_decl_name_mapping(lto_file_decl_data*, char const*)
        ../../gcc/gcc/lto-section-in.c:340
0x1098f447 varpool_node::get_constructor()
        ../../gcc/gcc/varpool.c:280
0x1098f447 varpool_node::get_constructor()
        ../../gcc/gcc/varpool.c:264
0x10981c4f get_variable_section(tree_node*, bool)
        ../../gcc/gcc/varasm.c:1121
0x10983ae3 get_block_for_decl
        ../../gcc/gcc/varasm.c:1194
0x1098663b make_decl_rtl(tree_node*)
        ../../gcc/gcc/varasm.c:1419
0x10989f43 make_decl_rtl_for_debug(tree_node*)
        ../../gcc/gcc/varasm.c:1467
0x102523f7 rtl_for_decl_location
        ../../gcc/gcc/dwarf2out.c:15760
0x102871e7 loc_list_from_tree
        ../../gcc/gcc/dwarf2out.c:14391
0x1028dc13 add_location_or_const_value_attribute
        ../../gcc/gcc/dwarf2out.c:15892
0x1028dc13 add_location_or_const_value_attribute
        ../../gcc/gcc/dwarf2out.c:15836
0x10297707 dwarf2out_finish
        ../../gcc/gcc/dwarf2out.c:24243
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.
make: *** [/home/trippels/tmp/ccC9suVr.ltrans0.ltrans.o] Error 1
lto-wrapper: fatal error: make returned 2 exit status
compilation terminated.
/home/trippels/bin/ld: fatal error: lto-wrapper failed
collect2: error: ld returned 1 exit status


  parent reply	other threads:[~2014-10-15 17:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-62026-4@http.gcc.gnu.org/bugzilla/>
2014-08-05 19:30 ` [Bug lto/62026] [4.9/4.10 " d.g.gorbachev at gmail dot com
2014-08-06  8:58 ` rguenth at gcc dot gnu.org
2014-08-09 14:55 ` trippels at gcc dot gnu.org
2014-08-17  5:27 ` [Bug lto/62026] [4.9/5 " d.g.gorbachev at gmail dot com
2014-08-29  8:40 ` trippels at gcc dot gnu.org
2014-08-29  9:46 ` smf.linux at ntlworld dot com
2014-08-29 10:06 ` trippels at gcc dot gnu.org
2014-08-29 12:54 ` smf.linux at ntlworld dot com
2014-09-03 11:57 ` jamborm at gcc dot gnu.org
2014-09-14 14:57 ` smf.linux at ntlworld dot com
2014-09-14 14:59 ` smf.linux at ntlworld dot com
2014-09-14 15:42 ` trippels at gcc dot gnu.org
2014-09-23 11:21 ` jamborm at gcc dot gnu.org
2014-09-23 11:38 ` trippels at gcc dot gnu.org
2014-10-04 22:00 ` hubicka at gcc dot gnu.org
2014-10-05  2:53 ` [Bug lto/62026] [5 " hubicka at gcc dot gnu.org
2014-10-15 17:00 ` trippels at gcc dot gnu.org [this message]
2014-10-15 17:01 ` hubicka at gcc dot gnu.org
2014-10-15 17:18 ` trippels at gcc dot gnu.org
2014-10-15 18:06 ` trippels 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-62026-4-DA89FLRNkI@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).