<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><span>Hello</span><span><br></span><span>I’ve found a need to change the granularity of JVMTI’s DynamicCodeGenerated for interpreter’s generated code.</span><div></div><div><span><br></span></div><div><span>Currently it shows just one big interpreter area, probably because of this code:</span></div><div><span><br></span></div><div><span style="color: rgb(63, 67, 80); font-family: "Open Sans", sans-serif; font-size: 13.5px; font-variant-ligatures: normal; orphans: 2; white-space: pre-wrap; widows: 2; background-color: rgba(63, 67, 80, 0.04); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"> JvmtiExport::post_dynamic_code_generated("Interpreter",
AbstractInterpreter::code()->code_start(),
AbstractInterpreter::code()->code_end());</span></div><div><span><br></span><span></span></div><span>However for template interpreter it’s possible to generate such entry for every bytecode instruction code generated ( e.g. one for sipush, etc). Just like -XX:+PrintInterpreter does.</span><div><span><br></span></div><div><span>What would be the ideal place to insert detailed </span><span>JvmtiExport::post_dynamic_code_generated() calls then ?</span><div></div></div><div><span><br></span></div><div><span>Thanks in advance, Vladimir</span></div></body></html>