-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b05
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2196667 | 7 | John Rose | P3 | Closed | Fixed | b104 |
JDK-2197814 | 6u23 | John Rose | P3 | Resolved | Fixed | b01 |
JDK-2199713 | 6u22m | John Rose | P3 | Resolved | Fixed | b01 |
JDK-2197524 | 6u21p | John Rose | P3 | Resolved | Fixed | b03 |
This is fairly straightforward, since (a) the constant pool already contains method handle references, and (b) the invokedynamic index can be treated as an ordered pair of BSM and NameAndType, just as an invokevirtual index is treated as an ordered pair of class and NameAndType.
The Java language support will need a way (presumably based on JSR 308 annotations) to specify the bootstrap methods.
- backported by
-
JDK-2197524 JSR 292 invokedynamic sites need local bootstrap methods
-
- Resolved
-
-
JDK-2197814 JSR 292 invokedynamic sites need local bootstrap methods
-
- Resolved
-
-
JDK-2199713 JSR 292 invokedynamic sites need local bootstrap methods
-
- Resolved
-
-
JDK-2196667 JSR 292 invokedynamic sites need local bootstrap methods
-
- Closed
-
- relates to
-
JDK-6982999 tools must support -target 7 bytecodes
-
- Closed
-
-
JDK-6983708 JSR 292 local bootstrap methods need extra parameters
-
- Closed
-
-
JDK-7001379 bootstrap method data needs to be moved from constant pool to a classfile attribute
-
- Closed
-
-
JDK-7001382 bytecode processing tools need to handle JSR 292 bytecode changes
-
- Closed
-