Re: How to translate a language that runs on JVM?

<jrefactors@hotmail.com> wrote:
>If we want to write a language translator that translates one language
>to another language (Java Source Code or Byte Code) that runs on JVM,
>which of the following approaches is better?
>
>1) Non-Java Source Code -> Language Translator -> Java Source Code
>2) Non-Java Source Code -> Language Translator -> Java Byte Code
>please advise. thanks!!


I would go with (2), in fact I did. It's a C to Java byte code
translation. I did consider C to Java source (1) but worried about
the crypticness of the resulting Java source.


The compatibility issues between Java byte code and other languages
such as C are real and challenging, but it's solvable. The
performance is also a concern, but so far by utilizing the techniques
in register allocation (graph coloring) I've been able to maximize the
use of JVM's local variables which I treat as if they are registers,
instead of having to access the large array of int I created to mimic
memory. This reduces code size somewhat and also makes it faster than
accessing the large array of int everytime a C variable is referenced.


Napi
--
http://www.axiomsol.com
http://www.cs.indiana.edu/hyplan/napi.html

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