-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 21, 23, 24
-
b22
Seen this in Leyden profiles, but it is a generic issue. The profiles show Node::grow and VectorSet::grow as hot methods. The methods are small, and since they are implementing doubling-the-array scheme, we often exit early without actually growing.
Outlining the actual growing part from the capacity check would allow inlining the common case.
Outlining the actual growing part from the capacity check would allow inlining the common case.
- duplicates
-
JDK-8350785 C2: resource allocation verification slows C2 down by around 4%
-
- Closed
-
- links to
-
Commit(master) openjdk/jdk/a5ad974b
-
Review(master) openjdk/jdk/21707