Re: [PATCH] gcc warning 'expression which evaluates to zero treated as a null pointer'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: didier <did447(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] gcc warning 'expression which evaluates to zero treated as a null pointer'
Date: 2019-11-13 21:01:19
Message-ID: 3243.1573678879@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

didier <did447(at)gmail(dot)com> writes:
> clang -E output before 7a0574b5
> HeapTuple newtuple = 0;
> with 7a0574b5
> HeapTuple newtuple = ((bool) 0);

Hm, did you re-run configure after 7a0574b5? If you didn't, it would
have gone through the not-stdbool.h path in c.h, which might account
for this. It's a good catch though, even if by accident :-)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2019-11-13 21:25:27 Re: Building infrastructure for B-Tree deduplication that recognizes when opclass equality is also equivalence
Previous Message didier 2019-11-13 20:38:12 Re: [PATCH] gcc warning 'expression which evaluates to zero treated as a null pointer'