From: "J.A. Magallon" <jamagallon@able.es>
To: Pavel Machek <pavel@suse.cz>
Cc: Robert Love <rml@tech9.net>, Martin Devera <devik@cdi.cz>,
Chris Meadors <clubneon@hereintown.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: gcc 3.0.2/kernel details (-O issue)
Date: Sun, 23 Dec 2001 00:54:28 +0100 [thread overview]
Message-ID: <20011223005428.I6735@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.10.10112192037490.3265-100000@luxik.cdi.cz> <1008792213.806.36.camel@phantasy> <20011222215457.A118@elf.ucw.cz>
In-Reply-To: <20011222215457.A118@elf.ucw.cz>; from pavel@suse.cz on Sat, Dec 22, 2001 at 21:54:58 +0100
On 20011222 Pavel Machek wrote:
>Hi!
>
>> > It is interesting that 2.2 can be done with -O. Also I'd expect
>> > errors during compilation and not silent crash...
>>
>> Well, you certainly won't get errors, because compiler optimizations
>> shouldn't change expected syntax.
>>
>> -O2 is the standard optimization level for the kernel; everything is
>> compiled via it. When developers test their code, nuances that the
>> optimization introduce are accepted. Removing the optimization may
>> break those expectations. Thus the kernel requires it.
>
>Huh? Those expectations are *bugs*.
>
>Kernel will not link without optimalizations because it *needs*
>inlining. Any else dependency is a *bug*.
> Pavel
Wouldn't it be better to mark such places with something like
#pragma inline, if gcc allows it, than relaying on gcc guesses about
inlining, or options activated in O2 ?
--
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.17-beo #1 SMP Fri Dec 21 21:39:36 CET 2001 i686
prev parent reply other threads:[~2001-12-22 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 18:55 gcc 3.0.2/kernel details (-O issue) devik
2001-12-19 19:49 ` Chris Meadors
2001-12-19 19:39 ` Martin Devera
2001-12-19 20:03 ` Robert Love
2001-12-20 0:10 ` Erik Mouw
2001-12-20 3:39 ` H. Peter Anvin
2001-12-20 9:22 ` J.A. Magallon
2001-12-20 12:03 ` H. Peter Anvin
2001-12-20 10:30 ` devik
2001-12-22 20:54 ` Pavel Machek
2001-12-22 23:35 ` devik
2001-12-22 23:54 ` J.A. Magallon [this message]
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=20011223005428.I6735@werewolf.able.es \
--to=jamagallon@able.es \
--cc=clubneon@hereintown.net \
--cc=devik@cdi.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rml@tech9.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