4 ms·
It’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 or
by Someone 6y ago
It’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?)