http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57208
--- Comment #3 from Martin Liška <marxin.liska at gmail dot com> ---
I had a problem with linker, looks like chrome build system uses both linkers.
I hacked build system to use just ld.bfd.
gcc revision: 197652. I know it's about 2 months old, same error is given by
gcc from about 15th May 2013. Latest gcc suffers from a different failure that
will be added in following comment.
ld --version:
GNU ld (GNU Binutils) 2.23.52.20130526
Failure:
g++ -Wl,-z,now -Wl,-z,relro -pthread -Wl,-z,noexecstack -fPIC -Wl,-O1
-Wl,--as-needed -flto -fno-fat-lto-objects -o mksnapshot.x64 -Wl,--start-group
obj/v8/src/mksnapshot.x64.mksnapshot.o obj/v8/tools/gyp/libv8_nosnapshot.x64.a
obj/v8/tools/gyp/libv8_base.x64.a -Wl,--end-group -fdump-ipa-all --save-temps
lto1: internal compiler error: in inline_call, at ipa-inline-transform.c:267
0x709296 inline_call(cgraph_edge*, bool, vec<cgraph_edge*, va_heap, vl_ptr>*,
int*, bool)
../../gcc/ipa-inline-transform.c:263
0x6fb118 inline_small_functions
../../gcc/ipa-inline.c:1613
0x6fb118 ipa_inline
../../gcc/ipa-inline.c:1794
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.
lto-wrapper: g++ returned 1 exit status
[Leaving LTRANS mksnapshot.x64.ltrans.out]
[Leaving LTRANS /tmp/ccIviE1Z.args]
/home/marxin/gcc-mirror/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/ld:
lto-wrapper failed
collect2: error: ld returned 1 exit status
Dump:
https://docs.google.com/file/d/0B0pisUJ80pO1ck5sUmF5Q0k1Mmc/edit?usp=sharing
Thanks,
Martin
