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

Deoptimization::revoke_for_object_deoptimization: stack processing start call is redundant

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 16
    • Fix Version/s: 16
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b27

      Description

      Calling StackWatermarkSet::start_processing() in
      Deoptimization::revoke_for_object_deoptimization() is redundant. There are
      KeepStackGCProcessedMarks on all paths leading to
      revoke_for_object_deoptimization() as the call hierarchy below shows.

      StackWatermarkSet::start_processing(JavaThread *, enum StackWatermarkKind) : void
      ....Deoptimization::revoke_for_object_deoptimization(JavaThread *, frame, RegisterMap *, JavaThread *) : void
      ........Deoptimization::deoptimize_objects_internal(JavaThread *, GrowableArray<compiledVFrame *> *, bool &) : bool
      ............EscapeBarrier::deoptimize_objects_internal(JavaThread *, intptr_t *) : bool
      ................EscapeBarrier::deoptimize_objects_all_threads() : bool.................... // has KeepStackGCProcessedMark
      ................EscapeBarrier::deoptimize_objects(intptr_t *) : bool
      ....................EscapeBarrier::deoptimize_objects(int, int) : bool.................... // has KeepStackGCProcessedMark

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rrich Richard Reingruber
              Reporter:
              rrich Richard Reingruber
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: