I wonder how fast would Java be on the Prizm. Could a game like Nightmare be possible?

This code just keeps growing

Trying to write an interpreter in Assembly really gives you an appreciation for why they're so large.

That's likely, it's a Java interpreter for a calculator

I hope it fits on-calc, lol.

Well, 1.97kb, but close enough

In reality, the area available for program use will probably be on the order of 100 kb. That's what the OS will handle and I don't really want to throw Flash management into the JVM (in addition to the garbage collector, JNI, threading, etc) in order to get more.

Nope, there's nothing like Jazelle.

No, that was a joke. They'll be limited to declaring 100 KB or so of usable memory during runtime. The actual program can be whatever size will fit in memory.

Now are we talking about 100 kb of executable, data, or executable and data. Remember that for the executable we can run that from flash which would give a possible size of several MB's and the heap looks like a promising area to keep data at 128 kB. There's also the system and add-in stack which for the most part are empty and combined are at a size of 1 MB. Also if it is not being used by anything the back buffer is a lot of ram.

Quote from: willrandship on April 17, 2011, 11:34:19 pm

Does the SH3 have anything like Jazzelle in its CPU? That would help a lot.

Not sure of how helpful that is, nobody has made Java on the NSpire yet and it has jazelle. Perhaps it's not Jazelle's problem and the nspire's.

Nice to see this progressing Qwerty.55.

how Jazelle works is that it executes the simple Java bytecode instructions in hardware just like they were any other CPU instruction, and then for the more complex instructions that are not implemented in hardware, Jazelle will pass off the instruction to the JVM to execute. Unfortunately the SH4A does not include Jazelle so we can't use it. I believe the current layout of our JVM for the Prizm is that several instructions are translated to machine code at a time and then that block is executed. That prevents all of the branches that would be done if you executed the instructions one at at  a time.