mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
To: Robert Love <rml@tech9.net>
Cc: 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: Thu, 20 Dec 2001 01:10:09 +0100	[thread overview]
Message-ID: <20011220001006.GA18071@arthur.ubicom.tudelft.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10112192037490.3265-100000@luxik.cdi.cz> <1008792213.806.36.camel@phantasy>
In-Reply-To: <1008792213.806.36.camel@phantasy>

On Wed, Dec 19, 2001 at 03:03:30PM -0500, Robert Love wrote:
> On Wed, 2001-12-19 at 14:39, Martin Devera wrote:
> > 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.

It doesn't change syntax, but anything lower than -O1 simply doesn't
inline functions with an "inline" attribute. The result is that the
inline functions in header files won't get inlined and the compiler
will complain about missing functions at link time (or module insert
time).

I'm actually surprised that 2.2 can be compiled with -O, AFAIK
linux-2.2 also has a lot of inline functions in headers. I know from
experience that -Os works for 2.4 kernels on ARM, I haven't tested it
with 2.2 or x86.


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Faculty
of Information Technology and Systems, Delft University of Technology,
PO BOX 5031, 2600 GA Delft, The Netherlands  Phone: +31-15-2783635
Fax: +31-15-2781843  Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/

  reply	other threads:[~2001-12-20  0:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 18:55 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 [this message]
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

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=20011220001006.GA18071@arthur.ubicom.tudelft.nl \
    --to=j.a.k.mouw@its.tudelft.nl \
    --cc=clubneon@hereintown.net \
    --cc=devik@cdi.cz \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®