public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "smf.linux at ntlworld dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/62303] New: g++ 4.9.1 lto1: internal compiler error: Segmentation fault
Date: Fri, 29 Aug 2014 08:31:00 -0000	[thread overview]
Message-ID: <bug-62303-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 62303
           Summary: g++ 4.9.1 lto1: internal compiler error: Segmentation
                    fault
           Product: gcc
           Version: lto
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: smf.linux at ntlworld dot com

Created attachment 33415
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33415&action=edit
Full details of failure with -wrapper valgind

While build Qt 4.8.6 as a lto build I found the following when building
libQtCLucene.so the rest of the build is ok. If the I swap the optimization
from O3 to O2 the problem goes away. The gcc version is 4.9.1, the binutils is
2.24 built using the instructions from LFS. I have also tried the latest gcc
from git and that behaves the same:

lto1: internal compiler error: Segmentation fault
0x840f5da crash_signal
    ../../gcc-4.9.1/gcc/toplev.c:337
0x8342b70 lto_get_decl_name_mapping(lto_file_decl_data*, char const*)
    ../../gcc-4.9.1/gcc/lto-section-in.c:346
0x8340b59 copy_function
    ../../gcc-4.9.1/gcc/lto-streamer-out.c:1989
0x8340b59 lto_output()
    ../../gcc-4.9.1/gcc/lto-streamer-out.c:2083
0x8373250 write_lto
    ../../gcc-4.9.1/gcc/passes.c:2298
0x8375ffa ipa_write_optimization_summaries(lto_symtab_encoder_d*)
    ../../gcc-4.9.1/gcc/passes.c:2495
0x813cb48 do_stream_out
    ../../gcc-4.9.1/gcc/lto/lto.c:2464
0x8140b00 stream_out
    ../../gcc-4.9.1/gcc/lto/lto.c:2506
0x8140b00 lto_wpa_write_files
    ../../gcc-4.9.1/gcc/lto/lto.c:2643
0x8140b00 do_whole_program_analysis
    ../../gcc-4.9.1/gcc/lto/lto.c:3302
0x8140b00 lto_main()
    ../../gcc-4.9.1/gcc/lto/lto.c:3422


             reply	other threads:[~2014-08-29  8:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  8:31 smf.linux at ntlworld dot com [this message]
2014-08-29  8:40 ` [Bug c++/62303] " 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-62303-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).