RFR: 8284849: Add deoptimization to unified logging [v8]

[Vladimir Kozlov]

On Thu, 9 Jun 2022 12:28:28 GMT, Johan Sjölén <duke at openjdk.java.net> wrote:

>> This PR adds a new "deoptimization" tag and a new log message on the info level mimicking JFR's deoptimization event. In the future this tag will be used to add trace level information, hopefully replacing TraceDeoptimization. JFR's event also captures the stacktrace, which this does not (happy to add this if considered important).
>> 
>> An example output looks like this: 
>> 
>> 
>> [1.346s][info][deoptimization] Deoptimization start {
>> [1.346s][info][deoptimization]   compileId = 407
>> [1.346s][info][deoptimization]   compiler = c2
>> [1.346s][info][deoptimization]   method:lineno:bci = java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(I)Z:176:26
>> [1.346s][info][deoptimization]   instruction = ifne
>> [1.346s][info][deoptimization]   reason = unstable_if
>> [1.346s][info][deoptimization]   action = reinterpret
>> [1.346s][info][deoptimization] } Deoptimization end
>
> Johan Sjölén has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Fix printing

I noticed that method name is missing signature (arguments type) which we have in `TraceDeoptimization` output:

UNCOMMON TRAP method=java.util.Properties.getProperty(Ljava/lang/String;)Ljava/lang/String;  bci=10 pc=0x00007fbae0c23a94, relative_pc=0x00000000000000b4, debug_id=0 compiler=c2 compile_id=9 (@0x00007fbae0c23a94) thread=2203929 reason=null_check action=make_not_entrant unloaded_class_index=-1 debug_id=0

Yes, `PrintCompilation` does not have it but it would be nice to have it in this output.

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

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