Re: DTrace probes broken in HEAD on Solaris?

From: Greg Stark <stark(at)enterprisedb(dot)com>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Robert Lor <Robert(dot)Lor(at)sun(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: DTrace probes broken in HEAD on Solaris?
Date: 2009-03-24 23:09:51
Message-ID: 4136ffa0903241609w2324ae33x4a694426fb605a30@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 24, 2009 at 10:53 PM, Martijn van Oosterhout
<kleptog(at)svana(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Brent Wood 2009-03-24 23:22:06 Re: Proper entry of polygon type data
Previous Message Martijn van Oosterhout 2009-03-24 22:53:18 Re: DTrace probes broken in HEAD on Solaris?