Marko Kreen <mark...@gmail.com> writes:
> On 12/16/09, Kurt Harriman <harri...@acm.org> wrote:
>> For gcc, I think the __attribute__ has to come after the function's
>> parameter list, rather than before the return type.
> No.
[ squint... ] That's nowhere documented that I can find: all the
examples in the gcc docs show __attribute__ after the parameters.
It does seem to work, but should we rely on it?
The bigger problem though is that not all versions of gcc understand
always_inline:
$ gcc -Wall check.c
check.c:3: warning: `always_inline' attribute directive ignored
which I think is sufficient reason to put an end to this sub-thread.
We have no particular need for force-inline semantics anyway, as
long as the compiler behaves reasonably for unreferenced inlines,
which gcc always has.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
