The FFM API JEP https://openjdk.org/jeps/454 is now implemented in JDK 22.
It can be used in place of existing JNI-based native access in the JDK.
The java.desktop module has a very large investment in JNI, but we can slowly start to adopt FFM where it makes sense.
One such case is the JDK's use of harfbuzz for OpenType layout.
This particular case has the potential to benefit from FFM for better code and better performance, as well as exploring the limits of what FFM can do and inform future improvements and direction.
It can be used in place of existing JNI-based native access in the JDK.
The java.desktop module has a very large investment in JNI, but we can slowly start to adopt FFM where it makes sense.
One such case is the JDK's use of harfbuzz for OpenType layout.
This particular case has the potential to benefit from FFM for better code and better performance, as well as exploring the limits of what FFM can do and inform future improvements and direction.
- relates to
-
JDK-8330746 [Linux/aarch64] java/awt/font/GlyphVector/LayoutCompatTest.java files differ byte offset=9891
-
- Open
-
-
JDK-8331735 UpcallLinker::on_exit races with GC when copying frame anchor
-
- Closed
-