org.graalvm.compiler.hotspot.meta

Class HotSpotPlatformConfigurationProvider

java.lang.Object

org.graalvm.compiler.hotspot.meta.HotSpotPlatformConfigurationProvider

All Implemented Interfaces:

PlatformConfigurationProvider

public class HotSpotPlatformConfigurationProvider
extends Object
implements PlatformConfigurationProvider

Constructor Summary

Constructors

Constructor and Description
HotSpotPlatformConfigurationProvider(GraalHotSpotVMConfig config, MetaAccessProvider metaAccess)

Method Summary

Modifier and Type	Method and Description
boolean	canVirtualizeLargeByteArrayAccess() Returns whether the underlying VM can recover from virtualizing large primitive unsafe writes in a byte array.
BarrierSet	getBarrierSet() Returns the barrier set that is used to insert the needed read/write barriers.
protected boolean	isWriteToNewObject(FixedAccessNode node) For initializing writes, the last allocation executed by the JVM is guaranteed to be automatically card marked so it's safe to skip the card mark in the emitted code.

Methods inherited from class java.lang.Object

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

Constructor Detail

HotSpotPlatformConfigurationProvider

public HotSpotPlatformConfigurationProvider(GraalHotSpotVMConfig config,
                                            MetaAccessProvider metaAccess)

Method Detail

canVirtualizeLargeByteArrayAccess

public boolean canVirtualizeLargeByteArrayAccess()

Description copied from interface: PlatformConfigurationProvider

Returns whether the underlying VM can recover from virtualizing large primitive unsafe writes in a byte array.

Specified by:

canVirtualizeLargeByteArrayAccess in interface PlatformConfigurationProvider

getBarrierSet

public BarrierSet getBarrierSet()

Description copied from interface: PlatformConfigurationProvider

Returns the barrier set that is used to insert the needed read/write barriers.

Specified by:

getBarrierSet in interface PlatformConfigurationProvider

isWriteToNewObject

protected boolean isWriteToNewObject(FixedAccessNode node)

For initializing writes, the last allocation executed by the JVM is guaranteed to be automatically card marked so it's safe to skip the card mark in the emitted code.