[aarch64-port-dev ] [URGENT] RFR (XS): Adjust code stub sizes for Shenandoah and future backports

[Aleksey Shipilev]

On 6/18/19 10:51 PM, Andrew John Hughes wrote:
>> Bumping it up seems rather safe: it wastes a handful of kilobytes in buffers, but it is also tedious
>> to update every time. This is why I bumped it all the way up to current jdk/jdk limits.
> 
> Yeah, I'm not so worried about it being safe, so much as it means all
> our builds from this tree - with or without Shenandoah being used - will
> have a greater memory usage than builds from the upstream tree.

Well, yes, but then again there are +20 KB max there. This is one of the reasons that limit is
usually bumped without much discussion.

> I guess it's ok, but seems like we do need to look at being able to
> configure Shenandoah out at compile-time on 8u, especially if we want to
> push it to upstream 8u at some point.

I don't think _this_ change would be controversial -- in fact, we can bring in incremental
adjustments via 8u backports to make it technically the same.

Going to push it shortly.

-- 
Thanks,
-Aleksey