Re:JEP 544: Ahead-of-Time Code Compilation
by java-man on Thursday September 10, 2026 @03:00PM
(#49648703)
GCJ was great - I wrote a handset UI entirely in java for a startup in the early 2000's, basically android before android existed, using GCJ. I remember their native interface was somewhat more convenient to use than JNI.
I wish we had GCJ resurrected, now that the java libraries are GPL'd.
Re:JEP 544: Ahead-of-Time Code Compilation
by alex7o on Thursday September 10, 2026 @04:17PM
(#49649624)
Just ask claude to port it to latest gcc :P, pls don't
Re:JEP 544: Ahead-of-Time Code Compilation
by cyberax on Thursday September 10, 2026 @03:30PM
(#49649087)
Yeah! I used it around 2003 to integrate a Java PDF parsing library into our C++ app.
Its biggest downside was the use of Boehm GC that had some issues with large heaps.
Re:JEP 544: Ahead-of-Time Code Compilation
by atgreen on Thursday September 10, 2026 @10:24PM
(#49652847)
I worked on this years ago. Gcj did support loading and interpreting bytecode alongside the AOT-compiled code. libffi's closures were originally implemented to support calling interpreted methods from AOT-compiled code, because a class's vtable could include a mix of AOT-compiled and interpreted methods. You could also compile jar files directly into .so files, which would get loaded and used at runtime if a classloader ever loaded the corresponding jar.
I don't remember if GCJ supported loading and running code dynamically with a built-in JIT or interpreter. I think it was just pure AOT, which caused some compatibility headaches.