From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: inline newNode() |
Date: | 2002-10-07 22:29:03 |
Message-ID: | 87ptulq3ww.fsf@mailbox.samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> How much did you bloat the code? There are an awful lot of calls to
> newNode(), so even though it's not all that large, I'd think the
> multiplier would be nasty.
The patch increases the executable from 12844452 to 13005244 bytes,
when compiled with '-pg -g -O2' and without being stripped.
> This isn't portable at all, AFAIK :-(. Unfortunately I can't think
> of a portable way to do it with a macro, either.
Well, one alternative might be to provide 2 definitions of the
function -- one an extern inline in the header file, and one using the
current method (in a separate file, non-inline). Then wrap the header
file in an #ifdef __GNUC__ block, and the non-inlined version in
#ifndef __GNUC__. The downside is that it means maintaining two
versions of the same function -- but given that newNode() is pretty
trivial, that might be acceptable.
BTW, the GCC docs on inline functions are here:
http://gcc.gnu.org/onlinedocs/gcc-3.2/gcc/Inline.html#Inline
According to that page, using 'static inline' instead of 'extern
inline' is recommended for future compatability with C99, so that's
what we should probably use (in the __GNUC__ version).
Cheers,
Neil
--
Neil Conway <neilc(at)samurai(dot)com> || PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | Curtis Faith | 2002-10-07 23:04:58 | Re: Analysis of ganged WAL writes |
Previous Message | Alvaro Herrera | 2002-10-07 21:45:57 | Re: 7.2.3 patching done |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-10-08 01:08:20 | Re: inline newNode() |
Previous Message | Kris Jurka | 2002-10-07 21:58:51 | Re: DBMD Patch |