[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] # Improve Java on Hurd (GSoC 2011) ## Description The project consists in improving Java support on Hurd. This includes porting OpenJDK, creating low-level Java bindings for Mach and Hurd, as well as creating Java libraries to help with translator development. For details, see my original [[proposal]]. ## Current status ### Apt repository Modified Debian packages are available in this repository: deb http://jk.fr.eu.org/debian experimental/ deb-src http://jk.fr.eu.org/debian experimental/ ### Glibc signal code improvements 2011-06-29: Patches were submitted to `libc-alpha` which implement global signal dispositions and `SA_SIGINFO`. My latest code is available on [github](http://github.com/jeremie-koenig/glibc/commits/master-beware-rebase), and modified Debian packages are available in my apt repository. One question is how the new symbols introduced by my patches should be handled. Weak symbols turned out to be impractical, so I'm currently considering using a Debian-specific symbol version in the interim period (`GLIBC_2.13_DEBIAN_8` so far). The ultimate symbol version to be used will depend on the time at which the patches get integrated upstream (most likely `GLIBC_2.15`), at which point we will alias the interim version to the new one in debian packages. I have modified libc0.3 to include a `deb-symbols(5)` file (alternatively see ) so that we get an accurate libc dependency in `hurd` and other packages when the symbols in question are pulled in. [[hurd/libthreads]] (cthreads library) will not be changed. There's no reason why its behavior should change, whereas for [[libpthread]] it's needed for conformance. Patches posted on 2011-05-25, but there's a more recent one in the modified hurd package (adds `_hurd_sigstate_delete` and removes the weak symbols). Another issue which came up with OpenJDK is the expansion by the dynamic linker of `$ORIGIN` in the `RPATH` header, see below. #### Plans The patches are pending review and inclusion upstream. As soon as we reach an agreement wrt. the new interfaces (in particular wrt. the value of `SA_SIGINFO`), the patches will be applied to the Debian libc packages for broader testing. ##### Open Items * Test patches: in progress, [[jkoenig]], Svante. More volunteers welcome, of course. > Current status: there's an issue with gdb, > namely signals lose their "untracedness" when they go > through the global sigstate's pending mask, > so gdb spins intercepting a signal and trying to deliver it. > My current > [patch](http://github.com/jeremie-koenig/glibc/commit/3ecb990e9d08d5f75adc40b738b35a1802cc0943) > makes the system unstable. > --[[jkoenig]] 2011-06-22 >> Correction: the patch is fine, problem solved. >> --[[jkoenig]] 2011-06-29 * If [[jkoenig]] thinks it's mature enough: should ask [[Samuel|samuelthibault]] to test these patches on the buildds. > There's a risk that a dependency on my patched libc > might be pulled in while building packages > (in particular hurd) > --[[jkoenig]] 2011-06-22 * Get patches reviewed (Roland?), and integrated into official sources: [!] [[tschwinge]]. > In progress. --[[jkoenig]] 2011-06-29 * Documentations bits (from [[proposal]] and elsewhere) should probably be moved either into the appropriate glibc or Hurd documentation files/reference manuals, or to [[glibc/signal]]. * `SA_SIGINFO` patche is based on [[Samuel|samuelthibault]]'s earlier work. Thus, have him review the new patch? * Perhaps have a look at `SA_NOCLDWAIT`. * Which numeric values to use for `SA_SIGINFO` (and `SA_NOCLDWAIT`)? > Staying in sync with BSD seems the most logical approach, > so I have defined it to 0x40. --[[jkoenig]] 2011-06-29 ### Port OpenJDK As suggested by [[tschwinge]], I have targeted OpenJDK 7 at first. I don't expect it will be too hard to backport my patches to OpenJDK 6. I have succeeded in building a working JIT-less ("zero") version, although the dynamic linker issue must be worked around. Porting Hotspot (the original just-in-time compiler of OpenJDK) should not be too hard. If that fails we can fall back on Shark (a portable alternative JIT which uses LLVM). Complexity of porting HotSpot: probably low. The complex things should be arch- rather than OS-specific. Not many Linux-specific interfaces used. Garbage collection/memory management, etc. and/or most of other Linux-specific interfaces are already dealt with for the zero build. The dynamic linker issue is as follows. An executable-specific search path can be provided in the ELF RPATH header. RPATH directories can include the special string `$ORIGIN`, which is to be expanded to the directory the executable was loaded from. OpenJDK's `java` command uses this feature to locate the right `libjli.so` at runtime. However, on Hurd this information is not available to the dynamic linker and as a consequence RPATH components which include `$ORIGIN` are silently discarded. This can be worked around by defining the `LD_ORIGIN_PATH` environment variable. (which have I used to build and test OpenJDK so far.) #### Plans I intend to fix the RPATH issue by building on [[pochu]]'s `file_exec_file_name()` [patches](http://lists.gnu.org/archive/html/bug-hurd/2010-08/msg00023.html). I have succeeded in building a Hotspot-enabled `libjvm.so`, although the current toolchain issues ([[toolchain/ELFOSABI_HURD]]) have so far prevented me from testing it. > It turns out the build fails later on in `hotspot/agent` > because Hurd lack a `libthread_db.so`. > Also, a Shark version builds, but the result does not work so far. > > In other news, Damien Raude-Morvan is > [working on a kFreeBSD version](http://lists.debian.org/debian-java/2011/06/msg00124.html), > so I intend to merge my current patches with his. > > --[[jkoenig]] 2011-06-29 ##### Open Items * [!] [[tschwinge]] to have a look at [[pochu]]'s `file_exec_file_name()` patches, whether it's generally the right idea. * Assuming it is, continue with getting `$ORIGIN` working. * [!] [[Samuel|samuelthibault]]/[[tschwinge]]/[[jkoenig]]: [[toolchain/ELFOSABI_HURD]]. * They seem to have a rather heavy-weight process for such projects: confer , for example. Do we need this, too? > Probably not. > My current approach (and Damien's wrt. the kFreeBSD patches) > is to add preprocessor directives in the Linux code > to make it more portable. > --[[jkoenig]] 2011-06-29 * Eclipse OK for testing -- but I'd very much hope that it *just works* as soon as we provide the required Java platform. But it may perhaps have some Linux-specifics (needlessly?) in its basement. Is it available for Debian GNU/kFreeBSD already? ### Java bindings for Mach #### Plans (just started.) ##### Open Items * [[tschwinge]] has to read about RMI and CORBA. * MIG * Hacking [[microkernel/mach/MIG]] shouldn't be too difficult. * (Unless you want to make MIG's own code (that is, not the generated code, but MIG itself) look a bit more nice, too.) ;-) * There are also alternatives to MIG. If there is interest, the following could be considered: * FLICK ([[!GNU_Savannah_task 5723]]). [[tschwinge]] has no idea yet if there would be any benefits over MIG, like better modularity (for the backends)? If we feel like it, we could spend a little bit of time on this. * For [[microkernel/Viengoos]], Neal has written a RPC stub generator entirely in C Preprocessor macros. While this is obviously not directly applicable, perhaps we can get some ideas from it. * Anything else that would be worth having a look at? (What are other microkernels using?) * `mach_msg` * Seems like the right approach to [[tschwinge]], but he hasn't digested all the pecularities yet. Will definitely need more time. ## Postponed Might get back to these as time/interest permits. ### GCJ * [[tschwinge]] has the feeling that Java in GCC (that is, GCJ) is mostly dead? (True?) * Thus perhaps not too much effort should be spent with it. If the POSIX threads signal semantics makes it going, then great, otherwise we should get a feeling what else is missing. ### Joe-E.