JLang adds an LLVM backend to the Polyglot compiler, translating Java into LLVM IR. See the Getting Started Guide to try it out, and the developer guide for an overview of the codebase (The repo can be found on GitHub).
JLang supports Java 7, as specified by the JLS. Since Polyglot additionally supports Java language extensions, and since it can generally translate these extensions down to vanilla Java, JLang should be interoperable with other Polyglot extensions by default. However, JLang also aims to be extensible, so that one can write direct translations to LLVM for language extensions when needed.
To be more concrete, here’s what Polyglot + JLang will allow you to do:
(1) Translate Java source files (
.java) down to LLVM IR (
.ll), and then from there down to object files (
.o) using the the LLVM toolchain.
(2) Link object files together along with JLang-compiled OpenJDK classes to create a standalone executable. JLang implements a runtime to provide the JVM functionality that the JDK expects, such as reflection and cross-language method calls. Native code in the JDK (e.g., low-level networking and I/O code) can be linked directly from your local JDK installation.
(3) (Optional) Extend Java with custom language features or type annotations using Polyglot, and either translate these features back into vanilla Java, or write a direct translation into LLVM IR by extending JLang.
JLang currently supports all Java 7 language features, except for some reflection support. This includes expressions, control flow, exceptions, method dispatch, switch statements, try-with-resources, initializer blocks, implicit type conversions, etc. OpenJDK 7 support is still a work in progress but enough is supported for many standard use cases (such as printing and accessing files).
All unit tests currently pass with OpenJDK 7, except for a number of advanced reflection features, primarily related to generic types.
See the README in the repository and the Relase Notes for the most up-to-date status.
If you would like to contribute to JLang, you should fork the repo and create a new branch whose name is related to the issue that you would like to address. You can submit a pull-request in order to have your changes mreged.
If you are interested in becoming more involved in JLang as, please follow and communicate via the jlang users list for more information, discussion and updates. To subscribe the mailing list, fill out the subscription form on the Contact Us page.
Current and Past Contributors
- Daniel Donenfeld
- Matthew Gharrity
- Yiteng Guo
- Andrew Myers
- Daniel Weber
- Drew Zagieboylo
- Yizhou Zhang