Uploaded image for project: 'JikesRVM'
  1. RVM-382

Integration of Jikes RVM and JNODE


    • Type: Task
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1000
    • Component/s: Infrastructure
    • Labels:


      I was lucky enough to meet many of the JNODE developers at FOSDEM '08 and there was a massive shared interest in integrating the Jikes RVM with JNODE. I've tried this a number of times, but we're in the best shape ever to make it happen. There are 2 main problems:

      1) license issues - JNODE is GPLv2 we're CPL
      2) package names

      We currently tackle issue 1 by explicit directory names... It would be good to know if we can do similar for JNODE? I don't see a problem unless we try to mix source from both projects in a single file, which I think we can work around.

      Package names are some what more tricky and we discussed how we should progress things.

      I hope that we can build an integrated JNODE and Jikes RVM runtime structure. I believe such a structure would have packages as follows:

      org.vmmagic - vmmagic unchanged
      org.mmtk - mmtk unchanged
      org.jikesrvm.compilers/adaptive/osr - Jikes RVM compiler system unchanged
      org.jikesrvm.jni - JNI interface that isn't of use to JNODE
      org.vm.scheduler - unified Jikes RVM and JNODE scheduler
      org.vm.runtime - unified runtime support
      org.jnode - JNODE filesystems, device drivers, etc. largely unchanged

      Obviously I've not covered everything with this list, so if people can add to this JIRA I'd appreciate it. Thanks.


          Issue links



              • Assignee:
                ianrogers Ian Rogers
              • Votes:
                0 Vote for this issue
                0 Start watching this issue


                • Created: