> In other words if the compiler can verify that an action before an
> invocation to "new", start(), or whatever is completely unaffected by the
> invocation and the invocation can not be affected by the action, then the
> action can be moved after the invocation. Unless the compiler is very clever
> it can not tell this and so will conservatively not move the code.
A further problem: moving any update to non-method-local state around a "new"
expression must also be reconciled with the precise semantics of
OutOfMemoryError.
Tim Harris
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:26 EDT