2 ms·
How do RISC architecture designers deal with the problem of low code density when modern chip technology makes RAM access considerably slower than anything that
by Koshkin 9y ago
How do RISC architecture designers deal with the problem of low code density when modern chip technology makes RAM access considerably slower than anything that happens inside the CPU? One answer could be to have a huge instruction cache, but I doubt that it is economically possible.
- 0xcde4c3db 9y agoAs far as I know, the two major approaches are 1) Caches 2) Supporting a "compressed" variant of the instruction set (ARM Thumb, MIPS16, RISC-V Compressed). This can be put together by using the same field for target and destination registers, shrinking the set of named registers, making shifts and conditions into explicit instructions instead of fields (for ARM), and similar tweaks.
- deepnotderp 9y agoA number of things. The biggest one is probably compressed instruction sets, which even x86 "CISC" processors use. For example, RISC-V and Thumb use this in their processors and they're a big boon. Also, I think that you've been lied to about the relative code density of RISC vs CISC. CISC is only about ~50% more dense than RISC in the best cases, unless you're talking about polynomial evaluation on VAX or something crazy like that.
- Symmetry 9y agoIf you're willing to be a bit impure like 64-bit ARM is you can get code density about equivalent to what you'd see in x86-64.