Re: Status of CONFIG_FORCED_INLINING?

Roland Dreier
2007-05-24T17:55:46Z

> And if you #include a non-inlined definition in two .c files, the compiler
> will emit two copies into two separate .o files. What you're hoping is that
> the linker will notice they're identical and merge them, and last I checked I
> couldn't even reliably get it to do that with constant strings.

No, I don't care if the linker merges it or not. In fact I hope that
maybe the compiler is smart enough to optimize the function for the
sites it's called from in a particular .c file.

But a function defined in a .h file had better be static, so it
shouldn't matter if there are two copies of it in the final linked
image (any more than it matters if there are 100 inlined copies of it).