CPU Design: Fetch/Store vs. operating on memory
CPU Design: Fetch/Store vs. operating on memory
What are CPU designs which are not fetch/store but operate directly on RAM?
I only know about the design of the Nintendo Entertainment System (NES), where the CPU does not have registers (AFAIK) and operates directly on RAM, with fast access to low addresses in the RAM.
What CPUs/Systems do you know, which also do not do fetch/store for their operands? Which systems are out there? Why do CPUs like RISC/Arm/AMD64 use fetch/store, what are the tradeoffs? Are there different architectures for CPUs working on operands outside of fetch/store, DMA and stack machines?
You're viewing a single thread.
primarily speed. In order to avoid constantly searching for RAM, the majority of CPUs have a cache adjacent to them. It resembles a priority queue with VIP cache on a separate queue.
Thank you very much for your answer. I totally agree and understand why modern CPUs have registers. But what about low end/cheap (embedded?) hardware, any design/board/CPU w/o registers?
Registers would only add very little amount of transistors to a CPU with huge gains, so even at the low end it isn't worth it.
These days low end is also crazy, you can get full fledged 32-bit microcontrollers for pennies.