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

InterpreterRuntime::monitorexit should be a JRT_LEAF function

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 16
    • 16
    • hotspot
    • None
    • b18


      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.

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

              Created:
              Updated:
              Resolved: