RFR: 8146788: remove jvmci.jar from mx suite
doug.simon at oracle.com
Wed Jan 13 23:24:55 UTC 2016
Fair enough. This was mainly removed because it’s not used by Graal any more. But you’re right, it’s still useful when hacking on JVMCI itself from within Eclipse.
How to I withdraw this JBS issue? Close it with “Won’t fix”?
> On 14 Jan 2016, at 00:09, Christian Thalinger <christian.thalinger at oracle.com> wrote:
> I’m not sure about this. One reason to have the monolithic jvmci.jar is to not have to build the JVMCI on command line when you make a change in your IDE:
> cthaling at macbook:~/ws/jdk9/hs-comp/hotspot$ mx -v vm -version
> /Users/cthaling/ws/jdk9/hs-comp/build/macosx-x86_64-normal-server-release/jdk/bin/java -server -XX:+UnlockExperimentalVMOptions -XX:+EnableJVMCI -d64 -Xbootclasspath/p:/Users/cthaling/ws/jdk9/hs-comp/build/mx/hotspot/dists/jvmci.jar -version
> java version "9-internal"
> Java(TM) SE Runtime Environment (build 9-internal+0-2016-01-11-180948.cthaling.hs-comp)
> Java HotSpot(TM) 64-Bit Server VM (build 9-internal+0-2016-01-11-180948.cthaling.hs-comp, mixed mode)
>> On Jan 11, 2016, at 4:05 AM, Doug Simon <doug.simon at oracle.com> wrote:
>> Please this small change to remove generation of a jvmci.jar by the mx JVMCI build system.
More information about the hotspot-compiler-dev