[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Most Difficult Emulator
- Subject: Re: Most Difficult Emulator
- From: "St�phane Guillard" <stephane.guillard@steria.com>
- Date: Tue, 3 Sep 2002 13:45:21 +0200
- Newsgroups: comp.sys.apple2
- Organization: Guest of ProXad - France
- References: <mxzc9.88342$On.4024791@bin3.nnrp.aus1.giganews.com>
- Xref: archiver1.google.com comp.sys.apple2:22588
Hi,
> [...]
> I have decided to use a different method of way that it will NOT
EMULATE
> 6502 into 80x86. First, my project reads ROM and/or disk images. Second,
> they convert 6502 routines into 80x86 routines (It is NOT to emulate each
> 6502 opcode into 80x86 opcode. Routines are NOT 6502 machine language NOR
> 80x86 machine language.) Routines are written according to my design.
> Third, ROM and/or disk images will be executing into NATIVE 80x86. It is
> MUCH faster than emulator/simulator. Can't you imagine that it can
measure
> up to 200MHz on Xeon 550MHz CPU!
> [...]
There is an intermediate approach of this, which is called JIT (ie Just In
Time compilation), that is the emulator compiles to native at run time, and
keeps native compiled code in a cache. No need to store native bin anywhere.
Almost all modern emulators tend to use this approach. For example,
Amithlon, an Amiga emulator running on PC, reaches 100 x the speed of the
fastest Amiga on earth on current configs, which is amazing.
Kind regards,
--
sg.