Re: compiler warnings on the buildfarm - Mailing list pgsql-hackers

From Zdenek Kotala
Subject Re: compiler warnings on the buildfarm
Date
Msg-id 469769AD.5000703@sun.com
Whole thread Raw
In response to Re: compiler warnings on the buildfarm  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: compiler warnings on the buildfarm  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
List pgsql-hackers
Stefan Kaltenbrunner wrote:
> Peter Eisentraut wrote:
>> Am Donnerstag, 12. Juli 2007 15:25 schrieb Stefan Kaltenbrunner:
>>> a lot of those are simply noise (like the LOOP VECTORIZED stuff from the
>>> icc boxes or the "statement not reached" spam from the sun compilers)
>>> but others might indicate real issues.
>>> To find warnings that might be a real problem we might want to look into
>>>  suppressing those - if possible -  using compiler switches.
>> It would be good to determine an appropriate set of compiler switches to 
>> reduce the warnings to a reasonable level.
> 
> yeah once we have determined that this whole experiment is useful it
> should be pretty easy to tweak the compiler switches for the non-gcc
> compilers (mostly icc and sun studio seem to be the ones that generate
> excessive output).
> 

For sun studio -erroff=E_STATEMENT_NOT_REACHED is useful there. If you 
want to determine warning tags for each warning add -errtags.

    Zdenek


pgsql-hackers by date:

Previous
From: Martin Pihlak
Date:
Subject: stored procedure stats in collector
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: compiler warnings on the buildfarm