Re: libffi on m68k failures
Andreas Schwab dixit:
>Thorsten Glaser <tg@mirbsd.de> writes:
>
>> The floating point errors are to be expected (on the emulator),
>
>No, they aren't.
OK. With that patch, we’re here:
Test Run By root on Sat Jan 14 18:04:27 2012
Native configuration is m68k-unknown-linux-gnu
=== libffi tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /tmp/buildd/libffi-3.0.10/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /tmp/buildd/libffi-3.0.10/testsuite/libffi.call/call.exp ...
FAIL: libffi.call/err_bad_abi.c -O0 -W -Wall execution test
FAIL: libffi.call/nested_struct2.c -O0 -W -Wall execution test
FAIL: libffi.call/err_bad_abi.c -O2 execution test
FAIL: libffi.call/nested_struct2.c -O2 execution test
FAIL: libffi.call/return_sc.c -O2 execution test
FAIL: libffi.call/err_bad_abi.c -O3 execution test
FAIL: libffi.call/nested_struct2.c -O3 execution test
FAIL: libffi.call/return_sc.c -O3 execution test
FAIL: libffi.call/err_bad_abi.c -Os execution test
FAIL: libffi.call/nested_struct2.c -Os execution test
FAIL: libffi.call/return_sc.c -Os execution test
FAIL: libffi.call/err_bad_abi.c -O2 -fomit-frame-pointer execution test
FAIL: libffi.call/nested_struct2.c -O2 -fomit-frame-pointer execution test
FAIL: libffi.call/return_sc.c -O2 -fomit-frame-pointer execution test
Running /tmp/buildd/libffi-3.0.10/testsuite/libffi.special/special.exp ...
=== libffi Summary ===
# of expected passes 1630
# of unexpected failures 14
# of unsupported tests 15
HTH & HAND,
//mirabilos
--
Support mksh as /bin/sh and RoQA dash NOW!
‣ src:bash (241 (260) bugs: 0 RC, 168 (182) I&N, 73 (78) M&W, 0 F&P)
‣ src:dash (72 (83) bugs: 3 RC, 27 (30) I&N, 42 (50) M&W, 0 F&P)
‣ src:mksh (1 bug: 0 RC, 0 I&N, 1 M&W, 0 F&P)
http://qa.debian.org/data/bts/graphs/d/dash.png is pretty red, innit?
Reply to: