public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/66687] WPA link fau: internal compiler error: bytecode stream: found non-null terminated string Date: Mon, 29 Jun 2015 08:42:00 -0000 [thread overview] Message-ID: <bug-66687-4-Wx1rzSx0WR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66687-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66687 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- Are you sure you produced all LTO bytecode with exactly the same compiler? Reminds me to bump the LTO bytecode version again on trunk (it's still the same as that on the GCC 5 branch...)
next prev parent reply other threads:[~2015-06-29 8:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-27 0:42 [Bug c/66687] New: " guido.hatzsis at yandex dot com 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 [this message] 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-Wx1rzSx0WR@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).