CompuServe Messages

A generic 6502 only accesses 64K & has a 256 byte stack (although my C128 has two of 16 MMU controlled banks of 64K and a 512K ram expansion with DMA that allows transfering 1 byte per cycle). Additionally, memory locations 00-FF are called zero page & can be addressed in lots of interesting ways that make for speedier & more efficient programs. I believe if one were to attempt to create a 68K->6502 "translater" one wouldn't attempt to simulate a 68000, but rather convert the code to take advantage of the 6502's strengths. For instance, the data and address register are easily simulated by using zero page as pseudo-registers, we end up with 128 of them. Calculating the addresses of operands might not take as much code as you believe, but since most 6502 systems don't multitask & usually load programs at a fixed address, calculating addresses is not difficult at all, and good programmers aren't scared by your example. Yes they have to be done by hand, but won't take days… or even seconds. The 6502 has a small instruction set (sort of an unintentional RISC processor, eh?) and doesn't have a built in division or multiplication, but 6502 are used to inventing ways around its limitations. I submit, that given the same clock speeds and comparable addressing space, that the 6502 can do anything a 68000 can do. Not as quickly nor efficiently, but it will reach the finish line. Remember, the 6502 is the 68000's father (or is it step-father? Uncle? Grandfather?) You should respect your [procesor's] elders… :^) I could go on and on, but this isn't the place for it. Now if you want to talk about some nightmarish processors, let's look at some Intel chips…. 😉