Here are some test results for various linux ports, ran on Debian unstable:

builds logs (except for mips) can be found at:
https://buildd.debian.org/status/package.php?p=libffi&suite=experimental

i386 and amd64 look ok.

arm-unknown-linux-gnueabi:
XPASS: libffi.call/cls_longdouble.c -O0 -W -Wall execution test
XPASS: libffi.call/cls_longdouble.c -O2 execution test
XPASS: libffi.call/cls_longdouble.c -O3 execution test
XPASS: libffi.call/cls_longdouble.c -Os execution test
XPASS: libffi.call/cls_longdouble.c -O2 -fomit-frame-pointer execution test
Running /build/buildd-libffi_3.0.10~rc8-1-armel-3UaGFl/libffi-3.0.10~rc8/testsuite/libffi.special/special.exp ...

                === libffi Summary ===

# of expected passes            1639
# of unexpected successes       5
# of unsupported tests          15

ia64:
                === libffi Summary ===

# of expected passes            1644
# of unsupported tests          15

kfreebsd-amd64:
                === libffi Summary ===

# of expected passes            1644
# of unsupported tests          15

kfreebsd-i386:
                === libffi Summary ===

# of expected passes            1644
# of unsupported tests          15

powerpc:
                === libffi Summary ===

# of expected passes            1644
# of unsupported tests          15


s390:
Running /build/buildd-libffi_3.0.10~rc8-1-s390-mB6C2g/libffi-3.0.10~rc8/testsuite/libffi.call/call.exp ...
FAIL: libffi.call/err_bad_abi.c -O0 -W -Wall execution test
FAIL: libffi.call/err_bad_abi.c -O2 execution test
FAIL: libffi.call/err_bad_abi.c -O3 execution test
FAIL: libffi.call/err_bad_abi.c -Os execution test
FAIL: libffi.call/err_bad_abi.c -O2 -fomit-frame-pointer execution test
Running /build/buildd-libffi_3.0.10~rc8-1-s390-mB6C2g/libffi-3.0.10~rc8/testsuite/libffi.special/special.exp ...

                === libffi Summary ===

# of expected passes            1639
# of unexpected failures        5
# of unsupported tests          15

sparc:
                === libffi Summary ===

# of expected passes            1644
# of unsupported tests          15



mips (mipsel should be the same):

                === libffi Summary ===

# of expected passes            1644
# of unsupported tests          15

however some test fail for mips64 and the new abi:

with -mabi=64:

FAIL: libffi.call/cls_double_va.c -O0 -W -Wall output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -O0 -W -Wall output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_double_va.c -O2 output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -O2 output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_double_va.c -O3 output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -O3 output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_double_va.c -Os output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -Os output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_double_va.c -O2 -fomit-frame-pointer output pattern test,

is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -O2 -fomit-frame-pointer output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
Running /home/doko/tmp/libffi-3.0.10~rc8/testsuite/libffi.special/special.exp 
...

                === libffi Summary ===

# of expected passes            1634
# of unexpected failures        10
# of unsupported tests          15



with -mabi=n32:

FAIL: libffi.call/cls_double_va.c -O0 -W -Wall output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -O0 -W -Wall output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_pointer.c -O0 -W -Wall (test for excess errors)
FAIL: libffi.call/cls_pointer_stack.c -O0 -W -Wall (test for excess errors)
FAIL: libffi.call/cls_double_va.c -O2 output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -O2 output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_pointer.c -O2 (test for excess errors)
FAIL: libffi.call/cls_pointer_stack.c -O2 (test for excess errors)
FAIL: libffi.call/cls_double_va.c -O3 output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -O3 output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_pointer.c -O3 (test for excess errors)
FAIL: libffi.call/cls_pointer_stack.c -O3 (test for excess errors)
FAIL: libffi.call/cls_double_va.c -Os output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -Os output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_pointer.c -Os (test for excess errors)
FAIL: libffi.call/cls_pointer_stack.c -Os (test for excess errors)
FAIL: libffi.call/cls_double_va.c -O2 -fomit-frame-pointer output pattern test,
is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_longdouble_va.c -O2 -fomit-frame-pointer output pattern test, is 0.0
res: 4
7.0
res: 4
, should match 7.0^M?
res: 4^M?
7.0^M?
res: 4
FAIL: libffi.call/cls_pointer.c -O2 -fomit-frame-pointer (test for excess 
errors)
FAIL: libffi.call/cls_pointer_stack.c -O2 -fomit-frame-pointer (test for excess errors)
Running /home/doko/tmp/libffi-3.0.10~rc8/testsuite/libffi.special/special.exp 
...

                === libffi Summary ===

# of expected passes            1624
# of unexpected failures        20
# of unsupported tests          15


--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4db2f583.1070...@ubuntu.com

Reply via email to