Re: JavaMemoryModel: Problem on single processor

• Next message: Bill Pugh: "JavaMemoryModel: Question about _current_ semantics of start"
• Previous message: Bill Pugh: "JavaMemoryModel: Volatile spec complience tests"
• In reply to: Paul Jakubik: "RE: JavaMemoryModel: Problem on single processor"
• Next in thread: Bill Pugh: "JavaMemoryModel: Replication of Problem on single processor?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

From: "Paul Jakubik" <pjakubik@dallas.objectspace.com>
Cc: "jmm" <JavaMemoryModel@cs.umd.edu>
Sent: Thursday, May 25, 2000 3:40 PM
Subject: RE: JavaMemoryModel: Problem on single processor

> Someone else pointed out to me what was really going on.
> ... The JIT assigned the reference to refer to raw memory
> before running the inlined constructor.
>
> While this sounds like buggy behavior, the JMM allows it.

I take it this is an example of a 'prescient store' (as defined in
the JLS)?

  http://java.sun.com/docs/books/jls/html/17.doc.html#45376

--
Joe Bowbeer
-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel

• Next message: Bill Pugh: "JavaMemoryModel: Question about _current_ semantics of start"
• Previous message: Bill Pugh: "JavaMemoryModel: Volatile spec complience tests"
• In reply to: Paul Jakubik: "RE: JavaMemoryModel: Problem on single processor"
• Next in thread: Bill Pugh: "JavaMemoryModel: Replication of Problem on single processor?"
• 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:26 EDT