RFR: 8348957: [leyden] Excess PrintCompilation printing on compile task start

[Aleksey Shipilev]

On Wed, 29 Jan 2025 11:26:53 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

> This bothers me a bit in current -XX:+PrintCompilation logs. For various reasons, we have the `DirectiveSet` for every method, which initialized `PrintCompilationOption = true` when `-XX:+PrintCompilation` is set, which prints the compile task at the task start. We don't need that printout, we only really care about the printout at the end of the compilation. 
> 
> Before:
> 
> 
> $ grep com.sun.tools.javac.comp.Resolve::notOverriddenIn out
>     105    W0.0                    646      AP 4       com.sun.tools.javac.comp.Resolve::notOverriddenIn (124 bytes)
>     105    W0.0   Q52.2    C0.1    646      AP 4       com.sun.tools.javac.comp.Resolve::notOverriddenIn (124 bytes)
>     252    W0.1                   3745      A  4       com.sun.tools.javac.comp.Resolve::notOverriddenIn (124 bytes)
>     252                            646      AP 4       com.sun.tools.javac.comp.Resolve::notOverriddenIn (124 bytes)   made not entrant
>     252    W0.1    Q0.0    C0.1   3745      A  4       com.sun.tools.javac.comp.Resolve::notOverriddenIn (124 bytes)
> 
> 
> After:
> 
> 
>      88    W0.0   Q31.3    C0.2    696      AP 4       com.sun.tools.javac.comp.Resolve::notOverriddenIn (124 bytes)
>     239                            696      AP 4       com.sun.tools.javac.comp.Resolve::notOverriddenIn (124 bytes)   made not entrant
>     239    W0.1    Q0.0    C0.1   3809      A  4       com.sun.tools.javac.comp.Resolve::notOverriddenIn (124 bytes)
> 
> 
> I'll also look into upstreaming the extended compile task logging, since it is useful to study compilation dynamics outside of Leyden as well.

Thanks! I think this can go in.

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

PR Comment: https://git.openjdk.org/leyden/pull/29#issuecomment-2622642880