From: Tom Rini <trini@kernel.crashing.org>
To: Alexander Viro <viro@math.psu.edu>
Cc: Gregory Maxwell <greg@linuxpower.cx>,
Andries.Brouwer@cwi.nl, alan@lxorguk.ukuu.org.uk,
bernds@redhat.com, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: gcc 2.95.2 is buggy
Date: Fri, 24 Nov 2000 08:23:24 -0700 [thread overview]
Message-ID: <20001124082324.A872@opus.bloom.county> (raw)
In-Reply-To: <20001123233454.B27831@xi.linuxpower.cx> <Pine.GSO.4.21.0011232344580.12702-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0011232344580.12702-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Thu, Nov 23, 2000 at 11:47:04PM -0500
On Thu, Nov 23, 2000 at 11:47:04PM -0500, Alexander Viro wrote:
>
>
> On Thu, 23 Nov 2000, Gregory Maxwell wrote:
>
> > On Fri, Nov 24, 2000 at 02:57:45AM +0100, Andries.Brouwer@cwi.nl wrote:
> > > but in the meantime there is good confirmation.
> > > This really is a bug in gcc 2.95.2.
> >
> > ... RedHat's GCC snapshot "2.96" handles this case just fine.
>
> Now, if you can isolate the relevant part of the diff between 2.95.2 and
> RH 2.96...
Well, now that there is a testcase, has anyone sent this on to the relevant
gcc lists? (The CCs I saw haven't)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-24 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 1:57 Andries.Brouwer
2000-11-24 4:10 ` Chris Wedgwood
2000-11-24 6:10 ` Peter Samuelson
2000-11-24 8:27 ` kumon
2000-11-24 4:34 ` Gregory Maxwell
2000-11-24 4:47 ` Alexander Viro
2000-11-24 15:23 ` Tom Rini [this message]
2000-11-24 15:41 ` Bernd Schmidt
2000-11-26 16:09 ` Alessandro Suardi
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=20001124082324.A872@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bernds@redhat.com \
--cc=greg@linuxpower.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®