CACAO
|
Hook points are inline functions acting as probes scattered throughout several VM subsystems. More...
Functions | |
void | breakpoint (Breakpoint *bp) |
bool | class_linked (classinfo *c) |
void | class_loaded (classinfo *c) |
void | jit_generated (methodinfo *m, codeinfo *code) |
Hook point just after code was generated. More... | |
void | jit_recycled (methodinfo *m, codeinfo *code) |
void | method_enter (methodinfo *m) |
void | method_exit (methodinfo *m) |
void | method_unwind (methodinfo *m) |
void | native_resolved (methodinfo *m, void *symbol, void **symbolptr) |
void | thread_start (threadobject *t) |
void | thread_end (threadobject *t) |
void | vm_init () |
Hook point after the VM is initialized. More... | |
void | vm_preinit () |
Hook point before the VM is initialized. More... | |
void | vm_shutdown () |
Hook point before the VM is actually destroyed. More... | |
bool | class_linked_dynoffsets (classinfo *c) |
Hook points are inline functions acting as probes scattered throughout several VM subsystems.
They can be used to implement event generation or statistics gathering without polluting the source code. Hence all compiler macro and runtime checks should be done in this file. One example of where hooks are useful is JVMTI event firing.
|
inline |
|
inline |
Hook point just after code was generated.
Note that one method can have multiple code realizations, the hook is fired for each of them. The code was not yet executed.
m | The method for which code was generated. |
code | The fully initialized codeinfo for the generated code. |
void Hook::jit_recycled | ( | methodinfo * | m, |
codeinfo * | code | ||
) |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |