This has been fixed now and Java works fine again on qemu-sh4 on git
master:
(sid-sh4-sbuild)root@nofan:/# java --version
openjdk 10 2018-03-20
OpenJDK Runtime Environment (build 10+46-Debian-5)
OpenJDK Zero VM (build 10+46-Debian-5, interpreted mode)
(sid-sh4-sbuild)root@nofan:/#
** Changed in:
John Paul Adrian Glaubitz writes:
> On 12/04/2017 10:29 AM, Alex Bennée wrote:
>> It's hard to imagine a scenario where taking the tb_lock() for resolving
>> something that will fail is going to be an improvement. However maybe
>> there is a subtle difference with sh4's javavm implementation.
>
On 12/04/2017 10:29 AM, Alex Bennée wrote:
> It's hard to imagine a scenario where taking the tb_lock() for resolving
> something that will fail is going to be an improvement. However maybe
> there is a subtle difference with sh4's javavm implementation.
So, OpenJDK doesn't have a SH-specific impl
Thomas Huth writes:
> On 01.12.2017 00:25, John Paul Adrian Glaubitz wrote:
>> The offending commit is:
>>
>> d25f2a72272b9ffe0d06710d6217d1169bc2cc7d is the first bad commit
>> commit d25f2a72272b9ffe0d06710d6217d1169bc2cc7d
>> Author: Alex Bennée
>> Date: Mon Nov 13 13:55:27 2017 +
>>
On 01.12.2017 00:25, John Paul Adrian Glaubitz wrote:
> The offending commit is:
>
> d25f2a72272b9ffe0d06710d6217d1169bc2cc7d is the first bad commit
> commit d25f2a72272b9ffe0d06710d6217d1169bc2cc7d
> Author: Alex Bennée
> Date: Mon Nov 13 13:55:27 2017 +
>
> accel/tcg/translate-all:
The offending commit is:
d25f2a72272b9ffe0d06710d6217d1169bc2cc7d is the first bad commit
commit d25f2a72272b9ffe0d06710d6217d1169bc2cc7d
Author: Alex Bennée
Date: Mon Nov 13 13:55:27 2017 +
accel/tcg/translate-all: expand cpu_restore_state addr check
We are still seeing signals d
On 11/30/2017 01:19 PM, Peter Maydell wrote:
> This sounds like it may be the bug fixed by this patchset:
> https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg05067.html
Unfortunately not. I will upload a prepared chroot for testing later
and link it in this bug report.
Adrian
--
.''`.
This sounds like it may be the bug fixed by this patchset:
https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg05067.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1735384
Title:
OpenJDK J