This is because of the System.setIn, setOut, setErr ugliness. These
fields are static finals. If the JIT decides to optimize access to
System.in, err, and out, then later doing a System.set* will make
the code where the optimization was done do the wrong thing.
See bug 4064670.
We need a JIT API that will let the VM specify that access to
certain final fields cannot be optimized.
anand.palaniswamy@Eng 1998-02-27
fields are static finals. If the JIT decides to optimize access to
System.in, err, and out, then later doing a System.set* will make
the code where the optimization was done do the wrong thing.
See bug 4064670.
We need a JIT API that will let the VM specify that access to
certain final fields cannot be optimized.
anand.palaniswamy@Eng 1998-02-27
- relates to
-
JDK-4238356 System.setOut still does not work with JIT enabled
-
- Closed
-