lkml.org 
[lkml]   [2008]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] prepare kconfig inline optimization for all architectures


On Sun, 27 Apr 2008, Adrian Bunk wrote:
>
> My opinion on this is still:
> "OPTIMIZE" means "work around bugs in the kernel".

No.

It means that

- gcc used to (long ago) always honor "inline", and we had kernel code
that depended on that in various ways (ie required that there was no
return etc).

We've been mostly replacing the ones we know about with
"__always_inline", but there may be some that remain. We'll find out, I
guess.

- gcc was a total and utter piece of horrible crap in the inlining
department, doign insane things and changing their documentation to
match the new behaviour (and some people then claimed that it was
always documented that way).

It would not inline big functions even when they statically collapsed
to nothing, etc.

As a result, we really couldn't afford to let gcc make any inlining
decisions, because the compiler was simply *broken*.

Linus



\
 
 \ /
  Last update: 2008-04-27 19:09    [W:0.064 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site