Background

Since async-profiler samples JIT compiler threads as well as Java threads, it can show CPU percentage spent on JIT compilation. At the same time, Java methods are different: some take more resources to compile, other take less. Furthermore, there are cases when a bug in C2 compiler causes a JIT thread to stuck in an infinite loop consuming 100% CPU. It will be helpful to highlight which particular Java methods take most CPU time to compile.

Proposal

Supplement C1/C2 stack traces with a virtual frame showing the current compilation task, i.e. Java method being compiled.

The feature is disabled by default and can be turned on with a command line option.