From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Anthony Green <green@moxielogic.com>
Cc: libffi-discuss <libffi-discuss@sourceware.org>,
Andreas Schwab <schwab@linux-m68k.org>,
James Clarke <jrtc27@debian.org>,
Matthias Klose <doko@debian.org>,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>
Subject: Re: [BUG]: libffi 3.3 breaks OpenJDK Zero on 32-bit PowerPC
Date: Fri, 14 Feb 2020 11:52:00 -0000 [thread overview]
Message-ID: <1675401f-745f-4f44-0d28-f81374fa808f@physik.fu-berlin.de> (raw)
In-Reply-To: <CACxje59jXF0VrE+roqxGHAahvJKCsEdEtw0CfGVRRPeC4Hbs3g@mail.gmail.com>
Hi Anthony!
On 2/14/20 12:46 PM, Anthony Green wrote:
> Thanks for pointing this out. I only figured out how to do CI testing for
> 32-bit PowerPC after the 3.3 release, and there are indeed a number of
> failures:
>
> https://github.com/libffi/rlgl-policy/blob/master/XFAIL#L202-L290
>
> travis-ci testing is done with a powerpc-eabisim GNU toolchain. We need to
> start going through these failures assuming that powerpc-eabisim is a close
> approximation of the system you are using.
This has been tested on Debian unstable (powerpc) with a current gcc-9
snapshot. I can try to track down the libffi commit that introduced the
regression.
Let me try.
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:[~2020-02-14 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 11:14 John Paul Adrian Glaubitz
2020-02-14 11:46 ` Anthony Green
2020-02-14 11:52 ` John Paul Adrian Glaubitz [this message]
2020-02-15 19:03 ` John Paul Adrian Glaubitz
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=1675401f-745f-4f44-0d28-f81374fa808f@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-powerpc@lists.debian.org \
--cc=doko@debian.org \
--cc=green@moxielogic.com \
--cc=jrtc27@debian.org \
--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).