[foreign-memaccess+abi] RFR: 8308293: A linker should expose the layouts it supports

Per Minborg pminborg at openjdk.org
Thu Jun 15 10:54:28 UTC 2023


On Thu, 15 Jun 2023 10:27:53 GMT, Maurizio Cimadamore <mcimadamore at openjdk.org> wrote:

> This is another stab at https://github.com/openjdk/jdk/pull/14037
> 
> I believe, after some offline discussion, that we have found a more satisfying solution to the problem of JAVA_CHAR being exposed. Jorn suggested that linkers should also provide mappings for JNI types such as `jint`, `jshort` and such (which are aliases for our layout constants anyway). I think that's a great way to bring `JAVA_CHAR` back into the fold.
> 
> For now, I decided not to specify support for JNI canonical layouts (but I could do so, if that's preferred). I think the highest priority is to provide some stable mappings for C builtin types (+ `size_t`) as that's what 99% of developers will be struggling with.
> 
> API-wise, we just expose a map. In the preovious PR there were questions as to whether the map should be split into two methods. In general I see the following options:
> 
> 1. Just expose a map (that's the primitive, other things can derived from it)
> 2. Expose a map, plus a method to get a canonical layout from a type name (that's the `Charset` approach, which has both `availableCharsets` *and* `forName`)
> 3. Expose a method to get canonical layout from name, plus a method that returns the set of supported canonical layout names
> 
> My (not so strong) preference would be for either (1) or (2).

Maybe we could add a test that ensures basic mapping is in place?

src/java.base/share/classes/jdk/internal/foreign/abi/AbstractLinker.java line 280:

> 278:                 .orElseGet(() -> FunctionDescriptor.ofVoid(stripNames(function.argumentLayouts())));
> 279:     }
> 280: 

Would it make sense to add a "hook" that exotic platforms can use to modify the initialization of the Map?

-------------

PR Comment: https://git.openjdk.org/panama-foreign/pull/839#issuecomment-1592812971
PR Review Comment: https://git.openjdk.org/panama-foreign/pull/839#discussion_r1230820336


More information about the panama-dev mailing list