On Fri, Aug 09, 2002 at 10:10:00AM +0300, Oleg Goldshmidt wrote: > Muli Ben-Yehuda <[EMAIL PROTECTED]> writes: > > > I was thinking of kernel compilation, which requires -O2 (force > > inlining) > > -O3 turns -finline-functions on. -O2 turns -fforce-mem on, maybe > that's what you meant.
The kernel documentaion requires that it be compiled with -O2 in order
to force inlining of inline functions. If -O2 does not really force
inlining, that bear investigating further.
see Documentatoin/Changes "In addition, please pay attention to
compiler optimization. Anything greater than -O2 may not be wise."
> > and thus would break horribly if you compile some of the files with
> > O1.
>
> Why? Why should compilation of different files affect each other?
> Do you mean that the *kernel* (as opposed to compilation) would break
> horribly at run time if compiled without -O2?
I thought that's what I said. -ENOTENOUGHCOFFEE ;)
--
"Hmm.. Cache shrink failed - time to kill something?
Mhwahahhaha! This is the part I really like. Giggle."
-- linux/mm/vmscan.c
http://vipe.technion.ac.il/~mulix/ http://syscalltrack.sf.net
msg20889/pgp00000.pgp
Description: PGP signature
