Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 6281377
Votes 0
Synopsis Provide Unsafe lazy field set methods
Category java:classes_util_concurrent
Reported Against b43
Release Fixed mustang(b53)
State 10-Fix Delivered, request for enhancement
Priority: 3-Medium
Related Bugs 6291823 , 6322334 , 6511866
Submit Date 07-JUN-2005
Description
Doug Lea writes:

"The request is to add three methods, whose primary use
is to support lazySet, but are also needed to
correctly and efficiently handle barrier-less volatile
writes. For example, setting the parkBlocker in support
of Mandy's stuff. (I can add more explanation and
implementation notes if they would be useful for CCC.)



      /**
       * Version of {@link #putObjectVolatile(Object, long, Object)}
       * that does not guarantee immediate visibility of the store to
       * other threads. This method is generally only useful if the
       * underlying field is a Java volatile (or if an array cell, one
       * that is otherwise only accessed using volatile accesses).
       */
      public native void    putOrderedObject(Object o, long offset,
Object x);

      /** Ordered/Lazy version of {@link #putIntVolatile(Object, long,
int)}  */
      public native void    putOrderedInt(Object o, long offset, int x);

      /** Ordered/Lazy version of {@link #putLongVolatile(Object, long,
long)} */
      public native void    putOrderedLong(Object o, long offset, long x);
"

  xxxxx@xxxxx   2005-06-07 07:06:32 GMT
Work Around
N/A
Evaluation
Hotspot implementation being provided by Doug Lea.

  xxxxx@xxxxx   2005-06-07 07:06:32 GMT
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang