Re: JavaMemoryModel: New approach to defining the Java Memory Model

• Next message: Cliff Click: "JavaMemoryModel: circular reasoning in compilers & memory models..."
• Previous message: Eliot Moss: "RE: JavaMemoryModel: New approach to defining the Java Memory Model"
• In reply to: Sarita Adve: "RE: JavaMemoryModel: New approach to defining the Java Memory Model"
• Next in thread: Cliff Click: "JavaMemoryModel: circular reasoning in compilers & memory models..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

Sarita Adve wrote:
> Can you give an example? If the compiler can reason that it won't
> generate all possible execution traces, then it has to have some
> explicit model of what it can generate that is independent of the model.

Please take care that you don't ask me (the compiler writer) to
define what my current or future memory models will be. What I have
now is surely inaccurate, and what I do in the future will be some
subset of all possibilities and will surely mutate over time.

Cliff

-- 
Dr. Cliff Click      Chief Architect, HotSpot Server  Sun Microsystems, Inc.
Cliff.Click@Sun.COM  Senior Staff Engineer            4150 Network Circle
(408) 276-7046       MS USCA14-102                    Santa Clara, CA 95054
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel

• Next message: Cliff Click: "JavaMemoryModel: circular reasoning in compilers & memory models..."
• Previous message: Eliot Moss: "RE: JavaMemoryModel: New approach to defining the Java Memory Model"
• In reply to: Sarita Adve: "RE: JavaMemoryModel: New approach to defining the Java Memory Model"
• Next in thread: Cliff Click: "JavaMemoryModel: circular reasoning in compilers & memory models..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:41 EDT