United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6939207 refactor constant pool index processing
JDK-6939207 : refactor constant pool index processing

Details
Type:
Bug
Submit Date:
2010-03-30
Status:
Resolved
Updated Date:
2010-09-24
Project Name:
JDK
Resolved Date:
2010-06-26
Component:
hotspot
OS:
generic
Sub-Component:
compiler
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
hs19 (b03)

Related Reports
Backport:
Backport:
Backport:
Backport:
Relates:
Relates:
Relates:

Sub Tasks

Description
Bug 6939203 (JSR 292 needs method handle constants) requires an extension to the construct pool structure and the ldc bytecode.  In particular, it needs to use the CP cache to manage method references, and therefore the ldc bytecode (when used by the new functionality) need to refer to a CP cache index.

To do this safely, the JVM's bytecode parsing modules must make a more rigorous distinction between types of bytecode indexes.  This change makes clear the difference between (a) a CP index and (b) a CP cache index, and also (1) a network-byte-order index and (2) a native-byte-order index.  With clarified distinctions, enforced mechanically, we can safely make the needed modifications.

For a draft of this change, see:
  http://hg.openjdk.java.net/mlvm/mlvm/hotspot/file/5353e955d315/cpindex-cleanup.patch

                                    

Comments
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/ab102d5d923e
                                     
2010-05-23



Hardware and Software, Engineered to Work Together