Integrated: 8336258: Document the behavior of 'exclude' and 'compileonly' with respect to inlining

Volker Simonis simonis at openjdk.org
Fri Jul 19 11:29:36 UTC 2024


On Thu, 11 Jul 2024 16:40:46 GMT, Volker Simonis <simonis at openjdk.org> wrote:

> The long-standing behavior of the `exclude` CompileCommand is to also apply to inlined versions of a method. On the other hand, the `compileonly` CompileCommand only affects top-level compilations of a method and not its inlining behavior.
> 
> The rational behind this decision is that `exclude` is intended to be used in production to workaround compiler crashes or bad compilations for certain methods and in these scenarios it usually doesn't matter if a "bad" method is getting compiled on the top level or if it gets inlined into another compilation unit.
> 
> The "inconsistent inlining behavior with CompileOnly" thread on hotspot-compiler-dev discusses this behavior (see [1]). The answer [2] specifically describes this long-standing behavior.
> 
> I think it would be good to document this behavior in the output of `-XX:CompileCommand=help`
> 
> [1] https://mail.openjdk.org/pipermail/hotspot-compiler-dev/2016-June/thread.html#23575
> [2] https://mail.openjdk.org/pipermail/hotspot-compiler-dev/2016-June/023583.html

This pull request has now been integrated.

Changeset: 84bc4767
Author:    Volker Simonis <simonis at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/84bc4767a4cd68fb52a36c6644bbec67c24b0e1d
Stats:     4 lines in 1 file changed: 4 ins; 0 del; 0 mod

8336258: Document the behavior of 'exclude' and 'compileonly' with respect to inlining

Reviewed-by: thartmann, jkarthikeyan

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

PR: https://git.openjdk.org/jdk/pull/20142


More information about the hotspot-compiler-dev mailing list