[aarch64-port-dev ] AARCH64: 8064611: Changes to HotSpot shared code

Vladimir Kozlov vladimir.kozlov at oracle.com
Wed Nov 19 03:03:29 UTC 2014


Yes, we can hide AARCH64 using something similar to 
CODE_CACHE_SIZE_LIMIT macro which could be overwritten in platform 
specific files if needed: USE_STORE_RELEASE_FOR_VOLATILE.
Or slightly more complicated declaration similar to 
support_IRIW_for_not_multiple_copy_atomic_cpu boolean constant.

Dean, will it help us if we do that? If yes, then we should do that.

I did not insisted on removing AARCH64 from C2 because there was 
discussion about generating special volatile load/store nodes instead of 
using memory order flag. So we may rewrite this code anyway.

Regards,
Vladimir

On 11/18/14 5:52 PM, Dean Long wrote:
> That would be my preference too, but then we have to touch all the other
> ports.
> I'll let Vladimir have the final vote.
>
> dl
>
> On 11/18/2014 1:38 AM, Roland Westrelin wrote:
>> There’s very little code that’s marked with #ifdef X86 or #ifdef SPARC
>> in the C2 code. Wouldn’t we want to hide everything that is AARCH64
>> specific behind functions in Matcher like we do elsewhere?
>>
>> Roland.
>


More information about the aarch64-port-dev mailing list