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

InterpreterRuntime::monitorexit should be a JRT_LEAF function

    XMLWordPrintable

Details

    • Enhancement
    • Status: Resolved
    • P4
    • Resolution: Fixed
    • 16
    • 16
    • hotspot
    • None
    • b18

    Description


      That the monitor has already been unlocked, or is a null stacklock monitor has been already checked in the caller, so the code that makes it a JRT_ENTRY_NO_ASYNC is unnecessary.

      Making it a JRT_LEAF like the compiled method entries makes it safer. We know it can never safepoint and unintentionally install a async exception.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8253901 ARM32: SIGSEGV during monitorexit due to incorrect register use (after JDK-8253540)

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8074292 nsk/jdb/kill/kill001: generateOopMap.cpp assert(bb->is_reachable()) failed

          • P3 - Major loss of function.
          • Closed
          links to

          Commit Commit openjdk/jdk/77a0f399

          Review Review openjdk/jdk/320

          Activity

            People

              coleenp Coleen Phillimore
              coleenp Coleen Phillimore
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: