JDK-8325585 : Remove no longer necessary calls to set/unset-in-asgct flag in JDK 17
  • Type: Task
  • Component: hotspot
  • Sub-Component: svc
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: os_x
  • CPU: aarch64
  • Submitted: 2024-02-10
  • Updated: 2025-03-23
  • Resolved: 2024-02-21
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 17
17.0.11 b05Fixed
Related Reports
Relates :  
Description
The backport of  JDK-8304725 to JDK 17 (tracked as JDK-8311636) brought in RAII instance for marking a code as executing on behalf of ASGCT but failed to remove the explicit calls to set/unset the corresponding flag. 

This does not cause functional issues but still brings a bit of inefficiency. The explicit calls should be removed and only the RAII should be used.
Comments
Changeset: 303e8def Author: Johannes Bechberger <jbechberger@openjdk.org> Committer: Goetz Lindenmaier <goetz@openjdk.org> Date: 2024-02-21 11:16:27 +0000 URL: https://git.openjdk.org/jdk17u/commit/303e8deffdfb4ab26c0e7d0ae33863160613edf5
27-02-2024

Changeset: 303e8def Author: Johannes Bechberger <jbechberger@openjdk.org> Committer: Goetz Lindenmaier <goetz@openjdk.org> Date: 2024-02-21 11:16:27 +0000 URL: https://git.openjdk.org/jdk17u-dev/commit/303e8deffdfb4ab26c0e7d0ae33863160613edf5
21-02-2024

[jdk17u-fix-request] Approval Request from Johannes Bechberger Removes two unnecessary calls, that I forgot to remove when backporting. Tested and low risk.
15-02-2024

A pull request was submitted for review. URL: https://git.openjdk.org/jdk17u-dev/pull/2207 Date: 2024-02-13 11:29:33 +0000
13-02-2024