public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vanboxem.ruben at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/55493] [4.8 Regression] LTO always ICEs on i686-mingw32
Date: Sun, 20 Jan 2013 18:34:00 -0000 [thread overview]
Message-ID: <bug-55493-4-YYHnQQmp9t@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55493-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55493
Ruben Van Boxem <vanboxem.ruben at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vanboxem.ruben at gmail dot
| |com
--- Comment #8 from Ruben Van Boxem <vanboxem.ruben at gmail dot com> 2013-01-20 18:34:11 UTC ---
I can confirm that this bug is present for GCC 4.8 dated 20121221, which is
available here:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/gcc-4.8-unstable/i686-w64-mingw32-gcc-4.8-unstable-win32_rubenvb.7z/download
I get:
lto1.exe: internal compiler error: cannot read LTO decls from
R:\temp\ccgzHybZ.o
Please submit a full bug report,
with preprocessed source if appropriate.
See <mingw-w64-public@lists.sourceforge.net> for instructions.
lto-wrapper: g++ returned 1 exit status
m:/development/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.8.0/../../../../i686-w64-mingw32/bin/ld.exe:
lto-wrapper failed
collect2.exe: error: ld returned 1 exit status
next prev parent reply other threads:[~2013-01-20 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 16:22 [Bug lto/55493] New: [4.8 Regression] LTO always ICEs on i686-w64-mingw32 fanael4 at gmail dot com
2012-11-27 16:26 ` [Bug lto/55493] " fanael4 at gmail dot com
2012-11-28 12:40 ` rguenth at gcc dot gnu.org
2013-01-07 15:26 ` rguenth at gcc dot gnu.org
2013-01-09 14:19 ` [Bug lto/55493] [4.8 Regression] LTO always ICEs on i686-mingw32 fanael4 at gmail dot com
2013-01-15 17:38 ` ktietz at gcc dot gnu.org
2013-01-15 18:33 ` ktietz at gcc dot gnu.org
2013-01-16 18:15 ` fanael4 at gmail dot com
2013-01-18 18:46 ` fanael4 at gmail dot com
2013-01-20 18:34 ` vanboxem.ruben at gmail dot com [this message]
2013-02-08 14:58 ` rguenth at gcc dot gnu.org
2013-02-12 15:28 ` ktietz at gcc dot gnu.org
2013-02-27 16:40 ` [Bug lto/55493] [4.8 Regression] LTO always ICEs on native i686-mingw32 fanael4 at gmail 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-55493-4-YYHnQQmp9t@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).