RFR: 8251462: Remove legacy compilation policy [v4]

[Igor Veresov]

On Fri, 22 Jan 2021 18:04:54 GMT, Vladimir Kozlov <kvn at openjdk.org> wrote:

>> I guess it's a matter of naming convention. What I tried to make the CompilerConfig API about is to check if compilers are present/enabled and in which combination. Of course presence of a compiler implies that we're going to see nmethod produced by it. I'd like to keep the current naming if it's not a huge eyesore for you.
>
> Hmm, may be we don't need these funxctions.
> Seems is_c1_only() will be true only when JVMCI is off. Right? We can also reinforce it to exclude AOT too.
> And AOT and JVMCI are disabled with -Xint.

It's not so easy. You can have AOT or JVMCI enabled with -Xint. JVMCI code installs can be initiated not only as a result of method going through the compiler broker. Remember that you can run Graal in "host" mode, where it is a normal C1/C2 system (or may be just an interpreter); Truffle can work in a mode like that. And you can totally run with AOT and interpreter (without any JIT).

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

PR: https://git.openjdk.java.net/jdk/pull/1985