public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <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: Tue, 12 Feb 2013 15:28:00 -0000	[thread overview]
Message-ID: <bug-55493-4-p2z0nJUj8U@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

--- Comment #10 from Kai Tietz <ktietz at gcc dot gnu.org> 2013-02-12 15:27:45 UTC ---
Well, I re-tried to reproduce this issue with current 4.8 gcc version (native).
As before, I can't reproduce that issue.  Anyway I don't get what report was
actual doing differently as I did, so I will keep this bug open.
Nevertheless we had recently some changes to lto, which are affecting mingw
targets, so it might be worth that report are retrying to reproduce.

Please make sure that you aren't mixing objects with LTO-infomration of
different versions.


  parent reply	other threads:[~2013-02-12 15:28 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
2013-02-08 14:58 ` rguenth at gcc dot gnu.org
2013-02-12 15:28 ` ktietz at gcc dot gnu.org [this message]
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-p2z0nJUj8U@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).