Re: [RFA] Add support for 64-bit MIPS GNU/Linux targets

[Daniel Jacobowitz <drow@mvista.com>]

On Tue, Dec 24, 2002 at 12:29:35PM -0700, Kevin Buettner wrote:
> On Dec 24,  9:53am, Daniel Jacobowitz wrote:
> 
> > > I'll fix the GDBSERVER_DEPFILES and tm-linux64 nits, but the
> > > supply_gregset issue will require further discussion.  In the interim,
> > > how would you like to proceed?
> > 
> > Since it won't affect thread support for 32-bit MIPS, I've no objection
> > to committing it now.
> 
> Okay, it's in.  In addition to fixing the problems previously discussed,
> I found it necessary to change the osabi registration (in mips-linux-tdep.c)
> from:
> 
>   gdbarch_register_osabi (bfd_arch_mips, 0, GDB_OSABI_LINUX,
>                           mips_linux_init_abi);
> 
> to:
> 
>   for (arch_info = bfd_lookup_arch (bfd_arch_mips, 0);
>        arch_info != NULL;
>        arch_info = arch_info->next)
>     {
>       gdbarch_register_osabi (bfd_arch_mips, arch_info->mach, GDB_OSABI_LINUX,
>                               mips_linux_init_abi);
>     }
> 
> I'm not entirely happy with this change, but I see no way around it
> due to the recent changes to osabi.c.  (I'm open to suggestions for
> better ways to do it...)

OK, that's a problem.  In fact it's disgusting...  A mach value of 0 is
always supposed to mean "default", if I remember my BFD correctly.  Has
the change to pass a machine of 0 broken osabi support for anything
that sets a machine?  It looks that way.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer