JDK-6592631 : instanceof should not cause class loading in the interpreter
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2007-08-14
  • Updated: 2011-01-26
  • Resolved: 2007-08-20
Related Reports
Relates :  
JDK-6607320 - Listeners/policies may cause loading of unneeded classes
Relates :  
JDK-6607310 - InputContext may cause loading of swing classes even for non-Swing applets
Relates :  
JDK-4354492 - instanceof should not cause class loading
Description
The fix for 4354492 appears to have been lost long ago due to an apparent mismerge.  The fix should be restored for the interpreter as it reduces classloading during startup.
Comments
EVALUATION Prohibited by JVM spec, and may affect compatibility. See comments for more detail.
20-08-2007
EVALUATION From 4354492 evaluation: If obj's class was loaded by the boot classloader, then if class (or interface) Foo has not been loaded by the boot classloader, return FALSE **without** loading Foo. Array classes are not considered for optimization. In the SwingSet2 demo, all occurances of arrays refered to java/lang/Object (already loaded).
14-08-2007