Maurizio Cimadamore

> From what I have learned, copy operations have high overhead because: > > * they are not hot, so aren't optimized so fast > > * when not optimized,...

> Thanks for your great explanation. Makes a lot of sense. > > Do you know if the `MAP_SHARED` flag is set for mapped memory segments? I guess this means...

> Isn't it an illustration of a more general problem we have with native code where it can mess with FP environment at any time? > > We already have...

@uschindler Just curious - did you get any feedback re. performance? Thanks

This problem seems relatively similar to what happens for versioned library names on e.g. linux distributions - e.g. `libclang.so.2`. In such cases users are stuck between a rock and a...

> (I'm pessimistic) To summarize: I think that allowing version-specific names (even if surrounded by parenthesis) in `System::loadLibrary` would be very odd. After all, `System::loadLibrary` doesn't support versioned names, even...

> Only the Java developer can select the right member. Right, and I think this problem is isomporphic to the problem we have in Linux distros of selecting between libclang.so.1...

> In case of jextract (jdk22 branch), we would then need something like the following if we want AIX to behave like the other platforms? > > ``` > diff...

> The symbols get found and the JVM can really call into the `libclang.a(libclang.so.16)`. Impressive! (That doesn't mean that jextract is working. clang crashes the way we are calling it....

I'd like to uplevel the discussion a bit. This PR started off to tweak the way in which `System::load` worked in AIX. We then discussed a bunch of options, talked...