REF: 8159888: [JVMCI] the client VM build is broken when INCLUDE_JVMCI is defined
vladimir.kozlov at oracle.com
Wed Jul 6 00:39:03 UTC 2016
On 7/5/16 5:35 PM, Vladimir Kozlov wrote:
> Changes looks good. I will push them.
> On 6/29/16 5:23 AM, Doug Simon wrote:
>> Even though client+JVMCI (i.e., !TIERED && COMPILER1 && INCLUDE_JVMCI)
>> doesn’t appear to be a supported configuration, it should still be
>> buildable and produce a working VM where a JVMCI compiler can be used
>> in hosted mode. This bug addresses that.
>> I was able to build an exploded jdk but building an image failed in a
>> way I cannot understand:
We don't support or build 64-bit Client VM on any platforms.
>> Building these configurations (matching CONF=release):
>> * linux-x86_64-normal-client-release
>> * linux-x86_64-normal-server-release
>> Building target 'images' in configuration
>> Building JVM variant 'client' with features 'all-gcs cds compiler1
>> fprof jni-check jvmci jvmti management nmt services vm-structs'
>> make: ***
>> Error 4
>> make: *** [generate-classlist] Error 1
>> ERROR: Build failed for target 'images' in configuration
>> 'linux-x86_64-normal-client-release' (exit code 2)
>> No indication of failed target found.
>> Hint: Try searching the build log for '] Error'.
>> Hint: If caused by a warning, try configure --disable-warnings-as-errors.
>> make: *** [main] Error 1
>> make: *** [images] Error 2
>> Using the exploded jdk, I tested the changes on Graal. I had to
>> manually edit
>> build/linux-x86_64-normal-client-release/jdk/lib/amd64/jvm.cfg from:
>> -server KNOWN
>> -client IGNORE
>> -client KNOWN
>> -server IGNORE
>> This file appears to be directly copied from
>> jdk/src/java.base/unix/conf/amd64/jvm.cfg. If/when client builds on
>> amd64 are supported, obviously the generation of jvm.cfg will have to
>> be a little more dynamic.
More information about the hotspot-compiler-dev