How to proceed with 8138732

Doug Simon doug.simon at oracle.com
Wed Sep 9 09:06:45 UTC 2020


Hi Philippe,

From the Graal perspective, I don’t believe there’s anything directly impacted by this change. To the extent that Graal cares about HotSpot intrinsics, it simply uses <https://github.com/oracle/graal/blob/d9b4e452cc0ab52c3f1c2abdd08d239553948039/compiler/src/org.graalvm.compiler.hotspot.test/src/org/graalvm/compiler/hotspot/test/CheckGraalIntrinsics.java#L624> the list of intrinsics provided by JVMCI. This list is derived <https://github.com/openjdk/jdk/blob/ec5bd02186668e2cdda6352dd1ae3ed29434d60e/src/hotspot/share/jvmci/jvmciCompilerToVMInit.cpp#L181> from the VM_INTRINSICS_DO macro which is unrelated to @HotSpotIntrinsicCandidate.

-Doug

> On 9 Sep 2020, at 10:34, Philippe Marschall <kustos at gmx.net> wrote:
> 
> Hello
> 
> I started working on 8138732 [2] as described in the issue [1]. However
> the question about the impact and coordination with other projects came
> up, eg.:
> 
> - projects that implement their own intrinsics
> - Graal
> - somebody else?
> 
> How do we want to address this and coordinate with these projects?
> 
> Given all the possible impact do we still want the issue to be
> implemented as described? Or do we want to have it implemented
> differently or not at all?
> 
> [1] https://bugs.openjdk.java.net/browse/JDK-8138732
> [2] https://github.com/openjdk/jdk/pull/45
> 
> Cheers
> Philippe



More information about the graal-dev mailing list