util.concurrent needs two pieces of "unsafe" functionality: atomic operations like compare and set, compare and increment, etc; and field offset discovering needed by AtomicIntegerFieldUpdater, for example. The other parts don't require special handling besides LockSupport with would benefit from som changes in java.lang.Thread.
On 1/24/06, Tim Ellison <[EMAIL PROTECTED]> wrote: > AIUI the Unsafe type is Sun's means of manipulating OS heap memory -- > classlib has a type that does that (currently in NIO module, and called > com.ibm.platform.OSMemory, though I agree with Paulex that it should > move into LUNI). If the functionality of OSMemory is lacking we can, of > course, extend it to support concurrent. > > Regards, > Tim > > Rodrigo Kumpera wrote: > > Can we import the backport of jsr-166 as the starting point for > > implementing this package? It's released as public domain, so there > > should be not license issue IFAIK. > > > > There are only a few things required make it work, like removing > > references to com.sun.Unsafe. > > > > -- > > Tim Ellison ([EMAIL PROTECTED]) > IBM Java technology centre, UK. >
