From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Matthias Klose <doko@ubuntu.com>,
Anthony Green <green@moxielogic.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, 25 Oct 2019 18:37:00 -0000 [thread overview]
Message-ID: <5564446c-2fdb-d58d-828c-5d1665a74d8f@physik.fu-berlin.de> (raw)
In-Reply-To: <87sgngfzh4.fsf@igel.home>
On 10/25/19 8:32 PM, Andreas Schwab wrote:
> On Okt 25 2019, John Paul Adrian Glaubitz wrote:
>> It's qemu-user that we are using here, not qemu-system. qemu-user is more finicky
>> when it comes to running testsuites.
>
> There is nothing finicky about this testsuite. It's pure user-space.
Yes, but qemu-user has known bugs which is why I disable testsuites for the time being
and I have elaborated why Aranym or real hardware are not an option at the moment either
I'm always open if someone offers a better solution to our current setup though
but currently that's just how things are. If someone needs tests on real hardware,
I can perform these tomorrow, both on sh4 and m68k.
PS: I think that converting the m68k backend in GCC from CC0 to MODE is a more
pressing problem at the moment.
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
next prev parent reply other threads:[~2019-10-25 18:37 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 [this message]
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
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=5564446c-2fdb-d58d-828c-5d1665a74d8f@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=libffi-discuss@sourceware.org \
--cc=schwab@linux-m68k.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).