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

JSR292: Many Callsite relinkages cause target method to always run in interpreter mode

    Details

    • Subcomponent:
    • Resolved In Build:
      b110
    • CPU:
      generic
    • OS:
      generic

      Description

      Setting the target on existing call site causes HotSpot to deoptimize the target method, and recompile it. After a few recompilations, HotSpot will bail out on compiling the method, leaving it running in interpreted mode. Albeit this is a good strategy under frequent relinkings, the recompilation cutoff might be too low for indy callsites, and can penalize legitimate use cases.

        Attachments

          Issue Links

          relates to

          Enhancement - null JDK-8147550 JSR292: Generate slow non-inlined code shape for unstable call sites

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

          Bug - A problem which impairs or prevents the functions of the product. JDK-8173338 C2: continuous CallSite relinkage eventually disables compilation for a method

          • P3 - Major loss of function.
          • Resolved

          Enhancement - null JDK-7087838 JSR 292: add throttling logic for optimistic call site optimizations

          • P3 - Major loss of function.
          • Closed

            Activity

              People

              • Assignee:
                vlivanov Vladimir Ivanov
                Reporter:
                shade Aleksey Shipilev
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: