A simple, independent optimization extracted from JDK-8230199:
Method::result_type() doesn't need to scan the signature of the method, since the result_type is always calculated and stored inside method->constMethod
Method::result_type is used in a number of places, so turning it from something that scans signatures to a trivial accessor turns out to be a small but very solid optimization.
Method::result_type() doesn't need to scan the signature of the method, since the result_type is always calculated and stored inside method->constMethod
Method::result_type is used in a number of places, so turning it from something that scans signatures to a trivial accessor turns out to be a small but very solid optimization.
- relates to
-
JDK-8230199 consolidate signature parsing code in HotSpot sources
-
- Resolved
-