Just a note that it is not just the compiler reorderings that we care about,
we have to worry about hardware reorderings also. Hardware shouldn't be
required to care about "native vs. non-native" code in principle. But I'm
not sure about details of how native code is invoked, so maybe I am missing
the point.
Sarita
> -----Original Message-----
> From: owner-javamemorymodel@cs.umd.edu
> [mailto:owner-javamemorymodel@cs.umd.edu] On Behalf Of Bill Pugh
> Sent: Thursday, April 15, 2004 4:18 PM
> To: javamemorymodel-cs.umd.edu
> Subject: JavaMemoryModel: Do any JVM's move memory accesses
> across native calls?
>
>
> OK, in most JVM's, interaction with the external world
> has to eventually be mediated by native code (perhaps
> native code running in a separate thread that synchronizes
> with Java code, but still native code).
>
> Do any JVM's move memory accesses across native calls?
> Without particular knowledge of what occurs in the native call,
> this would seem to be illegal in general.
>
> Bill
>
> -------------------------------
> JavaMemoryModel mailing list -
> http://www.cs.umd.edu/~pugh/java/memoryModel
>
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:01:04 EDT