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

OSR methods may not be recompiled at proper compilation level after deoptimization

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 9
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Introduced In Version:
      7
    • Resolved In Build:
      b04
    • CPU:
      generic
    • OS:
      generic

      Backports

        Description

        This bug may prevent methods that have been deoptimized from being recompiled at the proper level.

        In remove_osr_nmethod we are trying to find the highest comp level by iterating though all linked osr-nmethods. But the code fails to take into account that the chained OSR-nmethods may belong to any nmethod in that class, not just that nmethod (as is the case for non-OSR nmethods.)

        This bug has been present since the integration of tiered compilation.

        Impact: May cause loss of performance
        Likelihood: Unknown, but probably not uncommon in scenarios with lots of deopts.
        Workaround: Turn of tiered-compilation, but that will probably hurt performance even more.

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                neliasso Nils Eliasson (Inactive)
                Reporter:
                neliasso Nils Eliasson (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: