Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8136893

Improve early java.lang.invoke infrastructure initialization

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 8, 9
    • Fix Version/s: 9
    • Component/s: core-libs
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b88
    • CPU:
      generic
    • OS:
      generic

      Backports

        Description

        When using features that initialize java.lang.invoke infrastructure (such as lambdas) early in the JVM boot-up sequence, initialization issues show-up. Two of them have already been identified:

        http://mail.openjdk.java.net/pipermail/mlvm-dev/2015-March/006386.html

        and:

        http://mail.openjdk.java.net/pipermail/mlvm-dev/2015-March/006387.html

        This issue tracks solving both of them.

          Attachments

            Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8142158 Improve early java.lang.invoke infrastructure initialization

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved
            duplicates

            Bug - A problem which impairs or prevents the functions of the product. JDK-8076596 BytecodeDescriptor.parseMethod doesn't work during bootstrapping

            • P3 - Major loss of function.
            • Closed

              Activity

                People

                Assignee:
                plevart Peter Levart
                Reporter:
                plevart Peter Levart
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: