GCC 3.3 release criteria

[Robert Dewar]

> A common coding style (at least around here) is to write rather big
> and complex inline functions (frequently containing calls to other big
> inline functions), assuming that they will collapse to relatively
> little code when instantiated, because of constant folding and
> dead-code removal. Quite often the resulting code is smaller than the
> function call to a non-inlined function.

Indeed that is a common style, and I would say that if the compiler does
not inline in such a case, then even if the inline keyword is advisory,
this would seem to be a bug!