From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: libffi-discuss@sourceware.org
Cc: compnerd@compnerd.org
Subject: armhf testsuite failures possibly due to 7ad0ae7f42
Date: Mon, 23 Oct 2017 09:53:00 -0000 [thread overview]
Message-ID: <59EDBC0A.80905@foss.arm.com> (raw)
Hi all,
Matthias' testing of libffi [1] (thanks!) shows some recent failures on
armhf relating to closures with short types
(search for "FAIL:")
Considering that the results from May look okay I suspect the culprit is
commit 7ad0ae7f42f3e208431ab66a9032dc9549f978d0 (arm: zext return value
parameters)
from Oct 10.
Would it be possible to take a look and fix the failures?
Thanks,
Kyrill
(Please keep me on CC to any replies as I am not subscribed to this list)
[1]
https://buildd.debian.org/status/fetch.php?pkg=libffi&arch=armhf&ver=3.3~20171020-1&stamp=1508524302&raw=0
[2]
https://buildd.debian.org/status/fetch.php?pkg=libffi&arch=armhf&ver=3.3~20170512-1&stamp=1494644748&raw=0
next reply other threads:[~2017-10-23 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 9:53 Kyrill Tkachov [this message]
2017-10-24 0:35 ` Saleem Abdulrasool
2017-10-25 0:20 ` Saleem Abdulrasool
2017-10-25 8:15 ` Kyrill Tkachov
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=59EDBC0A.80905@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=compnerd@compnerd.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).