-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 18
-
b03
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8279504 | 17.0.3 | Robo Duke | P4 | Resolved | Fixed | b01 |
The compiler directive BreakAtExecute now can only instruct C2 to generate the os::breakpoint. It has no effect for C1.
Currently, C1 has its own control option: C1Breakpoint. It will generate MacroAssembler::int3() at all VEPs of nmethods. On the other hand, BreakAtExecute appears in the compiler directives can be method-specific.
C1 is capable of generating a LIR, but it's not in use right now.
void breakpoint() { append(new LIR_Op0(lir_breakpoint)); }
Currently, C1 has its own control option: C1Breakpoint. It will generate MacroAssembler::int3() at all VEPs of nmethods. On the other hand, BreakAtExecute appears in the compiler directives can be method-specific.
C1 is capable of generating a LIR, but it's not in use right now.
void breakpoint() { append(new LIR_Op0(lir_breakpoint)); }
