From: "J . A . Magallon" <jamagallon@able.es>
To: Lost Logic <lostlogic@toughguy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel compiler
Date: Fri, 26 Oct 2001 00:13:54 +0200 [thread overview]
Message-ID: <20011026001354.C2245@werewolf.able.es> (raw)
In-Reply-To: <E15wmgp-0005E8-00@the-village.bc.nu> <3BD841B7.5060405@toughguy.net>
In-Reply-To: <3BD841B7.5060405@toughguy.net>; from lostlogic@toughguy.net on Thu, Oct 25, 2001 at 18:45:43 +0200
On 20011025 Lost Logic wrote:
>GCC 3.0 Produces slower code, eh? I was of the understanding that it
>contained many more optimizations than previous versions...???
>
>Any way, I've been able to run my system based entirely on a fairly
>recent GCC CVS-3.02 snapshot, including kernels, and everything EXCEPT
>for glibc which is specifically incompatible according to the GNU folks.
>
>By way of information however, neither of the GCC 3.0 releases (3.0.0 or
>3.0.1) work at all on my system, and I cannot get a kernel to function
>at better than -O2 (not that I could get that to work in 2.95.* or
>2.96.* either).
>
-O3 activates -finline-functions:
`-finline-functions'
Integrate all simple functions into their callers. The compiler
heuristically decides which functions are simple enough to be worth
integrating in this way.
If all calls to a given function are integrated, and the function
is declared `static', then the function is normally not output as
assembler code in its own right.
Last paragraph is the key. Perhaps previous gcc'd did not all his work
as the manual says (ie, did not kill the non-inline version, bug),
but people has got used to the bug, and see it as a feature.
--
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:13 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
2001-10-25 22:13 ` J . A . Magallon [this message]
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=20011026001354.C2245@werewolf.able.es \
--to=jamagallon@able.es \
--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