public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincenzo.innocente at cern dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/53746] [lto] segfault in std::vector::__base_ctor (with -fno-math-errno -fipa-pta) and ICE with trunk revision 188906
Date: Sat, 23 Jun 2012 09:37:00 -0000 [thread overview]
Message-ID: <bug-53746-4-wdsLrWvrJZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53746-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53746
vincenzo Innocente <vincenzo.innocente at cern dot ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[lto] segfault in |[lto] segfault in
|std::vector::__base_ctor |std::vector::__base_ctor
|(with -fno-math-errno |(with -fno-math-errno
|-fipa-pta) |-fipa-pta) and ICE with
| |trunk revision 188906
--- Comment #3 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2012-06-23 09:37:33 UTC ---
just updated to latest trunk and
$CXXGO -Wl,-v stubs.o -shared -o libstubs.so -Wl,-rpath=./
collect2 version 4.8.0 20120623 (experimental) [trunk revision 188906]
/home/innocent/gccDir/bin/ld -plugin
/home/innocent/gccDir/libexec/gcc/x86_64-unknown-linux-gnu/4.8.0/liblto_plugin.so
-plugin-opt=/home/innocent/gccDir/libexec/gcc/x86_64-unknown-linux-gnu/4.8.0/lto-wrapper
-plugin-opt=-fresolution=/tmp/ccvCCsbR.res -plugin-opt=-pass-through=-lgcc_s
-plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc_s --eh-frame-hdr
-m elf_x86_64 -shared -o libstubs.so /lib/../lib64/crti.o
/home/innocent/gccDir/lib/gcc/x86_64-unknown-linux-gnu/4.8.0/crtbeginS.o
-L/home/innocent/gccDir/lib/gcc/x86_64-unknown-linux-gnu/4.8.0
-L/home/innocent/gccDir/lib/gcc/x86_64-unknown-linux-gnu/4.8.0/../../../../lib64
-L/lib/../lib64 -L/usr/lib/../lib64
-L/home/innocent/gccDir/lib/gcc/x86_64-unknown-linux-gnu/4.8.0/../../.. -v
stubs.o -rpath=./ -lstdc++ -lm -lgcc_s -lc -lgcc_s
/home/innocent/gccDir/lib/gcc/x86_64-unknown-linux-gnu/4.8.0/crtendS.o
/lib/../lib64/crtn.o
GNU gold (version 2.22.52.0.1-10.fc17 20120131) 1.11
lto1: internal compiler error: in lhd_decl_printable_name, at langhooks.c:222
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
lto-wrapper: c++ returned 1 exit status
/home/innocent/gccDir/bin/ld: fatal error: lto-wrapper failed
collect2: error: ld returned 1 exit status
next prev parent reply other threads:[~2012-06-23 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 16:57 [Bug lto/53746] New: [lto] segfault in std::vector::__base_ctor vincenzo.innocente at cern dot ch
2012-06-21 17:13 ` [Bug lto/53746] " markus at trippelsdorf dot de
2012-06-23 9:06 ` [Bug lto/53746] [lto] segfault in std::vector::__base_ctor (with -fno-math-errno -fipa-pta) vincenzo.innocente at cern dot ch
2012-06-23 9:37 ` vincenzo.innocente at cern dot ch [this message]
2012-06-23 10:00 ` [Bug lto/53746] [lto] segfault in std::vector::__base_ctor (with -fipa-pta) vincenzo.innocente at cern dot ch
2012-11-01 7:17 ` vincenzo.innocente at cern dot ch
2021-09-12 7:52 ` [Bug ipa/53746] " pinskia 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-53746-4-wdsLrWvrJZ@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).