From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Anthony Green <green@redhat.com>
Cc: Anthony Green <green@moxielogic.com>,
Matthias Klose <doko@ubuntu.com>,
libffi-discuss <libffi-discuss@sourceware.org>,
Debian m68k <debian-68k@lists.debian.org>,
debian-superh@lists.debian.org
Subject: Re: libffi 3.3 release candidate 1
Date: Fri, 01 Nov 2019 22:24:00 -0000 [thread overview]
Message-ID: <3a9deaae-443c-b54b-98bb-8b87468bd072@physik.fu-berlin.de> (raw)
In-Reply-To: <85954740-09a2-6e8c-7f8b-3f49d803a006@physik.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Hello!
On 11/1/19 9:01 AM, John Paul Adrian Glaubitz wrote:
> Here's the log for running the testsuite on sh4 with kernel 3.16 and glibc 2.29,
> gcc-9 on real hardware (my SH7785LCR evaluation board). m68k is coming later.
Attaching the testsuite run for libffi 3.3-rc1 on my Amiga 4000/68060 running
Debian unstable with kernel 5.3.0 and glibc 2.29.
Let me know if you need any more information.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
[-- Attachment #2: ffi-m68k.log --]
[-- Type: text/x-log, Size: 4006 bytes --]
MAKE m68k-unknown-linux-gnu : 0 * check
make[1]: Entering directory '/srv/libffi-3.3-rc1/m68k-unknown-linux-gnu'
Making check in include
make[2]: Entering directory '/srv/libffi-3.3-rc1/m68k-unknown-linux-gnu/include'
make[2]: Nothing to be done for 'check'.
make[2]: Leaving directory '/srv/libffi-3.3-rc1/m68k-unknown-linux-gnu/include'
Making check in testsuite
make[2]: Entering directory '/srv/libffi-3.3-rc1/m68k-unknown-linux-gnu/testsuite'
make check-DEJAGNU
make[3]: Entering directory '/srv/libffi-3.3-rc1/m68k-unknown-linux-gnu/testsuite'
Making a new site.exp file ...
srcdir='../../testsuite'; export srcdir; \
EXPECT=expect; export EXPECT; \
if /bin/bash -c "runtest --version" > /dev/null 2>&1; then \
exit_status=0; l='libffi'; for tool in $l; do \
if runtest --tool $tool --srcdir $srcdir ; \
then :; else exit_status=1; fi; \
done; \
else echo "WARNING: could not find 'runtest'" 1>&2; :;\
fi; \
exit $exit_status
Using ../../testsuite/lib/libffi.exp as tool init file.
Test run by root on Fri Nov 1 00:31:40 2019
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 ../../testsuite/config/default.exp as tool-and-target-specific interface file.
Running ../../testsuite/libffi.bhaible/bhaible.exp ...
FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=56 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O2 execution test
FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=56 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O2 -fomit-frame-pointer execution test
FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=57 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O2 execution test
FAIL: libffi.bhaible/test-call.c -W -Wall -Wno-psabi -DDGTEST=57 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O2 -fomit-frame-pointer execution test
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=54 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O0 execution test
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=55 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O0 execution test
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=55 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O2 execution test
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=55 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O2 -fomit-frame-pointer execution test
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=56 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O0 execution test
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=56 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O2 execution test
FAIL: libffi.bhaible/test-callback.c -W -Wall -Wno-psabi -DDGTEST=56 -Wno-unused-variable -Wno-unused-parameter -Wno-unused-but-set-variable -Wno-uninitialized -O2 -fomit-frame-pointer execution test
Running ../../testsuite/libffi.call/call.exp ...
Running ../../testsuite/libffi.complex/complex.exp ...
Running ../../testsuite/libffi.go/go.exp ...
=== libffi Summary ===
# of expected passes 2140
# of unexpected failures 11
# of unsupported tests 30
make[3]: Leaving directory '/srv/libffi-3.3-rc1/m68k-unknown-linux-gnu/testsuite'
make[2]: Leaving directory '/srv/libffi-3.3-rc1/m68k-unknown-linux-gnu/testsuite'
make[1]: Leaving directory '/srv/libffi-3.3-rc1/m68k-unknown-linux-gnu'
next prev parent reply other threads:[~2019-11-01 22:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:17 Anthony Green
2019-10-25 10:08 ` Matthias Klose
2019-10-25 10:29 ` John Paul Adrian Glaubitz
2019-10-25 14:41 ` Andreas Schwab
2019-10-25 14:44 ` John Paul Adrian Glaubitz
2019-10-25 18:32 ` Andreas Schwab
2019-10-25 18:37 ` John Paul Adrian Glaubitz
2019-10-25 19:04 ` Andreas Schwab
2019-10-25 19:07 ` John Paul Adrian Glaubitz
2019-10-26 11:35 ` Anthony Green
2019-10-26 12:54 ` Anthony Green
2019-10-31 19:49 ` Anthony Green
2019-10-31 20:32 ` John Paul Adrian Glaubitz
[not found] ` <CAAs=koj3HU08uxx36809NcPYe33xvEjUDsLwJc_9R8V4tbr9Zg@mail.gmail.com>
2019-10-31 22:16 ` John Paul Adrian Glaubitz
2019-11-01 8:01 ` John Paul Adrian Glaubitz
2019-11-01 22:24 ` John Paul Adrian Glaubitz [this message]
2019-11-08 9:21 ` Matthias Klose
2019-11-08 14:28 ` Anthony Green
2019-11-09 16:04 ` Matthias Klose
2019-11-09 17:46 ` Anthony Green
2019-11-10 16:22 ` Matthias Klose
2019-11-26 8:39 ` Matthias Klose
2019-11-26 23:25 ` Anthony Green
2019-11-27 7:54 ` Matthias Klose
2019-11-27 9:28 ` Anthony Green
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=3a9deaae-443c-b54b-98bb-8b87468bd072@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-68k@lists.debian.org \
--cc=debian-superh@lists.debian.org \
--cc=doko@ubuntu.com \
--cc=green@moxielogic.com \
--cc=green@redhat.com \
--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).