--- Quote Start ---
I'm getting a bit frustrated with NIOS and I'd like to consider alternative soft-cores.
--- Quote End ---
--- Quote Start ---
I want something with an area size similar to the /e core, but not at the expense of 6 clocks or more per instruction. This is almost ridiculous for RISC. It is, of course, just a consequence of NIOS being designed around a deep pipeline.
--- Quote End ---
Sounds like a complaint to me.
You are unknowingly complaining about the pipeline.
In order to execute an instruction, you have to
1 - fetch the instruction from memory,
2 - decode the instruction to determine what registers / memory need to be accessed and what operations will be performed on those operands.
3 - Execute the instruction (add, multiply, etc.)
4 - Access the memory (in the case of instructions that load or store from memory)
5 - Write execution or memory stage results back into registers.
So, you can either do all of theses steps sequentially for every instruction or you can pipeline them. By complaining about the execution time of the /e core you are saying that you don't like the fact that all of the above steps have to be performed sequentially. However, you are also saying that you don't like the logic usage of the /s or /f cores which are pipelined and use a cache. A pipeline is required for efficiency (talking about MIPS).
Now in reality, the above steps can be reduced to a 3-stage pipeline by combining stages. This results in an fmax penalty as more combinatorial logic is required in each of the stages.
Your best bet may be the Microblaze which gives you the option of using a 3-stage pipeline. I don't know what the logic usage would be and of course that would be a different forum. And I'm sure the Microblaze forum would have no problem with complaints about the NIOS.