This is the mail archive of the gdb-patches@sources.redhat.com 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]

[almost-obvious patch, and 6.0 RFA] treat mipsisa64 as 64-bitMIPS.


Currently, the gdb configury doesn't DTRT with "mipsisa64", i.e., it
doesn't treat it as 64-bit MIPS.

This causes problems when you want to debug with sim, you end with the
error:

18 [ldt-sj3-010] bin % mipsisa64-elf-gdb 
tGNU gdb 2003-08-11-cvs
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=mipsisa64-elf".a
(gdb) target sim
Size of register  (0/0) incorrect (8 instead of 4))Connected to the simulator.
(gdb) 

(I'm sure it causes other problems, too.  8-)


So, this patch adds 'mipsisa64' variants for all of the generic
'mips64' configure.tgt entries.

The reason this patch is *almost* but not quite obvious is that I
don't know what the mips64*-big-* target is about.  It looks suitably
generic that, assuming it should exist at all, it should have a
mipsisa64* entry.  However i really don't know.  (The -big- and
-little- targets are confusing to me.  I mean, why do they exist any
more at all, and why is there only a 32-bit -little- target and no
64-bit one?)

Note that I don't think that most of these targets are horribly useful
anymore, but they should probably have "mipsisa64" variants for
completeness.

(The issue is that if you configure a mipsisa64<some-cpu>-... GDB,
e.g. mipsisa64sb1-..., you should get different simulator bits than if
you do mips64<some-other-cpu>-...  Personally, the more I think about
it, I think that the choice of "mipsisa32" and "mipsisa64" to name
MIPS32/MIPS64 ISA targets was unfortunate...  But I didn't set the
trend, and it would have been wrong to name MIPS64 something other
than mipsisa64 once mipsisa32 existed...  *sigh*)


Verified that this does the expected thing on the trunk with
mipsisa64-elf.

Also verified that it applies cleanly to the 6.0-branch configure.tgt,
but not tested further than that.  (read it, it won't cause harm.  8-)




cgd
--
2003-08-13  Chris Demetriou  <cgd@broadcom.com>

        * configure.tgt (mipsisa64*-big-*, mipsisa64*el-*-ecoff*)
        (mipsisa64*-*-ecoff*, mipsisa64*el-*-elf*)
        (mipsisa64*-*-elf*, mipsisa64*-*-linux*): Treat identically
        to corresponding "mips64" configurations.

Index: configure.tgt
===================================================================
RCS file: /cvs/src/src/gdb/configure.tgt,v
retrieving revision 1.111
diff -u -p -r1.111 configure.tgt
--- configure.tgt	1 Aug 2003 21:14:33 -0000	1.111
+++ configure.tgt	13 Aug 2003 17:43:12 -0000
@@ -144,16 +144,22 @@ m68*-*-vxworks*)	gdb_target=vxworks68 ;;
 
 mcore*-*-*)		gdb_target=mcore ;;
 mips64*-big-*)		gdb_target=mips64 ;;
+mipsisa64*-big-*)	gdb_target=mips64 ;;
 mips*-big-*)		gdb_target=mips ;;
 mips*-dec-*)		gdb_target=mips ;;
 mips*-*-pe)		gdb_target=wince ;;
 mips64*el-*-ecoff*)	gdb_target=embedl64 ;;
+mipsisa64*el-*-ecoff*)	gdb_target=embedl64 ;;
 mips64*-*-ecoff*)	gdb_target=embed64 ;;
+mipsisa64*-*-ecoff*)	gdb_target=embed64 ;;
 mips64*vr*-*-elf*)	gdb_target=mips64 ;;
 mips*tx39*-elf*)	gdb_target=tx39 ;;
 mips64*el-*-elf*)	gdb_target=embedl64 ;;
+mipsisa64*el-*-elf*)	gdb_target=embedl64 ;;
 mips64*-*-elf*)		gdb_target=embed64 ;;
+mipsisa64*-*-elf*)	gdb_target=embed64 ;;
 mips64*-*-linux*)	gdb_target=linux64 ;;
+mipsisa64*-*-linux*)	gdb_target=linux64 ;;
 mips*el-*-ecoff*)	gdb_target=embedl ;;
 mips*-*-ecoff*)		gdb_target=embed ;;
 mips*el-*-elf*)		gdb_target=embedl ;;


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