Re: To RISC or not to RISC

Herbert Kleebauer wrote:


*snip*

IMHO there isn't much point in trying to impose a "generic" naming scheme
for the x86. Why?

There's only a few registers.

The 'E' part of the registers can't be accessed invidually.

SI/DI/SP/BP aren't byte-accessible.

Some registers have special purpose. SI/DI/SP source/destination/stack are
easy to remember, but having to remember that, for instance, that these were
r0, r3, r5 (arbitrarily chosen here) would be harder.

On other and properly designed hardware with more registers and a more
coherent opcode map, r0-rxx naming would make sense. But on x86, it makes
about as much sense at a/b's weird "line noise" language.


.

Relevant Pages

  • Re: non load/store architecture?
    ... Programmers can write great code on a RISC ... Especially in a PC marketplace dominated by the x86. ... Lots of registers and an orthogonal instruction set are important - both have these. ... The lack of registers means much more memory IO, which causes stalls and requires complex scheduling. ...
    (comp.arch.embedded)
  • Re: Intel publishes Larrabee paper
    ... Using x86 as the base it is understandable that the third vector operand ... 32 registers times 4 sets, plus some rename registers and you are ... visible registers your actual register set becomes large, ... The die size tradeoffs of 4 way multi threading is mostly about reducing ...
    (comp.arch)
  • Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
    ... to the SBCL developers saying that they don't use a precise GC on x86 ... should be more likely that their stack locations have to be touched ... than on architectires with more registers. ... and initializing all those stack locations would ...
    (comp.lang.lisp)
  • Re: What cpus to compile for (in order)?
    ... >>> I'm at the stage of looking at code generation options and would like to ... >> in my case, I aim for x86 and x86-64, and that is about it. ... >> as for ia64, I am not sure if it has much chance of really going anywhere ... structure, different treatment of registers, ...). ...
    (comp.lang.misc)
  • Re: Ommiting frame pointer
    ... which speeds things up on processors with few registers (in ... just because of extra indirections. ... I've read that some architectures have no performance penalty for PIC, but x86 and amd64 definitely do not fall in that group. ...
    (comp.lang.c)