| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: compiler warnings on the buildfarm |
| Date: | 2007-07-12 16:19:25 |
| Message-ID: | 4696548D.7020406@kaltenbrunner.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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).
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-12 16:31:36 | Re: compiler warnings on the buildfarm |
| Previous Message | Stefan Kaltenbrunner | 2007-07-12 16:15:54 | Re: compiler warnings on the buildfarm |