From: "J . A . Magallon" <jamagallon@able.es>
To: J Sloan <jjs@lexus.com>
Cc: "T . A ." <tkhoadfdsaf@hotmail.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Re: Which kernel (Linus or ac)?
Date: Sat, 13 Oct 2001 00:59:30 +0200 [thread overview]
Message-ID: <20011013005930.I1693@werewolf.able.es> (raw)
In-Reply-To: <XFMail.20011011094548.jkp@riker.nailed.org> <3BC5E152.3D81631@bigfoot.com> <3BC5E3AF.588D0A55@lexus.com> <3BC5EB56.21B4EF88@bigfoot.com> <3BC5FA12.F8E5C91E@lexus.com> <OE64cxtniFKULPEhGD100007fff@hotmail.com> <3BC688A2.4C7640B7@pobox.com> <OE394qrvAsp4XgWZGbR0000e29d@hotmail.com> <3BC729E2.E93A416E@lexus.com>
In-Reply-To: <3BC729E2.E93A416E@lexus.com>; from jjs@lexus.com on Fri, Oct 12, 2001 at 19:35:30 +0200
On 20011012 J Sloan wrote:
>After this post we should take it offline and
>let the s/n ratio on lkml settle back down to
>a dull roar - apologies for the noise, this is
>the last post on this dead horse.
>
>"T. A." wrote:
>
>
>Here is a heads-up for the benefit of those wondering
>about gcc-2.96:
>
>http://www.bero.org/gcc296.html
>
Nice, a bunch of comments about the front end. But you miss the point
that what was broken in gcc-2.96 was the back end (the optimizer).
And you missed that it needed about 50 updates to get a real compiler.
gcc that ships with RH 7.1 generates bad code in optimized mode. Do not
remember the exact post in LKML, but I saw 2 lines of code that made gcc
put the user initialization of a variable before the automatic one to zero.
If you want a good distro, take Mandrake 8.1.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.13-pre1-beo #1 SMP Fri Oct 12 11:32:03 CEST 2001 i686
next prev parent reply other threads:[~2001-10-12 22:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 14:45 Which kernel (Linus or ac)? jkp
2001-10-11 17:42 ` Robert Love
2001-10-11 17:52 ` Tim Connors
2001-10-11 18:11 ` Tim Moore
2001-10-12 2:01 ` Horst von Brand
[not found] ` <001901c152ca$0b42c080$0600000a@petersohn.net>
2001-10-12 18:32 ` Tim Moore
2001-10-11 18:13 ` Tim Moore
2001-10-11 18:23 ` J Sloan
2001-10-11 18:56 ` Tim Moore
2001-10-11 19:59 ` [OT] " J Sloan
2001-10-12 4:42 ` T. A.
2001-10-12 6:07 ` J Sloan
2001-10-12 9:14 ` T. A.
2001-10-12 9:59 ` Luigi Genoni
2001-10-12 17:35 ` J Sloan
2001-10-12 22:59 ` J . A . Magallon [this message]
2001-10-11 23:50 ` Oden Eriksson
2001-10-11 23:56 ` Arnaldo Carvalho de Melo
2001-10-12 0:09 ` J Sloan
2001-10-12 4:37 ` T. A.
2001-10-12 6:56 ` Ville Herva
2001-10-12 9:25 ` T. A.
2001-10-12 10:02 ` Ville Herva
2001-10-12 11:35 ` Andrea Arcangeli
2001-10-11 19:43 ` M. R. Brown
2001-10-11 22:05 ` Luigi Genoni
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=20011013005930.I1693@werewolf.able.es \
--to=jamagallon@able.es \
--cc=jjs@lexus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tkhoadfdsaf@hotmail.com \
/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.