Re: [patch] measurements, numbers about CONFIG_OPTIMIZE_INLINING=y impact

Valdis.Kletnieks
2009-01-11T22:45:34Z

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

On Fri, 09 Jan 2009 08:34:57 PST, "H. Peter Anvin" said:

> A lot of noise is being made about the naming of the levels (and I
> personally believe we should have a different annotation for "inline
> unconditionally for correctness" and "inline unconditionally for
> performance", as a documentation issue), but those are the four we get.

I know we use __builtin_return_address() in several places, and several
other places we introspect the stack and need to find the right frame entry.
Are there any other places that need to be inlined for correctness?

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]