Now Available: "Juice," A Robust Java-to-C Translation System

"Juice" translates Java bytecodes to C. After being compiled, the
generated routines link with juice's run-time system, which includes a
complete garbage collector, threads package, and core Java API.


Juice translates applications (e.g., javac), not applets.
Juice-translated applications typically run 3-5 times faster than
those interpreted by Sun's JDK 1.0.2. Juice's API does not currently
include AWT or dynamic linking, but is otherwise a complete Java
execution environment.


Currently, Juice runs only under Solaris. Ports to other platforms
will be forthcoming, although not soon. (Our freely-available
distribution includes source code for all of Juice---we encourage
outside porting efforts.) Juice (the translator) is written in Java.
The run-time system is in C. Juice uses the freely-available
Boehm-Weiser garbage collector and the native Solaris threads package.


(We have not used any of Sun's source code--in any way--to develop
Juice. Juice source code is free of all of Sun's licensing
restrictions.)


While this is a beta distribution, Juice appears robust. Because of
their significantly improved performance, we run "juiced" versions of
javac (and juice itself) exclusively for development purposes and have
done so for the last two months.


For more information please visit our website,
http://www.cs.arizona.edu/sumatra/juice/


Or, simply fetch our distribution and enjoy running your java applications
many times faster:
ftp://ftp.cs.arizona.edu/sumatra/juice/juice.tar.Z


Juice is part of the larger, on-going "Sumatra" research project at the
Department of Computer Science of The University of Arizona. The Sumatra
project explores the issues surrounding efficient execution of mobile
code. For more information about the Sumatra Project, visit our website,
http://www.cs.arizona.edu/sumatra/


Members of the Sumatra Project:
Todd A. Proebsting (project leader)
John H. Hartman
Gregg Townsend
Patrick Bridges
Tim Newsham
Scott A. Watterson
--

Return to the comp.compilers page.
Search the comp.compilers archives again.