JDK-6873116 : Modify reexecute implementation to use pcDesc to record the reexecute bit
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs17
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-08-18
  • Updated: 2010-04-02
  • Resolved: 2009-09-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7 Other
6u21Fixed 7Fixed hs17Fixed
Related Reports
Relates :  
JDK-6889869 - assert(!Interpreter::bytecode_should_reexecute(code),"should not reexecute")
Description
Currently we use DebugInfoWriteStream/DebugInfoReadStream to record the reexecute bit by compress the reexecute bit
into bci. This makes the code look weird :
read_bci_and_reexecute(bool& reexecute);
write_bci_and_reexecute(int bci, bool reexecute);
It also makes the future addition of debuginfo difficult.

We can use pcDesc to record the reexecute bit, and then map it scopeDesc when a scopeDesc object is created.
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/72088be4b386
20-08-2009