From: Andries Brouwer <aeb@veritas.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc-2.95.2-51 is buggy
Date: Sat, 25 Nov 2000 21:01:47 +0100 [thread overview]
Message-ID: <20001125210147.A6798@veritas.com> (raw)
In-Reply-To: <14878.58.908955.701821@notabene.cse.unsw.edu.au> <Pine.LNX.4.21.0011251522430.8818-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0011251522430.8818-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Sat, Nov 25, 2000 at 03:26:15PM -0200
On Sat, Nov 25, 2000 at 03:26:15PM -0200, Rik van Riel wrote:
> The gcc-2.95.2-6cl from Conectiva 6.0 is buggy too.
Yes. Probably you have seen it by now, but the difference between
good and bad versions of gcc-2.95.2 did not lie in the applied patches,
but was the difference between compilation for 686 or 386.
It is not your (SuSE's, Debian's) fault. A fix already exists.
Andries
-
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-25 20:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-24 5:20 gcc-2.95.2-51 is buggy Andries.Brouwer
2000-11-24 5:44 ` Neil Brown
2000-11-24 6:47 ` Alexander Viro
2000-11-25 17:26 ` Rik van Riel
2000-11-25 19:16 ` Jeff V. Merkey
2000-11-25 20:01 ` Andries Brouwer [this message]
2000-11-25 20:06 ` Rik van Riel
2000-11-26 15:33 ` Olaf Dietsche
2000-11-26 16:58 ` Rik van Riel
2000-11-26 19:36 ` Mike Castle
2000-11-26 19:41 ` Russell King
2000-11-26 19:55 ` J . A . Magallon
2000-11-24 9:37 ` Ion Badulescu
2000-11-24 10:18 ` Linux Kernel Developer
2000-11-24 9:57 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2000-11-24 8:09 Frédéric L . W . Meunier
2000-11-24 12:48 Andries.Brouwer
2000-11-24 16:46 ` Matthew Vanecek
2000-11-24 13:04 Mikael Pettersson
2000-11-27 14:28 Pavel Pisa;research student
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=20001125210147.A6798@veritas.com \
--to=aeb@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.