3 ms·
In modern parlance I think the best way to think of the zero page is as a primitive form of 'nearby' memory, we'd do this transparently through a cache. Some pr
by jacquesm 3y ago
In modern parlance I think the best way to think of the zero page is as a primitive form of 'nearby' memory, we'd do this transparently through a cache. Some processors extended this 'register file in RAM' concept considerably, for instance the https://en.wikipedia.org/wiki/TMS9900 https://en.wikipedia.org/wiki/TMS9900 TMS9900 with it's workspace register.
All of these concepts, register file, cache, context memory were quite fluid at the time and not yet settled in the way we see them today so it isn't surprising to see one party refer to the 6502 zero page (or the 6809 direct page) as an extension of the register file in the CPU and another to see it as a cache, a task context or more efficient bit of memory. All of these can be right, it's just a POV difference.
- kjs3 3y agoI don't disagree that there was significant malleability in nomenclature, but the idea that zero-pages or 9900-style workspaces were register equivalents was in the most charitable sense was never anything but marketing, and never by anyone who honestly did the math. Even the 9900 folks pretty quickly stopped trying to convince us they had 'registers' and moved to how quickly they could change contexts and mitigate the speed asymmetries between on and off chip memory.
- cmrdporcupine 3y agoI absolutely agree, I don't think I would contradict that in any way, I just think the above exchange I was replying to was silly on both fronts and dunno why it got heated but wanted to provide more tempered POV on the utility of the zero page as a set of registers. You can frame it that way, and compilers often do, but it's honestly stretching the "truth" a bit. And for that I got downvoted. Huh.