search for: qblfysoceuqj

...y image for the mips program onto a > giant array of bytes? int32 values, actually. The best documentation I have found is the description of mips2java. It seems to be down, so I've included a link via google's cache http://www.xwt.org/mips2java/ http://64.233.167.104/search?q=cache:QblfYsocEuQJ:www.xwt.org/mips2java/ Here is the relevant information: > Architecture Representation > > Conveniently, we can represent main memory as a Java int[][], which > allows efficient accesses so long as they are aligned, > 32-bit-word-at-a-time accesses. The first index is the top 16...

...iant >> array of bytes? > > int32 values, actually. The best documentation I have found is the > description of mips2java. It seems to be down, so I've included a link via > google's cache > > http://www.xwt.org/mips2java/ > http://64.233.167.104/search?q=cache:QblfYsocEuQJ:www.xwt.org/mips2java/ Wow, they are very serious about this. Okay, so I don't know exactly what your (Curt's) goals are, but here's my impression. If you want to do a fully general LLVM->Java translator (not an interpreter) it should basically start as a system similar to MIPS...

On Tue, 1 Mar 2005, Curt Cox wrote: > Mips2Java solves the same problem. The latest version of Mips2Java is called > NestedVM and is part of the larger Vexi project. Much work has been done on > NestedVM and it is quite impressive. > http://wiki.vexi.org/ Interesting, do you know of any documentation that describes how this works? Does it just map the memory image for the mips

Mips2Java solves the same problem. The latest version of Mips2Java is called NestedVM and is part of the larger Vexi project. Much work has been done on NestedVM and it is quite impressive. http://wiki.vexi.org/ Still, it could use a lot of improvement. It's biggest immediate problems are: 1) It doesn't integrate well into a standard (Ant-based) Java build 2) There is no documented