From: Thomas Pornin <Thomas.Pornin@ens.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: GCC3.0 Produce REALLY slower code!
Date: Tue, 26 Jun 2001 09:40:16 +0200 [thread overview]
Message-ID: <20010626094016.A5899@bolet.ens.fr> (raw)
In-Reply-To: <200106260121.f5Q1LuE14141@habitrail.home.fools-errant.com>
In article <200106260121.f5Q1LuE14141@habitrail.home.fools-errant.com>
you write:
> Then there's the other question: Why should we test a compiler that
> seems to be quite proprietary?
Apart from questions of optimization, compiling the same code with two
different compilers is a very good way to find bugs, both in the code
and in the compilers.
Besides, the kernel is, for now, dependent on many gcc features; but
it might be worth thinking about writing code a bit more "standard",
just in case another free C compiler emerges on some specific arch. Then
again, aiming at compiling with several compilers is one way to achieve
portability.
(yet I do not believe it will happen anyday soon)
--Thomas Pornin
next prev parent reply other threads:[~2001-06-26 7:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0106251339370.13095-100000@rudy.mif.pg.gda.pl>
2001-06-25 11:53 ` Alexander V. Bilichenko
2001-06-25 23:30 ` Hacksaw
2001-06-26 0:29 ` Alexander V. Bilichenko
2001-06-26 1:21 ` Hacksaw
2001-06-26 7:40 ` Thomas Pornin [this message]
2001-06-26 8:18 ` Hacksaw
2001-06-24 22:44 Alexander V. Bilichenko
2001-06-24 22:48 ` Rik van Riel
2001-06-24 23:46 ` Luigi Genoni
2001-06-25 9:33 ` Thomas Pornin
2001-06-24 23:19 ` Daniel Phillips
2001-06-25 9:16 ` Matthias Andree
2001-06-25 11:31 ` Alexander V. Bilichenko
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=20010626094016.A5899@bolet.ens.fr \
--to=thomas.pornin@ens.fr \
--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
all inboxes | Powered by JetHome®