JDK-8256754 : Deoptimization::revoke_for_object_deoptimization: stack processing start call is redundant
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 16
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-11-20
  • Updated: 2020-12-03
  • Resolved: 2020-11-30
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 16
16 b27Fixed
Related Reports
Relates :  
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

Comments
Changeset: e77aed62 Author: Richard Reingruber <rrich@openjdk.org> Date: 2020-11-30 08:37:06 +0000 URL: https://git.openjdk.java.net/jdk/commit/e77aed62
30-11-2020