Date: Fri, 13 Jul 2007 14:01:49 +0200
From: Zdenek Kotala <Zdenek.Kotala@Sun.COM>
Subject: Re: compiler warnings on the buildfarm
In-reply-to: <4696548D.7020406@kaltenbrunner.cc>
To: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Cc: Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Message-id: <469769AD.5000703@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <46962BBD.5000108@kaltenbrunner.cc>
	<200707121744.22730.peter_e@gmx.net>
	<4696548D.7020406@kaltenbrunner.cc>
User-Agent: Thunderbird 2.0.0.0 (X11/20070508)

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