Linked by Kroc Camen on Thu 28th Jan 2010 17:29 UTC
Permalink for comment 406586
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2009-10-14
There are three options. Not good options, but options if you want to devote a lot of time.
The flash compiler uses llvm. llvm isn't a compiler, it's a low level virtual machine which can be compiled (or JITed) to a bunch of real architectures (including arm, x86, ppc, alpha, .net, etc). llvm and java vm are both documented (and open source), so in theory a jar file could be converted to llvm and compiled to arm (or another target). Of course it's not that simple since jvm is stack-based and llvm is register based and much lower level than the jvm, but it could happen.
GCC now includes a java compiled which can (optionally) compile to native code. There's also an llvm-gcc fork which compiles to llvm code. How about marrying the two up? Last I checked (which was a few years ago), the gcc jcc used its own backend and I don't think llvm-gcc supports java but if you switched the jcc backend to use the standard backend it might work.
The third option is using get to compile your java to a javascript web app.