possible patch

[Phil Edwards]

> I wonder why library compilation needs -Winline at all. When you write
> the library functions, you tag some as 'inline' based on your
> experience with the C++ language, just as you make other
> implementation decisions. It is not a serious problem if you mark some
> functions with inline that can't be inlined.

Just for the record, the functions in question aren't marked as inline;
they are defined in the header.  As Benjamin pointed out, -O2 is where the
new inliner starts working on those kinds of functions.  The other kind,
which must be marked as inline, get it at -O3.

(Unless I'm completely wrong again.)


> No. Please have a look at the documentation, in particular:
[snip for space]

Ah, that's good to know.  The -finline-functions flag was the only one I
recalled from before.  (GCC's -f flags are like socks or wire coat-hangers;
leave them alone for a little while and they start to breed.)


Thanks!
Phil