From: Matthias Klose <doko@ubuntu.com>
To: Bruno Haible <bruno@clisp.org>, libffi-discuss@sourceware.org
Subject: Re: test results on many platforms
Date: Sun, 22 Oct 2017 08:12:00 -0000 [thread overview]
Message-ID: <98b4d355-2a30-26d7-29a2-831338ea76cf@ubuntu.com> (raw)
In-Reply-To: <2437301.0N14NqkuRT@omega>
On 21.10.2017 20:31, Bruno Haible wrote:
> 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:
[...]
could you repeat these tests with libffi trunk?
could these new tests added to the libffi testsuite itself?
Matthias
next prev parent reply other threads:[~2017-10-22 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 18:31 Bruno Haible
2017-10-22 8:12 ` Matthias Klose [this message]
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=98b4d355-2a30-26d7-29a2-831338ea76cf@ubuntu.com \
--to=doko@ubuntu.com \
--cc=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).