From: Bruno Haible <bruno@clisp.org>
To: libffi-discuss@sourceware.org
Subject: test results on many platforms
Date: Sat, 21 Oct 2017 18:31:00 -0000 [thread overview]
Message-ID: <2437301.0N14NqkuRT@omega> (raw)
Hi,
I tested libffi-3.2.1 (building from source, and then test it using the
test suite from https://haible.de/bruno/gnu/libffi-testsuite.tar.gz ).
I've registered individual bugs in https://github.com/libffi/libffi/issues .
Here's a summary of the results:
aix-powerpc-32-gcc FTBFS
aix-powerpc-32-xlc FTBFS
aix-powerpc-64-gcc FTBFS
aix-powerpc-64-xlc FTBFS
cygwin-32 failed-call, failed-callback
cygwin-64 failed-call, failed-callback
freebsd-arm64 OK
freebsd-x86-32 test-call crash, failed-callback
freebsd-x86-64 OK
hpux-hppa-32 FTBFS
hpux-hppa-64 FTBFS
hpux-ia64-32 FTBFS
hpux-ia64-64 FTBFS
hurd-x86 OK
irix-mips-32 FTBFS
irix-mips-n32-cc FTBFS
irix-mips-n32-gcc FTBFS
kfreebsd-x86-64 OK
linux-alpha test-call unaligned access
linux-alpine-x86-64 test-callback crash
linux-arm64 OK
linux-armel failed-callback
linux-armelhf FTBFS; failed-callback
linux-centos6-x86-64 OK
linux-centos7-x86-64 OK
linux-hppa test-call crash
linux-ia64 failed-call, failed-callback
linux-m68k failed-call, failed-callback
linux-mipseb-32 failed-call, failed-callback
linux-mipseb-64 failed-call, failed-callback
linux-mipseb-n32 failed-call, failed-callback
linux-mipsel-32 failed-callback
linux-mipsel-64 failed-callback
linux-mipsel-n32 failed-callback
linux-powerpc-32 failed-call, failed-callback
linux-powerpc-64 failed-call, failed-callback
linux-powerpc-64el failed-callback
linux-s390-32 failed-call, failed-callback
linux-s390-64 failed-call, failed-callback
linux-sparc-32 test-call crash, failed-callback
linux-sparc-64 test-call crash, failed-callback
linux-x86-32 OK
linux-x86-64 OK
linux-x86-x32 FTBFS
macosx-powerpc failed-call, failed-callback
macosx-x86-32 FTBFS
macosx-x86-64 test-callback crash
macosx-x86-64-clang OK
netbsd-sparc-32 test-call crash, test-callback crash
netbsd-x86-32 OK
netbsd-x86-64 test-callback crash
openbsd-x86-32 test-call crash, failed-callback
openbsd-x86-64 test-call crash
solaris10-sparc-32-cc failed-call, failed-callback
solaris10-sparc-32-gcc test-call crash, failed-callback
solaris10-sparc-64-cc FTBFS
solaris10-sparc-64-gcc test-call crash, failed-callback
solaris10-x86-32-cc FTBFS
solaris10-x86-32-gcc OK
solaris10-x86-64-cc FTBFS
solaris10-x86-64-gcc test-callback crash
windows-mingw-32 failed-call, test-callback crash
windows-mingw-64 test-call crash, failed-callback
windows-msvc-32 FTBFS
windows-msvc-64 FTBFS
Legend:
- FTBFS means "fails to build from source".
- "test-call crash" means that the test program that exercises
ffi_call() crashes.
- failed-call means that ffi_call behaves badly at runtime,
but no crash.
- "test-callback crash" means that the test program that exercises
ffi_closure crashes.
- failed-callback means that ffi_closure behaves badly at runtime,
but no crash.
Best regards,
Bruno
next reply other threads:[~2017-10-21 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 18:31 Bruno Haible [this message]
2017-10-22 8:12 ` Matthias Klose
2017-10-22 14:58 ` Bruno Haible
2017-10-22 18:28 ` Kaz Kylheku (libffi)
2017-10-22 20:33 ` small return types Bruno Haible
2017-10-22 21:38 ` Kaz Kylheku (libffi)
2017-10-25 5:18 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2437301.0N14NqkuRT@omega \
--to=bruno@clisp.org \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).