Re: compiler warnings on the buildfarm

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: compiler warnings on the buildfarm
Date: 2007-07-13 12:19:30
Message-ID: 46976DD2.3050202@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala wrote:
> 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.

Is that supported on all versions of sun studio(Sun WorkShop 6, Sun
Studio 8,11) we have on the farm ?

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2007-07-13 12:25:16 Re: compiler warnings on the buildfarm
Previous Message Zdenek Kotala 2007-07-13 12:01:49 Re: compiler warnings on the buildfarm