Skip site navigation (1) Skip section navigation (2)

Re: elog/ereport noreturn decoration

From: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: elog/ereport noreturn decoration
Date: 2012-06-30 01:28:13
Message-ID: CAEYLb_VLRodPyzMnPWz7U9WXJQvOOW399pr9RBhWue1tet28Rg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 29 June 2012 22:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> IOW I am not on board with reducing
> the number of warnings in clang by increasing the number everywhere
> else.

I successfully lobbied the Clang developers to remove some warnings
that came from certain sites where we use a single element array at
the end of a struct as pseudo flexible arrays (Clang tried to do
compile-time bounds checking, with predictable results). Now, I had to
make a nuisance of myself in order to get that result, but you might
consider trying that.

I have been using the Clang static analyser some. I've seen all those
false positives. The greater problem is that the analyser apparently
won't work across translation units.

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services

In response to

pgsql-hackers by date

Next:From: Alex HunsakerDate: 2012-06-30 02:16:08
Subject: Re: Support for array_remove and array_replace functions
Previous:From: Edson RichterDate: 2012-06-29 23:36:38
Subject: Can someone help me to get ODBC fdw running on windows?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group