[aarch64-port-dev ] 8153107: Unbalanced recursive locking
Andrey Petushkov
andrey.petushkov at gmail.com
Mon Jun 18 14:09:47 UTC 2018
I can, but that would only be check for regression, not the fix itself
> On 18 Jun 2018, at 16:47, Andrew Haley <aph at redhat.com> wrote:
>
> On 06/18/2018 02:43 PM, Andrey Petushkov wrote:
>>
>>> On 18 Jun 2018, at 16:39, Andrew Haley <aph at redhat.com> wrote:
>>>
>>> On 06/18/2018 02:29 PM, Andrey Petushkov wrote:
>>>> The problem is that I’m not aware of any reproducer for any of the platforms part of main openjdk.
>>>> Also Andrew Haley as well as Derek cannot help here I think since they are working with cpu/aarch64 port code, which did not have mentioned problem at all.
>>>> Me myself is dealing with cpu/aarch32 port which is not part of main openjdk and jdk10 version of it is not yet even pushed into project-aarch32 openjdk repos. There is jdk9 version but there is no ready made reproducer there. The jdk10 version (on review now) has 100% reproducer for this problem, the runtime/CreateMirror/ArraysNewInstanceBug.java hotspot jtreg test, however I’m not sure anyone wants to try that out. Maybe Ed Nevill could help as a more or less independent party.
>>>
>>> Where is the problem? We're asking you to test it on AArch32.
>> Please elaborate what meaning you put into “AArch32” term here
>>
>> - The patch under review deals with cpu/arm implementation. I do not have a reproducer for binaries created from this code
>> - I do have a reproducer for the cpu/aarch32 and I’ve tested extremely similar patch numerous times. Does it count as a means of verification of patch under review?
>
> Ah, my mistake. This patch also affects AArch64. So, I take it that
> your problem is that you don't have AArch64 systems to run the test on?
>
> --
> Andrew Haley
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com <https://www.redhat.com/>>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the aarch32-port-dev
mailing list