jextract error: Crossing storage unit boundaries
maurizio.cimadamore at oracle.com
Mon Feb 22 13:15:44 UTC 2021
I'll take a closer look. We did some changes in this area, to fix
issues associated to bitfields parsing.
The new code now works generally better, but is also stricter in
rejecting headers which break some of the invariants that are relied
upon (unfortunately, the underlying issue here is that libclang is not
100% transparent when it comes to bitfield allocation).
My suspicion here is that there is some "pack" pragma involved, and a
bitfield which crosses one storage boundary into the next, which is not
My feeling is that, in these corner cases, we should try to keep going
with code generation, and issue a warning, rather than completely blow
up code generation.
On Mon, 2021-02-22 at 12:54 +0000, Duncan Gittins wrote:
> I've missed some recent messages so sorry if this repeats anything
> has been reported before or already captured in bug db for ongoing
> I just pulled latest panama-foreign and rebuilt, the jextract no
> works on Windows:
> set "WINKIT=c:\Program Files (x86)\Windows
> jextract -source -lole32 -t duncan.winh -d gen.java --filter
> combaseapi.h -I "%WINKIT%\um" "%WINKIT%\um\shlobj_core.h"
> => fails with message: Crossing storage unit boundaries
> Kind regards
More information about the panama-dev