RFR: 8264806: Remove the experimental JIT compiler [v2]
iignatyev at openjdk.java.net
Sat Apr 10 16:50:46 UTC 2021
On Sat, 10 Apr 2021 16:36:54 GMT, Vladimir Kozlov <kvn at openjdk.org> wrote:
>> should we remove `sun.hotspot.code.Compiler::isGraalEnabled` method and update a few of its users accordingly?
>> what about `vm.graal.enabled` `@requires` property?
> @iignatev If you think that I should clean tests anyway I will file follow up RFE to do that.
> > should we remove `sun.hotspot.code.Compiler::isGraalEnabled` method and update a few of its users accordingly?
> > what about `vm.graal.enabled` `@requires` property?
> Thank you, @iignatev for looking on changes.
> I forgot to mention that `Compiler::isGraalEnabled()` returns always false now. Because 94 tests uses `@requires !vm.graal.enabled` I don't want to include them in these changes which are already very big. I am not sure if I should modify tests if GraalVM group wants to run all these tests.
> If you think that I should clean tests anyway I will file follow up RFE to do that.
changing `Compiler::isGraalEnabled()` to always return false effectively makes these tests unrunnable for GraalVM group (unless they are keep the modified `sun/hotspot/code/Compiler` and/or `requires/VMProps` in their forks). on top of that, I foresee that there will be more tests incompatible w/ Graal yet given it won't be run/tested in OpenJDK, these tests won't be marked and hence will fail when run w/ Graal. so Graal people will have to either do marking themselves (I guess in both upstream and their fork) or maintain a list of inapplicable tests in a format that works best for their setup.
that's to say, I think we should clean up the tests, yet I totally agree there is no need to do it as part of this PR. we can discuss how to do it better for both OpenJDK and GraalVM folks in the follow-up RFE.
More information about the hotspot-compiler-dev