[jdk11u-dev] RFR: 8270306: [TESTBUG] Add smoke test for JVMCI bootstrapping

[Severin Gehwolf]

On Mon, 12 Jul 2021 14:16:17 GMT, Michal Karm Babacek <github.com+691097+Karm at openjdk.org> wrote:

>> Yes, `vm.graal.enabled` would make sense for this test.
>
> @jerboaa 
> With this, the test runs:
> 
>  * @requires vm.jvmci & !vm.graal.enabled
> 
> It is exlcuded with:
> 
>  * @requires vm.jvmci & vm.graal.enabled
> 
> So....not sure what to make of `vm.graal.enabled` then.
> 
> My build:
> 
>  ./configure --with-zlib=bundled --with-libjpeg=bundled --with-libpng=bundled \
>   --with-lcms=bundled --with-giflib=bundled --with-stdc++lib=static \
>   --disable-warnings-as-errors --with-boot-jdk=/home/karm/X/JDKs/openjdk-11 \
>   --enable-unlimited-crypto --with-jvm-features=zgc,shenandoahgc

Sorry this property checks whether or not the Graal JIT is enabled at runtime i.e. via a command line flag when the test run boots up. Since we don't need the graal JIT to run the test (the forked JVM enables the graal JIT), `@requires vm.jvmci` should be sufficient. Sorry again, I confused this with the graal JVM feature being compiled in.

-------------

PR: https://git.openjdk.java.net/jdk11u-dev/pull/122