>This is one of the intended purposes of this mechanism, and as I
>>indicated, is needed by MIPS. Being able to project an arbitrary [debug
>>info] view of the registers onto the raw register buffer.
>>
>>BTW, what happens when there is an attempt to write a long long value?
>>GDB again assumes that it can write to contigious registers - the reason
>>why REGISTER_BYTE can't be killed.
>
>
>That ugliness could go away too with Mark's introduced method. GDB
>could be fixed to find the next register properly.
GDB also uses it to encode offsets into a register. It also does not
help the MIPS where the debug register does need to be projected into
the raw registers. Why have add more mechanisms when the existing one
is sufficient. Focus the effort on fixing the real problem.
BTW, my comment about no names was wrong. They can be named, that
restriction should have been removed by the introduction of reggroups.
Well, in that case I guess it would work. Let's do it?
It still feels much more like a hack to me than Mark's approach; I'll
just quietly disagree I suppose.