On Mon, Apr 23, 2012 at 10:30 AM, Julius Baxter <[email protected]> wrote: > For OR2K I'd like to see the ISA re-done from scratch. It wouldn't be > just delay slot dropping, it'd be an entirely different instruction > set to address the horrible code density OR1K has. Having baggage in > terms of backward compatibility of ISAs will be counterproductive.
I'm just curious how you intend to address code density. OpenRISC should be similar in that respect to other RISC ISAs like MIPS or SPARC, so I wouldn't say the code density is horrible, per se. The only way I can think of to improve it would be to do something like ARM Thumb, or to stray from the RISC paradigm and add more complex operations. I rather like the fact that the ISA is so simple, since it leads to simple designs and makes it suitable for use in research and so on. I don't think OpenRISC should abandon that use case. -Pete _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
