New candidate JEP: 454: Foreign Function & Memory API

Rony G. Flatscher Rony.Flatscher at wu.ac.at
Tue Sep 19 09:41:27 UTC 2023


Just for the record: this thread got moved to panama-dev as suggested by Mark. The e-mail thread 
there starts with <https://mail.openjdk.org/pipermail/panama-dev/2023-September/019869.html>.

---rony

On 14.09.2023 12:56, Mark Reinhold wrote:
> 2023/9/13 12:33:07 -0400, rony.flatscher at wu.ac.at:
>> On 11.09.2023 22:21, Mark Reinhold wrote:
>>> https://openjdk.org/jeps/454
>>>
>>>    Summary: Introduce an API by which Java programs can interoperate with
>>>    code and data outside of the Java runtime. By efficiently invoking
>>>    foreign functions (i.e., code outside the JVM), and by safely accessing
>>>    foreign memory (i.e., memory not managed by the JVM), the API enables
>>>    Java programs to call native libraries and process native data without
>>>    the brittleness and danger of JNI.
>> This JEP includes the "|--enable-native-access=M" and "||/.../ |the JAR-file manifest attribute
>> |Enable-Native-Access: ALL-UNNAMED| can be used /in an executable JAR//.../"||
>>
>> Can you explain how to inhibit the warning in JRE (Java/JDK runtime environment) deployment cases
>> where neither a monolithic Java app nor an executable jar causes the JVM to get started up?
>>
>> ...
> Please take this discussion to the panama-dev list.
>
> - Mark



More information about the jdk-dev mailing list