From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kris Jurka <books(at)ejurka(dot)com>, Gevik Babakhani <pgdev(at)xs4all(dot)nl>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 2x compile warning |
Date: | 2006-04-24 20:11:12 |
Message-ID: | 200604242011.k3OKBCa09990@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Kris Jurka <books(at)ejurka(dot)com> writes:
> > Also I was testing a gcc 4.2 snapshot (20060419) and it has a whole lot of
> > warnings stemming from heap_getattr's isnull check:
> > aclchk.c:791: warning: the address of 'isNull', will always evaluate as
> > 'true'
>
> We need to lobby the gcc maintainers to not give warnings about valid
> and perfectly reasonable code. I'm not thrilled with changing the API
> of a key macro for no other reason than that gcc has started to complain
> about it.
Right. The issue is that when I originally transfered that function to
a macro, the isnull parameter was optionally 0/NULL. While our code
doesn't use that ability, I see no reason to remove it.
I understand why it is complaining because you are really doing if
(&var), but it is a macro, so it can be used in other circumstances as
well.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-24 20:22:57 | Re: Regression error on float8 |
Previous Message | Magnus Hagander | 2006-04-24 20:03:57 | Re: Regression error on float8 |