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

RFE: switch from eager deoptimization to lazy deoptimization

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 5.0
    • 1.4.2_06, 5.0
    • hotspot
    • tiger
    • generic, x86
    • generic, linux

      Hotspot current eagerly deoptimizes nmethods. This reuires it to carry a lot
      of state around in vframeArrays and more importantly requires it to patch
      return addresses in frames. Patching return addresses in frames is one reason
      why the jni trampoline was needed on register window machines. If we switch
      to lazy deopt then with a small amount of work in the interpreter we can eliminate the jni trampoline (which is added overhead on all jni calls) and
      greatly reduce the complexity of stack walking (no more deoptimized frames)
      and simplify the deopt code by making vframeArray handling much simpler.

            sgoldman Steve Goldman (Inactive)
            sgoldman Steve Goldman (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: