[aarch64-port-dev ] JDK 13 AArch64 issues to backport

Andrew Dinn adinn at redhat.com
Thu Jun 20 07:53:36 UTC 2019


On 19/06/2019 17:50, Aleksey Shipilev wrote:
>> No, don't bother to backport
>>
>>>   8221995: AARCH64: problems with CAS instructions encoding
> 
> This looks like a hard to diagnose bug that might only manifest in complicated compilations. Do we
> really not care about this?

What Andrew said. As for your follow-up question: in the unlikely event
we were to need this to enable an upstream fix and then needed to
backport that fix downstream said backport would break and it would be
obvious that we also needed to pull this one down.

>>>   8218185: aarch64: missing LoadStore barrier in TemplateTable::putfield_or_static
>>>   8219635: aarch64: missing LoadStore barrier in TemplateTable::fast_storefield
>>>   8221220: AArch64: Add StoreStore membar explicitly for Volatile Writes in TemplateTable
> 
> It is a bit awkward that they are backported to 8u, but not to 11u, so maybe just the consistency
> reasons make them good candidates for 11u backports? Do we think these three are not affecting
> correctness at all? They don't seem to be harmful for performance, as they affect the interpreter only.
These do not affect correctness nor performance. They were merely
included to dot is and cross ts. If someone wants to spend time
backporting them I have no concern but it would be a no-op.

regards,


Andrew Dinn
-----------
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander


More information about the aarch64-port-dev mailing list