This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: MIPS: Handle the DSP registers



Daniel Jacobowitz wrote:
>
>   
>> Index: binutils-quilt/src/gdb/features/mips-linux.xml
>> ===================================================================
>> --- binutils-quilt.orig/src/gdb/features/mips-linux.xml	2007-12-07 15:08:21.000000000 +0000
>> +++ binutils-quilt/src/gdb/features/mips-linux.xml	2007-12-07 15:13:02.000000000 +0000
>> @@ -11,6 +11,7 @@
>>    <xi:include href="mips-cpu.xml"/>
>>    <xi:include href="mips-cp0.xml"/>
>>    <xi:include href="mips-fpu.xml"/>
>> +  <xi:include href="mips-dsp.xml"/>
>>     
>
> And a corrolary of that is that we'll have two mips-linux
> descriptions, with and without the DSP registers.
>   

Sounds like this mechanism could rapidly get unwieldy if there were many
disjoint, optional register sets supported by an architecture -- would
you need a different description for each possible permutation? For
example with a bare-iron target you might want to omit the
floating-point register descriptions for CPUs which don't have a h/w
FPU, so then we've got Base, Base+FPU, Base+DSP, Base+FPU+DSP. Then
double again for 32-bit vs 64-bit, and so on. Or have I missed something.

Nigel


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]