There is also an issue with PPC processors with +/-0 in the cube test:
*** ./expected/cube.out Thu Jul 27 05:23:14 2006
--- ./results/cube.out Thu Jul 27 05:43:21 2006
***************
*** 144,150 ****
SELECT '-1e-700'::cube AS cube;
cube
------
! (0)
(1 row)
SELECT '1234567890123456'::cube AS cube;
--- 144,150 ----
SELECT '-1e-700'::cube AS cube;
cube
------
! (-0)
(1 row)
SELECT '1234567890123456'::cube AS cube;
I am seeing a reodering of results issue on my AIX box, for both gcc and
native CC.
Check the buildfarm members asp and kookaburra.
It looks like the alternate expected files need to be updated as well.
-rocco
> -----Original Message-----
> From: pgsql-patches-owner@postgresql.org
> [mailto:pgsql-patches-owner@postgresql.org] On Behalf Of Joshua Reich
> Sent: Thursday, July 27, 2006 11:04 AM
> To: Andrew Dunstan
> Cc: Tom Lane; pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] [HACKERS] [COMMITTERS] pgsql:
> /contrib/cube improvements:
>
>
> You are correct.
>
> Patch against the latest HEAD attached.
>
> Josh
>
> Andrew Dunstan wrote:
> > Joshua Reich wrote:
> >
> >> Ok. Here is a diff taken from the top of the contrib tree. I have
> >> suppressed the notices in both the cube and earthdistance
> packages.
> >> All tests pass.
> >>
> >
> > Doesn't this contain parts that have been already applied?
> It looks to
> > me like you need to do a cvs update (and then a subsequent
> clean and
> > test) before generating the diff.
> >
> > cheers
> >
> > andrew
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 4: Have you searched our list archives?
> >
> > http://archives.postgresql.org
>