From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: Claus Fischer <claus.fischer@clausfischer.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Likely code generation bug in GCC 4.0.1
Date: Mon, 14 May 2007 09:59:00 -0000 [thread overview]
Message-ID: <17992.13065.31663.520523@zebedee.pink> (raw)
In-Reply-To: <20070514095013.GB19170@clausfischer.com>
Claus Fischer writes:
> On Mon, May 14, 2007 at 10:35:57AM +0100, Andrew Haley wrote:
> : Claus Fischer writes:
> : > On Mon, May 14, 2007 at 10:18:26AM +0100, Andrew Haley wrote:
> : > : Claus Fischer writes:
> : > : >
> : > : > I think I found a code generation bug in GCC 4.0.1.
> : > : >
> : > : > I'm sending this mail to make sure this bug is known and
> : > : > is or will be removed in newer versions.
> : > : > On a quick glance I couldn't find it in the bug database,
> : > : > so it may not be known.
> : > :
> : > : Redirected to gcc-help.
> : > :
> : > : Please send a full test case that can be run, with full information
> : > : about the expected effect.
> : >
> : >
> : > The full test case is way too big to run and contains data
> : > which I don't have authority to disclose publicly.
>
>
> [ Unfortunately, creating the MINGW cross compilation environment
> itself is a task that would probably keep most gcc developers from
> examining the case, even if I posted the instructions. ]
Sure, but if we had a test case we'd know if this bug was mingw
specific.
Anyway, something you should know: there is zero probablility that any
bugs in gcc 4.0.x will ever be fixed: the branch was closed after the
release of GCC 4.0.4.
Andrew.
next prev parent reply other threads:[~2007-05-14 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070513221443.GA3660@clausfischer.com>
2007-05-14 9:18 ` Andrew Haley
2007-05-14 9:29 ` Claus Fischer
2007-05-14 9:36 ` Andrew Haley
2007-05-14 9:50 ` Claus Fischer
2007-05-14 9:59 ` Andrew Haley [this message]
2007-05-14 10:15 ` Claus Fischer
2007-05-14 19:56 ` Claus Fischer
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=17992.13065.31663.520523@zebedee.pink \
--to=aph-gcc@littlepinkcloud.com \
--cc=claus.fischer@clausfischer.com \
--cc=gcc-help@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).