On Jun 25, 1:13 am, ndatta wrote:
> Oh, I see. Any particular reason? Is a JIT planned in a future
> release? Thanks.
We do intend to support JIT compilation in a future release.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Go
Oh, I see. Any particular reason? Is a JIT planned in a future
release? Thanks.
On Jun 22, 10:42 pm, fadden wrote:
> On Jun 22, 3:20 am, ndatta wrote:
>
> > Isn't the JITter smart enough to convert (1) to (2) above?
>
> There is no JIT in the current software release.
--~--~-~--~~--
On Jun 23, 7:49 am, LouisB wrote:
> fadden, thanks for taking a looksy into the emulator. Great ideas for
> optimization BTW. I've been looking at your ideas plus this document
> (http://slack.net/~ant/nes-emu/6502.html) and wondering how much mhz I
> can squeeze out of her.
Interesting articl
fadden, thanks for taking a looksy into the emulator. Great ideas for
optimization BTW. I've been looking at your ideas plus this document
(http://slack.net/~ant/nes-emu/6502.html) and wondering how much mhz I
can squeeze out of her.
> How are you determining performance?
Mhz is calculated by c
On Jun 20, 8:00 pm, LouisB wrote:
> Fadden, thanks for taking interest. I've been racking my brain for a
> few weeks now trying to come up with optimizations. Sofar nada. I
> definitely have an Apple][ APK - how can I share?
I nosed around with "dexdump -d" for a bit.
EmAppleII.readMemory()
On Jun 22, 3:20 am, ndatta wrote:
> Isn't the JITter smart enough to convert (1) to (2) above?
There is no JIT in the current software release.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" gr
> For example, this:
>
> byte b0, b1;
> b0 = mMemory.data[0];
> b1 = mMemory.data[1];
>
> is not as fast as:
>
> byte[] data = mMemory.data;
> byte b0, b1;
> b0 = data[0];
> b1 = data[1];
Isn't the JITter smart enough to convert (1) to (2) above?
--~--~-~--~~
Fadden, thanks for taking interest. I've been racking my brain for a
few weeks now trying to come up with optimizations. Sofar nada. I
definitely have an Apple][ APK - how can I share?
p.s. i'm looking in traceview and a function (_eaimm_ - fetches an
immediate from mem[PC] and increments the
On Jun 17, 7:14 pm, LouisB wrote:
> Hello, i'm porting a 6502 Emulator to android. I have it working, but
> only at roughly .3mhz (1 required.) After running the profiler I see
> the simply reading memory (byte[]) is one of the most costly
> operations. Does anyone have any ideas for speeding
9 matches
Mail list logo
