August 2023 - jextract-dev

RFR: 7903239: ofAddress factory of function pointer type is wrong for struct returns
by Marko 02 Jan '24

02 Jan '24

When generating the lambda inside the `ofAddress` factory, it is missing the `SegmentAllocator` needed when the function returns a struct. This is [implemented for regular functions](https://github.com/openjdk/jextract/blob/0582eaf1b4cdba95f0ee8c2…, but not for function pointers. ------------- Commit messages: - 7903239: ofAddress factory of function pointer type is wrong for struct returns Changes: https://git.openjdk.org/jextract/pull/58/files Webrev: https://webrevs.openjdk.org/?repo=jextract&pr=58&range=00 Issue: https://bugs.openjdk.org/browse/CODETOOLS-7903239 Stats: 47 lines in 3 files changed: 44 ins; 2 del; 1 mod Patch: https://git.openjdk.org/jextract/pull/58.diff Fetch: git fetch https://git.openjdk.org/jextract pull/58/head:pull/58 PR: https://git.openjdk.org/jextract/pull/58

3 11

RFR: Add path independence
by Per Minborg 02 Jan '24

02 Jan '24

This small PR incorporated feedback from the original PR: https://github.com/openjdk/jextract/pull/66 made after it was integrated. ------------- Commit messages: - Add path independence Changes: https://git.openjdk.org/jextract/pull/68/files Webrev: https://webrevs.openjdk.org/?repo=jextract&pr=68&range=00 Stats: 10 lines in 4 files changed: 2 ins; 0 del; 8 mod Patch: https://git.openjdk.org/jextract/pull/68.diff Fetch: git fetch https://git.openjdk.org/jextract pull/68/head:pull/68 PR: https://git.openjdk.org/jextract/pull/68

5 7

RFR: Add Dockerfile, zero-dep reproducible builds
by Gavin Ray 02 Jan '24

02 Jan '24

As title says, adds a Dockerfile that will fetch all necessary deps and build `jextract` for you on Ubuntu 22.10 It would be nice if some official JDK organization could put this on their Dockerhub, so that users could just do: $ docker run --rm -it openjdk/jextract:latest I've pushed it to my personal Dockerhub, so if anyone would like to test it out, you can use the README directions but prepend `gavinray/` before the image name: $ echo "struct Foo { int a; long b; }; int use_foo(struct Foo foo);" >> sample.h $ docker run --rm -it -v ${PWD}:/tmp/jextract \ gavinray/jextract:latest \ -I /tmp/jextract \ --source \ -l libfoo \ --output /tmp/jextract/generated \ --target-package com.example \ ------------- Commit messages: - Add Dockerfile, zero-dep reproducible builds Changes: https://git.openjdk.org/jextract/pull/74/files Webrev: https://webrevs.openjdk.org/?repo=jextract&pr=74&range=00 Stats: 75 lines in 2 files changed: 75 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jextract/pull/74.diff Fetch: git fetch https://git.openjdk.org/jextract pull/74/head:pull/74 PR: https://git.openjdk.org/jextract/pull/74

3 6

RFR: Add third-party sample list to README, populate with java-vulkan.
by Michael Ennen 02 Jan '24

02 Jan '24

I made a more complex example (1000 lines, mostly because setting up a boilerplate Vulkan program is super lengthy) of using jextract on Vulkan and Win32 APIs. I think it may be too lengthy and too much of a maintenance burden to commit to the `/samples` directory, so I thought maybe including a section on third-party samples would be better. If this is not something you want to entertain that's totally understandable, but thought I would put it out there a bigger sample that interfaces with a pretty complex API may be helpful to others. ------------- Commit messages: - Add third-party sample list to README, populate with java-vulkan. Changes: https://git.openjdk.org/jextract/pull/93/files Webrev: https://webrevs.openjdk.org/?repo=jextract&pr=93&range=00 Stats: 3 lines in 1 file changed: 2 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jextract/pull/93.diff Fetch: git fetch https://git.openjdk.org/jextract pull/93/head:pull/93 PR: https://git.openjdk.org/jextract/pull/93

3 3

debug logging
by Rel 29 Oct '23

29 Oct '23

Hi all, Developing with jextract is a bit difficult: - there is not too much debug logging, the "-Dlibclang.debug=true" enables certain logging but mostly for clang and not jextract itself. To find out what jextract is doing and trace it, is very difficult. It could be remidiated with running debug under IDE but it does not work well if you generate bindings for big "C" projects. Using "-Djextract.debug=true" as of today seems only prints more information during the exceptions but does not show what steps were taken before it - Sometime you receive "Failed to parse /tmp/jextract$1721579888733730008.h:" message, when you try to see contents of /tmp/jextract$1721579888733730008.h to understand why it is failed the file is already deleted. - no logging on what properties we pass to clang Please let me know if I all this make sense or I am doing something wrong. As part of my experiments on c++ side I integrated JUL to address these problems: https://github.com/enatai/jextractcpp/commit/531f1d6183a53b0a1da0c18d7411f1… If this seems useful for jextract I can send MR for it. Regards,

3 10

jextract C++ support
by Rel 24 Sep '23

24 Sep '23

Hi, I would like to know how to participate in C++ support for jextract. Watching Project Panama video (https://inside.java/2023/04/18/levelup-panama/) Paul mentioned that C++ is in the plans. Do we have someone working on it already so I can syncup on what is the plan and where I can help? In particular: - will it be part of jextract or may be jextract++? - will it use clang or something else? if clang then which interface https://clang.llvm.org/docs/Tooling.html There are many things to be done for C++ support but if I pick the most basic like symbols, in C++ they are mangled so current jextract linking logic will need to be changed. Do you think modifying NameMangler to store those mangled C++ symbols will be the right approach? Regards,

4 15

RFR: 7903547: libffmpeg sample crashes JVM
by Athijegannathan Sundararajan 31 Aug '23

31 Aug '23

try..finally is moved inside another enclosing try-with-resources for the confined Arena object. Repeated runs of sample many times do not crash anymore. ------------- Commit messages: - 7903547: libffmpeg sample crashes JVM Changes: https://git.openjdk.org/jextract/pull/128/files Webrev: https://webrevs.openjdk.org/?repo=jextract&pr=128&range=00 Issue: https://bugs.openjdk.org/browse/CODETOOLS-7903547 Stats: 241 lines in 1 file changed: 63 ins; 79 del; 99 mod Patch: https://git.openjdk.org/jextract/pull/128.diff Fetch: git fetch https://git.openjdk.org/jextract.git pull/128/head:pull/128 PR: https://git.openjdk.org/jextract/pull/128

2 2

RFR: 7903542: jextract sample compilation scripts can avoid specifying standard include directory in Mac OS
by Athijegannathan Sundararajan 29 Aug '23

29 Aug '23

jextract infers standard include directory automatically. ------------- Commit messages: - 7903542: jextract sample compilation scripts can avoid specifying standard include directory in Mac OS Changes: https://git.openjdk.org/jextract/pull/127/files Webrev: https://webrevs.openjdk.org/?repo=jextract&pr=127&range=00 Issue: https://bugs.openjdk.org/browse/CODETOOLS-7903542 Stats: 31 lines in 29 files changed: 0 ins; 31 del; 0 mod Patch: https://git.openjdk.org/jextract/pull/127.diff Fetch: git fetch https://git.openjdk.org/jextract.git pull/127/head:pull/127 PR: https://git.openjdk.org/jextract/pull/127

2 2