[aarch64-port-dev ] Backport patches for 8031818, 8139758 and 8144993

[Felix Yang]

Hi Andrew,

    Actually, I am not quite clear about the correct procedure to do
backport on jdk8u repo. Please let me know if there is anything wrong I am
doing.
    There are not bugfixing patches, but just performance improvement ones.
    So it seems to me that it might be hard or inappropriate for them to go
into jdk8u repo, right?
    As the jdk8u aarch64 port repo can benefit from these patches in
respect of performance, I want this repo to have them.
    I don't want to keep them in my private repo, but this will surely
cause some difference for shared code between jdk8u and jdk8u aarch64 port.

Thanks,
Felix


On 19 June 2017 at 19:16, Andrew Haley <aph at redhat.com> wrote:

> On 19/06/17 11:55, Felix Yang wrote:
>
> >   Please review: http://cr.openjdk.java.net/~fyang/8u-backports/webrev/
> >
> >   This backport three patchs: 8031818, 8139758 and 8144993 to jdk8u
> aarch64
> > port.
> >   I think It's necessary for this repo to have the last two patches.  I
> > backport the first one as the second one depends on it.
> >   We see some performance gain for one of our real world Java
> application.
> >   Tested with JTreg on aarch64 Linux platform, OK to push?
>
> Changes to shared code should usually be submitted to the global jdk8u
> list.  These all seem to be potentially destabilizing changes.  Is
> there any reason you're submitting them as AArch64 patches to this
> list?
>
> --
> Andrew Haley
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
>