Bug 545509 - [X] JEP 303: Intrinsics for the LDC and INVOKEDYNAMIC Instructions
Summary: [X] JEP 303: Intrinsics for the LDC and INVOKEDYNAMIC Instructions
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.11   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 544047
  Show dependency tree
 
Reported: 2019-03-18 19:38 EDT by Manoj N Palat CLA
Modified: 2023-07-21 09:08 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Manoj N Palat CLA 2019-03-18 19:38:51 EDT 
Expose intrinsified library support allowing Java developers to write Java source code that reliably translates into INVOKEDYNAMIC invocations, so they can directly access functionality implemented via invokedynamic bootstraps. Expose the ability to lazily initialize create runtime entities expressible as JVM constants (like Class and MethodHandle) without compromising performance. Enhance constant propagation to include descriptor types for relevant constant pool entry types, such as Class, MethodType, and MethodHandle.

Ref: https://bugs.openjdk.java.net/browse/JDK-8178320
Comment 1 Eclipse Genie CLA 2021-07-28 16:58:10 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-07-21 09:08:19 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.