From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Adrian Bunk <bunk@stusta.de>, linux-kernel@vger.kernel.org
Subject: Re: RFC: Raise required gcc version to 3.2 ?
Date: Thu, 28 Jul 2005 09:59:55 -0400 [thread overview]
Message-ID: <20050728135955.GC31019@csclub.uwaterloo.ca> (raw)
In-Reply-To: <m3hdefxfyn.fsf@defiant.localdomain>
On Thu, Jul 28, 2005 at 02:39:12PM +0200, Krzysztof Halasa wrote:
> Compilation speed? Don't know, using 3 (4?) years old Athlon 2000
> it's not a problem unless I need full build 30 times a day.
>
> But people on 266 MHz ARM5 may notice.
Hmm, an a 400Mhz PXA 255 I found using gcc 3.x meant I could use xscale
rather than older optimizations, and the resulting kernel certainly felt
much faster (I never did actually meassure if it was faster or not).
Using gcc 2.95 requried changing the cpu optimization lines in the
kernel. Of course this was in a kernel patched with the pxa arm patches
so it isn't quite the same as the mainline kernel. I certainly won't
consider using gcc 2.95 on an arm anymore (although perhaps on older arm
models it does make sense).
I have no idea if it took longer to compile with gcc 3.x, but the result
seemed better to me. To me performance of the resulting kernel is more
important than performance compiling the kernel.
Of course if you leave the choice as 2.95 and above rather than 3.2 and
above, people can pick whatever they want based on their needs.
Len Sorensen
next prev parent reply other threads:[~2005-07-28 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 12:00 Adrian Bunk
2005-07-28 12:39 ` Krzysztof Halasa
2005-07-28 13:59 ` Lennart Sorensen [this message]
2005-07-28 17:05 ` Christoph Lameter
2005-07-28 16:48 Mikael Pettersson
2005-07-29 15:56 ` Adrian Bunk
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=20050728135955.GC31019@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=bunk@stusta.de \
--cc=khc@pm.waw.pl \
--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®