Re: [PATCH v12 2/2] gdb: mips: Add MIPSR6 support

["Maciej W. Rozycki" <macro@orcam.me.uk>]

On Sun, 2 Mar 2025, Maciej W. Rozycki wrote:

>  This all also means I can use the R3400 system to reliably verify GDB 
> changes and will proceed with your submission once I'm back from my 
> holiday in a fortnight's time.  Meanwhile I do hope this analysis helps.

 I have regression-tested your change now and while the problem previously 
noted persists with `call-ar-st' and `varargs' tests, leaving them stuck 
forever in a weird state:

macro     1299  0.0  0.0     0    0 ?        XW   Mar24   0:03 [call-ar-st]
macro     4501  0.0  0.0     0    0 ?        XW   Mar24   0:05 [varargs]

results are looking good otherwise, except for the newly-added R6 case:

Running .../gdb/testsuite/gdb.arch/mips-64-r6.exp ...
gdb compile failed, Assembler messages:
Fatal error: can't create .../gdb/testsuite/gdb.arch/mips-64-r60.o: No such file or directory
DUPLICATE: gdb.arch/mips-64-r6.exp: failed to prepare

This is because there's no output directory present for the object file 
requested: there's no gdb.arch/ under .../gdb/testsuite/.  I reckon it's 
been many years already since our directory arrangement here was changed.  
Have you run your verification with the upstream trunk version of GDB?

 Also the duplicate failure message needs to be corrected as test messages 
are expected to be uniquely identifiable.

 Please update your patch accordingly and resubmit; meanwhile I'll have a 
detailed look at the backend updates.

  Maciej