[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#730830: ocaml: Please add powerpcspe to the list of native architectures



Hi,

On 01/12/13 12:59, Stéphane Glondu wrote:
> almabench is very intensive and also times out on some buildds. I am
> planning to disable it on $(SLOW_ARCHITECTURES) (defined in
> debian/rules, which includes powerpc). I can add powerpcspce there as well.

Yes, please do. I tried to let it run for a few days bit gave up today -
still not finished...

> Thanks for the build log. It doesn't look severely broken, but test
> failures must be further investigated:
> 
>  * Native backtrace tests are completely broken, but it is also the
>    case on powerpc but it seems to have been fixed upstream.

OK, considering it the same issue as on powerpc.

>  * tests/lib-bigarray/fftba.ml: no idea what's going on. It would be
>    nice to get tests/lib-bigarray/fftba.output and compare with
>    tests/lib-bigarray/fftba.reference.

I'm attaching the two: The diff is:

--- fftba.reference	2010-01-25 14:01:33.000000000 +0000
+++ fftba.result	2013-12-01 13:37:42.657964357 +0000
@@ -1,13 +1,13 @@
-16... ok
-32... ok
-64... ok
-128... ok
-256... ok
-512... ok
-1024... ok
-2048... ok
-4096... ok
-8192... ok
-16384... ok
-32768... ok
-65536... ok
+16... ERROR
+32... ERROR
+64... ERROR
+128... ERROR
+256... ERROR
+512... ERROR
+1024... ERROR
+2048... ERROR
+4096... ERROR
+8192... ERROR
+16384... ERROR
+32768... ERROR
+65536... ERROR

>  * tests/misc/nucleic.ml: fails with
>      Fatal error: exception Assert_failure("nucleic.ml", 3205, 9)
>    which is very weird and looks difficult to figure out.

Please tell if I can help here somehow.

> The first point is explained and would not prevent a switch, but I think
> the last two should at least be explained before making powerpcspe
> native. Is there a powerpcspe porterbox available for DDs?

Not currently, but I'm working towards this - negotiating with a former
employer of a former powerpcspe port maintainer.

Roland

16... ok
32... ok
64... ok
128... ok
256... ok
512... ok
1024... ok
2048... ok
4096... ok
8192... ok
16384... ok
32768... ok
65536... ok
16... ERROR
32... ERROR
64... ERROR
128... ERROR
256... ERROR
512... ERROR
1024... ERROR
2048... ERROR
4096... ERROR
8192... ERROR
16384... ERROR
32768... ERROR
65536... ERROR

Reply to: