From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: libffi-discuss@sourceware.org
Cc: 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: Sat, 15 Feb 2020 19:03:00 -0000 [thread overview]
Message-ID: <e5debba1-5c28-9374-f402-450c5e5f369c@physik.fu-berlin.de> (raw)
In-Reply-To: <9b5d9318-5ef1-593d-daab-3428818707b5@physik.fu-berlin.de>
Hi!
On 2/14/20 12:14 PM, John Paul Adrian Glaubitz wrote:
> After libffi was upgraded to 3.3 in Debian, all OpenJDK versions started
> to break on 32-bit PowerPC with the freshly compiled JVM crashing with
> the following backtrace:
The commit that broke OpenJDK Zero on 32-bit PowerPC is:
commit 73dd43afc8a447ba98ea02e9aad4c6898dc77fb0
Author: Samuel Holland <samuel@sholland.org>
Date: Sun Nov 17 07:22:25 2019 -0600
IEEE754 binary128 long double support for PowerPC64 (#526)
* powerpc: Adjust flags to make room for vector types
* powerpc64 ELFv2 IEEE128 long double support
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
prev parent reply other threads:[~2020-02-15 19:03 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
2020-02-15 19:03 ` John Paul Adrian Glaubitz [this message]
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=e5debba1-5c28-9374-f402-450c5e5f369c@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-powerpc@lists.debian.org \
--cc=doko@debian.org \
--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).