3 ms·
RISC itself has nothing to do with the number of instructions. It's about the load-store principle, separating instructions that access memory wrt. those that c
by zozbot234 6y ago
RISC itself has nothing to do with the number of instructions. It's about the load-store principle, separating instructions that access memory wrt. those that compute on registers.
- Someone 6y agoIt’s hard to define RISC, but separating load and stores from computations is a side effect of the desire to have uniform, low instruction execution times in order to simplify pipelining, not a goal of RISC. AES would be non-RISCy because it won’t execute in a single clock cycle, either stopping the pipeline or necessitating complex logic. Having said that, I don’t think RISC-V implementations are 100% RISC in that respect (is any CPU?)