From: Stef van der Made <svdmade@planet.nl>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: gcc 2.95.3
Date: Sat, 24 Jan 2004 00:20:02 +0100 [thread overview]
Message-ID: <4011AC22.8050903@planet.nl> (raw)
In-Reply-To: <1074882836.20723.4.camel@minerva>
Matthew Reppert wrote:
>snip
>
>
>Many people have been using gcc-3.2 or later to build kernels, and I
>haven't really heard of any problems with this, at least on i386. I
>personally have used 3.2.2 and 3.3.2 (well, with Debian's patches) and
>haven't had any weirdness with 2.6 or 2.4. ISTR there being arches that
>need 3.x to compile, but I could be mistaken.
>
>2.95.3 is definitely the *oldest* compiler you'd want to use, and pretty
>much skip between that and 3.2.
>
>Matt
>
>
Same here. I've been using gcc3.2.0 and beyond currently 3.3.2 since the
day they were released and never had any big issues. I would recomend
using gcc 3.3.2 since it improves performance when using optimizations
quite a bit as far as I can remember the statistics.
Stef
next prev parent reply other threads:[~2004-01-23 23:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 14:50 make in 2.6.x Karel Kulhavý
2004-01-23 15:11 ` Bas Mevissen
2004-01-23 15:20 ` Sam Ravnborg
2004-01-23 15:39 ` David Woodhouse
[not found] ` <20040123100035.73bee41f.jeremy@kerneltrap.org>
2004-01-23 15:13 ` gcc 2.95.3 Karel Kulhavý
2004-01-23 16:03 ` Daniel Andersen
[not found] ` <001b01c3e1ca$26101f20$1e00000a@black>
2004-01-23 16:30 ` Karel Kulhavý
2004-01-23 18:33 ` Matthew Reppert
2004-01-23 23:20 ` Stef van der Made [this message]
2004-01-24 0:48 ` Russell King
2004-01-26 14:41 ` David Woodhouse
2004-01-24 12:46 ` Ingo Buescher
2004-01-24 18:32 ` Stef van der Made
2004-01-23 18:55 ` Felipe Alfaro Solana
2004-01-25 11:05 ` Florian Weimer
2004-01-23 15:20 ` make in 2.6.x Karel Kulhavý
2004-01-23 17:42 ` Wakko Warner
2004-01-23 20:32 ` Sam Ravnborg
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=4011AC22.8050903@planet.nl \
--to=svdmade@planet.nl \
--cc=linux-kernel@vger.kernel.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