io.rsocket.internal.jctools.util

Class UnsafeAccess

java.lang.Object

io.rsocket.internal.jctools.util.UnsafeAccess

public class UnsafeAccess
extends Object

Why should we resort to using Unsafe?

1. To construct class fields which allow volatile/ordered/plain access: This requirement is covered by AtomicReferenceFieldUpdater and similar but their performance is arguably worse than the DIY approach (depending on JVM version) while Unsafe intrinsification is a far lesser challenge for JIT compilers.
2. To construct flavors of AtomicReferenceArray.
3. Other use cases exist but are not present in this library yet.

Field Summary

Fields

Modifier and Type	Field and Description
static boolean	SUPPORTS_GET_AND_SET
static sun.misc.Unsafe	UNSAFE

Constructor Summary

Constructors

Constructor and Description
UnsafeAccess()

Method Summary

Modifier and Type	Method and Description
static long	fieldOffset(Class clz, String fieldName)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

SUPPORTS_GET_AND_SET

public static final boolean SUPPORTS_GET_AND_SET

UNSAFE

public static final sun.misc.Unsafe UNSAFE

Constructor Detail

UnsafeAccess

public UnsafeAccess()

Method Detail

fieldOffset

public static long fieldOffset(Class clz,
                               String fieldName)
                        throws RuntimeException

Throws:

RuntimeException