lkml.org 
[lkml]   [2009]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact
> I think that's the point. gcc will not get it right. 

I don't think that's necessary an universal truth. It
can be probably fixed.

> So we need to do it ourselves in the kernel sources.
> We may not like it, but it's the only way to guarantee reproducable
> reliable inline / noinline decisions.

For most things we don't really need it to be reproducable,
the main exception are the inlines in headers.

Universal noinline would also be a bad idea because of its
costs (4.1% text size increase). Perhaps should make it
a CONFIG option for debugging though.

-Andi



>
> /D
>
> --
> Dirk Hohndel
> Intel Open Source Technology Center
>

--
ak@linux.intel.com


\
 
 \ /
  Last update: 2009-01-09 18:51    [W:0.265 / U:0.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site