-
Enhancement
-
Resolution: Fixed
-
P4
-
hs22, 5.0
-
b08
-
generic, sparc
-
generic, solaris_8
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2223894 | 8 | Bengt Rutisson | P4 | Resolved | Fixed | b36 |
JDK-8018192 | 7u45 | Bengt Rutisson | P4 | Closed | Fixed | b01 |
JDK-8002468 | 7u40 | Bengt Rutisson | P4 | Closed | Fixed | b01 |
I was curious what the allow_dirty flag, which is carefully passed through quite a few layers of verify calls, actually controlled so I walked down the call chain. The only potential uses of the flag appear to be in Klass::oop_verify_old_oop and objArrayKlass::oop_verify_old_oop, both of whose bodies are completely commented out. It might be nice to completely delete this useless flag and method.
- backported by
-
JDK-2223894 oop_verify_old_oop appears to be dead
-
- Resolved
-
-
JDK-8002468 oop_verify_old_oop appears to be dead
-
- Closed
-
-
JDK-8018192 oop_verify_old_oop appears to be dead
-
- Closed
-
- duplicates
-
JDK-7044349 Remove dead code associated with verify_old_oop()
-
- Closed
-