-
Enhancement
-
Resolution: Fixed
-
P4
-
24
-
b20
All around Hotspot, we have calls to `method->is_initializer()`. That method tests for both instance and static initializers. In many cases, the uses imply we actually want to test for constructor, not static initializer. Sometimes we filter explicitly for `!m->is_static()`, sometimes we don't. We need to sharpen this, probably remove the confusing `is_initializer` to avoid future accidents.
The behavioral changes are split into related issues.
The behavioral changes are split into related issues.
- is blocked by
-
JDK-8336465 C2: EA incorrectly/unnecessarily checks for clinits
- Resolved
-
JDK-8336466 C2: Parser incorrectly/unnecessarily checks for clinits
- Resolved
-
JDK-8336468 Reflection and MethodHandles should use more precise initializer checks
- Resolved
- links to
-
Commit(master) openjdk/jdk/54c9348c
-
Review(master) openjdk/jdk/20120