From: Adrian Bunk <bunk@fs.tum.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: John Bradford <john@grabjohn.com>, linux-kernel@vger.kernel.org
Subject: Re: Recommended compiler version
Date: Sat, 29 May 2004 16:31:35 +0200 [thread overview]
Message-ID: <20040529143135.GR16099@fs.tum.de> (raw)
In-Reply-To: <20040529161247.A19214@electric-eye.fr.zoreil.com>
On Sat, May 29, 2004 at 04:12:47PM +0200, Francois Romieu wrote:
>...
> It makes no sense to religiously recommended 2.95.3 if it is known broken.
In my experience, 2.95.3 isn't more broken than the average 3.3
compiler.
> If nobody comes with a better approach, I'll simply submit a patch to
> remove the 2.95.3 recommendation (+ #error for the driver as suggested by ak).
The common solution in the kernel for such issues is to change the code
to compile correctly with all supported compilers.
This might not be a perfect solution, but otherwise different drivers
might require different compiler versions resulting in a chaos.
Whether support for gcc 2.95 should be dropped is a discussion for 2.7.
> Ueimor
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-05-29 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 9:16 Recommended compiler version 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 [this message]
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
[not found] <218aB-15c-17@gated-at.bofh.it>
2004-05-29 10:51 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-05-29 14:42 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
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=20040529143135.GR16099@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=john@grabjohn.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox