Details
-
Bug
-
Resolution: Fixed
-
P4
-
11.0.10-oracle
-
None
Description
[Renamed from "ForkJoinPool initialization interferes with other static initialization", because the related changes can't be disentangled.]
This CR mainly provides updates enabling planned loom and related jdk enhancements. The main goal is to streamline initialization by removing other JDK dependencies including VarHandles, and access control (currently only when deprecated SecurityManagers are not used; eventually further removable). It also includes performance improvements for async usages, as well as a few new methods (ForkJoinPool.lazySubmit and setParallelism) needed by other jdk enhancements. Also, to simplify upcoming integrations, it includes java.util.concurrent API updates in Future and ExecutorService that are introduced by loom, but do not directly involve VirtualThreads, and are independently useful.
This CR mainly provides updates enabling planned loom and related jdk enhancements. The main goal is to streamline initialization by removing other JDK dependencies including VarHandles, and access control (currently only when deprecated SecurityManagers are not used; eventually further removable). It also includes performance improvements for async usages, as well as a few new methods (ForkJoinPool.lazySubmit and setParallelism) needed by other jdk enhancements. Also, to simplify upcoming integrations, it includes java.util.concurrent API updates in Future and ExecutorService that are introduced by loom, but do not directly involve VirtualThreads, and are independently useful.
Attachments
Issue Links
- csr for
-
JDK-8285450 jsr166 refresh for jdk19
-
- Closed
-
- duplicates
-
JDK-8257781 Add ForkJoinTask.adaptInterruptible
-
- Closed
-
- relates to
-
JDK-8295962 Reference to State in Task.java is ambiguous when building with JDK 19
-
- Resolved
-
-
JDK-8301216 ForkJoinPool invokeAll() ignores timeout
-
- Resolved
-
-
JDK-8317960 [17u] Excessive CPU usage on AbstractQueuedSynchronized.isEnqueued
-
- Resolved
-
(3 links to)