[aarch64-port-dev ] JDK 7 support in aarch64-port

Andrew Dinn adinn at redhat.com
Sat Jul 20 23:43:24 UTC 2019


Hi Aleksey,

On 19/07/2019 13:07, Aleksey Shipilev wrote:
> Hi,
> 
> I was wondering why these changes are in aarch64-port/jdk8u-shenandoah:
>   https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/c40a7ed7df16
>   https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/623e2e5f003a
> 
> They stick out in the difference against 8u upstream. It even adds another public method in API:
> JVM_SetProtectionDomain. Do we actually use TARGET_JDK_VERSION=7 for building anywhere? If not,
> should we revert this part?
I'm not sure about all the second set of changes but in the first one:

The main change to vm.make primarily exposes the two functions needed by
the simulator and debugger (das1 and bccheck)

The export of SetProtectionDomain is a hangover from when it needed to
be explicitly inserted into the map file when building the jdk8 JVM to
support the jdk7 JDK runtime. This was a cheap way of getting a jdk7
AArch64 build. It should not be needed for our jdk8u builds as we don't
run jdk7 on the jdk8 JVM and don't even build jdk7 any more.

regards,


Andrew Dinn
-----------



More information about the aarch64-port-dev mailing list