Tiered: policy should make consistent decisions about osr levels

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P4
    • hs22
    • Affects Version/s: hs22
    • Component/s: hotspot
    • None
    • b02
    • generic
    • generic
    • Not verified

        After my fix for 7058689 it is possible that the AdvancedThresholdPolicy will make a different decision as to what compilation level for osr is appropriate in loop_event() and call_event() from what happens in method_back_branch_event(). In method_back_branch_event() in case the OSR compilation level is CompLevel_limited_profile we change it to CompLevel_full_profile but we don't do the same in call_event() and loop_event() to determine whether the existing OSR methods are current. The solution would be to move this level fixup from method_back_branch_event() to loop_event() and call_event().

              Assignee:
              Igor Veresov
              Reporter:
              Igor Veresov
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: