From: | Chris <list(at)1006(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | 8.0 beta 1 on linux-mipsel R5900 |
Date: | 2004-08-24 00:21:40 |
Message-ID: | 1093306900.7020.206.camel@dell |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I've compiled 8.0 beta 1 on a R5900 V3.1 (a playstation 2) running
Linux (PS2 Linux 1) for portability testing.
Here is what make check gave:
Without --disable-spinlocks
compilation *appears* to be fine, but the backends core dumps
on the spinlock assembly in s_lock.c (signal 4 -- illegal
instruction) on first run.
With --disable-spinlocks
all is well except the two floating point tests float4 and float8
out of 96 tests fail. This is likely due to the R5900 not being
fully IEEE-compliant(?) (regression.diffs attached).
--
I'm wondering: would it be hard to fix the assembly spinlock code
for the R5900?
If that's not worth the trouble, would it be a good idea to have
configure disable spinlocks automagically on unsupported platforms?
Or is it to hard to autodetect this?
Bye, Chris.
PS: I've compiled using gcc 2.95.2 and with CFLAGS -O0 -g.
Attachment | Content-Type | Size |
---|---|---|
regression.diffs | text/x-patch | 4.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-08-24 01:11:26 | Re: missing data/global |
Previous Message | Steve Atkins | 2004-08-24 00:12:01 | Re: fsync and hardware write cache |