Re: OpenBSD/Sparc status - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: OpenBSD/Sparc status
Date
Msg-id 2694.24.211.141.25.1101039155.squirrel@www.dunslane.net
Whole thread Raw
In response to Re: OpenBSD/Sparc status  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Responses Re: OpenBSD/Sparc status  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Stefan Kaltenbrunner said:
> Tom Lane wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>
>>>Meanwhile, what do we do? Turn off -O in src/template/openbsd for
>>>some/all releases?
>>
>>
>> Certainly not.  This problem is only known to exist in one gcc version
>> for one architecture, and besides it's only affecting (so far as we
>> can tell) one rather inessential contrib module.  I'd say ignore the
>> test failure until Stefan can get a fixed gcc.
>
> FWIW: I got the bug confirmed by Miod Vallat (OpenBSD hacker) on IRC,
> it  looks that at least OpenBSD 3.6-STABLE and OpenBSD-current on
> Sparc64  with the stock system compiler are affected.


I guess my concern is that on Sparc64/OpenBSD-3.6* at least, this bug is
exposed by the seg tests but might well occur elsewhere and bite us in
various unpleasant ways.

I have no idea how many people out there are using this combination. Of
course, even it it's only one (and I suspect that's the right order of
magnitude) we should want to be careful with their data.

cheers

andrew






pgsql-hackers by date:

Previous
From: "John Hansen"
Date:
Subject: Re: Unicode characters above 0x10000 #2
Next
From: Joe Conway
Date:
Subject: Re: How to check the postgresql version