From: Andi Kleen <ak@muc.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Recommended compiler version
Date: Sat, 29 May 2004 12:51:52 +0200 [thread overview]
Message-ID: <m3brk7pktz.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <218aB-15c-17@gated-at.bofh.it> (Francois Romieu's message of "Sat, 29 May 2004 11:20:09 +0200")
Francois Romieu <romieu@fr.zoreil.com> writes:
> The linux kernel README and Documentation/CHANGES suggests to use
> gcc 2.95.3. These files have not been updated for ages. Is there
> a rough consensus regarding the required versions of the different
> tools in the buildchain or should one simply submit a patch to remove
> the offending files ?
I would suggest to just remove them. We're past the state when each new
compiler version broke the kernel. Originally that was a lot due
to buggy inline assembly etc., but that should be all fleshed out now.
> I forgot to mention: 2.95.3 does not compile correctly the 2.6.6 r8169
> driver.
Make it an #error then. Better a compile time error than a mysterious
malfunction.
-Andi
next parent reply other threads:[~2004-05-29 10:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <218aB-15c-17@gated-at.bofh.it>
2004-05-29 10:51 ` Andi Kleen [this message]
2004-05-29 14:42 Recommended compiler version Dan Kegel
2004-05-29 23:55 ` Karim Yaghmour
2004-05-29 23:20 ` Dan Kegel
2004-05-30 0:40 ` Karim Yaghmour
2004-05-30 0:38 ` Karim Yaghmour
2004-05-30 10:37 ` John Bradford
-- strict thread matches above, loose matches on Subject: below --
2004-05-29 9:16 Francois Romieu
2004-05-29 9:52 ` Francois Romieu
2004-05-29 13:30 ` John Bradford
2004-05-29 14:12 ` Francois Romieu
2004-05-29 14:31 ` Adrian Bunk
2004-05-29 14:57 ` John Bradford
2004-05-30 1:18 ` George Georgalis
2004-05-29 14:53 ` John Bradford
2004-05-29 16:58 ` Francois Romieu
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=m3brk7pktz.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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.