[aarch64-port-dev ] AARCH64: Changes to HotSpot shared code
Lindenmaier, Goetz
goetz.lindenmaier at sap.com
Wed Nov 12 13:47:49 UTC 2014
Yes, if you add defined(PPC64) I can handle the rest in the back end.
But I can also add that later on ... basically I wanted to say that it's a good
idea to align the class space that way.
Best regards,
Goetz.
-----Original Message-----
From: Andrew Haley [mailto:aph at redhat.com]
Sent: Mittwoch, 12. November 2014 12:43
To: Lindenmaier, Goetz; hotspot-dev Source Developers; aarch64-port-dev at openjdk.java.net
Subject: Re: AARCH64: Changes to HotSpot shared code
On 11/12/2014 11:40 AM, Lindenmaier, Goetz wrote:
> I think EM_AARCH64 is not defined in my case because the gcc / environment
> is too old to know about AARCH.
Okay, I can #ifdef that.
> metaspace:
> Ok, I think I missed that you can ignore the shift altogether as the compressed class space
> is enforced to be < 0xc0000000. Further, klasses are never 0.
> So on ppc we will still prefer to shift if the heap is < 32g, but 4G alignment helps in the
> other cases as long as the compressed class space is smaller than 4G.
I suppose we're getting close to declaring that this should really be
handled by the back end.
Andrew.
More information about the aarch64-port-dev
mailing list