From: "J . A . Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Lost Logic <lostlogic@toughguy.net>, linux-kernel@vger.kernel.org
Subject: Re: kernel compiler
Date: Fri, 26 Oct 2001 00:00:31 +0200 [thread overview]
Message-ID: <20011026000031.A2245@werewolf.able.es> (raw)
In-Reply-To: <3BD841B7.5060405@toughguy.net> <E15wo76-0005TI-00@the-village.bc.nu>
In-Reply-To: <E15wo76-0005TI-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Oct 25, 2001 at 19:16:15 +0200
On 20011025 Alan Cox wrote:
>> GCC 3.0 Produces slower code, eh? I was of the understanding that it
>> contained many more optimizations than previous versions...???
>
>It does - but the end result right now is typically slower. it has the
>infrastructure and optimisation code to create faster code than 2.x ever
>could but it isnt yet at the point it has been refined to do so
>-
3.0.2 is out. Time to check it.
What I sure have seen is that code is much bigger than with 2.96. About 40k
for an 800k kernel.
Wil try with 14-pre1.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.14-pre1-beo #1 SMP Thu Oct 25 16:19:19 CEST 2001 i686
next prev parent reply other threads:[~2001-10-25 22:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 15:20 kernel compiler John Weber
2001-10-25 15:26 ` Axel
2001-10-25 15:45 ` Alan Cox
2001-10-25 16:45 ` Lost Logic
2001-10-25 17:16 ` Alan Cox
2001-10-25 22:00 ` J . A . Magallon [this message]
2001-10-25 22:13 ` J . A . Magallon
2001-10-26 9:18 ` Allan Sandfeld
2001-10-26 9:35 ` Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2001-10-25 14:31 Frontgate Lab
2001-10-25 15:08 ` David Weinehall
2001-10-25 15:28 ` Alan Cox
2001-10-25 15:27 ` Steve Lord
2001-10-25 15:46 ` Jakub Jelinek
2001-10-25 15:45 ` Steve Lord
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=20011026000031.A2245@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lostlogic@toughguy.net \
/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