public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "guido.hatzsis at yandex dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/66687] New: WPA link fau: internal compiler error: bytecode stream: found non-null terminated string Date: Sat, 27 Jun 2015 00:42:00 -0000 [thread overview] Message-ID: <bug-66687-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66687 Bug ID: 66687 Summary: WPA link fau: internal compiler error: bytecode stream: found non-null terminated string Product: gcc Version: lto Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: guido.hatzsis at yandex dot com Target Milestone: --- Created attachment 35860 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35860&action=edit res file With gcc 5.1 is was possible to compile executables statically with with an libc (musl) static library. It is no longer possible with 6.0 COLLECT_GCC_OPTIONS='-c' '-ffp-contract=off' '-fmath-errno' '-fsigned-zeros' '-ftrapping-math' '-fno-trapv' '-fno-openmp' '-fno-openacc' '-mtune=generic' '-march=x86-64' '-O2' '-fPIC' '-fno-exceptions' '-B' '/x32/gcc/stageN/./gcc/' '-B' '/x32/build/host/x86_64-sb-linux-muslx32/bin/' '-B' '/x32/build/host/x86_64-sb-linux-muslx32/lib/' '-v' '-save-temps' '-mtune=generic' '-march=x86-64' '-fltrans-output-list=/tmp/cctXDCnL.ltrans.out' '-fwpa' '-fresolution=conftest.res' /x32/gcc/stageN/./gcc/lto1 -quiet -dumpbase crt1.o -mtune=generic -march=x86-64 -mtune=generic -march=x86-64 -auxbase crt1 -O2 -version -ffp-contract=off -fmath-errno -fsigned-zeros -ftrapping-math -fno-trapv -fno-openmp -fno-openacc -fPIC -fno-exceptions -fltrans-output-list=/tmp/cctXDCnL.ltrans.out -fwpa -fresolution=conftest.res @/tmp/ccir6VzL GNU GIMPLE (GCC) version 6.0.0 20150619 (experimental) (x86_64-sb-linux-muslx32) compiled by GNU C version 5.1.0, GMP version 6.0.0, MPFR version 3.1.3, MPC version 1.0.3 GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 GNU GIMPLE (GCC) version 6.0.0 20150619 (experimental) (x86_64-sb-linux-muslx32) compiled by GNU C version 5.1.0, GMP version 6.0.0, MPFR version 3.1.3, MPC version 1.0.3 GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 lto1: internal compiler error: bytecode stream: found non-null terminated string Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. lto-wrapper: fatal error: /x32/gcc/stageN/./gcc/xgcc returned 1 exit status compilation terminated. [Leaving LTRANS /tmp/ccO8tBym] [Leaving LTRANS /tmp/cctXDCnL.ltrans.out] /x32/build/host/x86_64-sb-linux-muslx32/bin/ld: fatal error: lto-wrapper failed
next reply other threads:[~2015-06-27 0:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-27 0:42 guido.hatzsis at yandex dot com [this message] 2015-06-27 0:42 ` [Bug c/66687] " guido.hatzsis at yandex dot com 2015-06-27 0:45 ` [Bug lto/66687] " pinskia at gcc dot gnu.org 2015-06-27 1:16 ` guido.hatzsis at yandex dot com 2015-06-27 1:24 ` pinskia at gcc dot gnu.org 2015-06-27 15:15 ` hjl.tools at gmail dot com 2015-06-28 19:50 ` guido.hatzsis at yandex dot com 2015-06-28 19:57 ` hjl.tools at gmail dot com 2015-06-29 4:35 ` pinskia at gcc dot gnu.org 2015-06-29 8:42 ` rguenth at gcc dot gnu.org 2015-07-01 23:32 ` guido.hatzsis at yandex dot com
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-66687-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: linkBe 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).