On Tue, Mar 24, 2009 at 10:53 PM, Martijn van Oosterhout <klep...@svana.org> wrote: > Sorry, I meant to say that the compiler could determine the address at > compile time, something like: > > __builtin_constant_p( !&(__x)) )
Hm, that's a better idea. How about something like (__builtin_constant_p(__x) || __builtin_constant_p(!&(__x))) This would still pass expressions like foo[x] even if x might be out-of-bounds or foo might be pointed to a freed object or something like that though. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
