RFR: 8143730 [JVMCI] infopoint recording is too restrictive
christian.thalinger at oracle.com
Wed Nov 25 18:50:59 UTC 2015
> On Nov 23, 2015, at 1:16 PM, Doug Simon <doug.simon at oracle.com> wrote:
> JVMCI compilers can optionally record extra debug info for compiled code in addition to the debug info required for safepoints, calls and exceptions. This is the kind of extra information recorded for -XX:+DebugNonSafepoints. Currently, CompilationResult only allows one piece of debug info to be recorded per machine code position. This means the compiler has to insert extra no-ops if it does not want to discard any of the extra debug info.
> The proposed change here is to relax the constraint in the VM independent JVMCI code. If the VM only supports one piece of debug info per machine code position, it should have local logic to decide which of multiple debug infos to record when installing code.
I see usages of InfopointReason.LINE_NUMBER in Graal code. What’s the deal here?
Also, there is one test that uses UNUSED:
163: test(r -> r.addInfopoint(new Infopoint(0, null, InfopointReason.UNKNOWN)));
More information about the hotspot-compiler-dev