Re: [RFC] mips gdb fails to detect o32

[Daniel Jacobowitz <drow@mvista.com>]

On Wed, Aug 07, 2002 at 05:38:39PM -0700, Michael Snyder wrote:
> Daniel Jacobowitz wrote:
> > 
> > On Wed, Aug 07, 2002 at 05:23:43PM -0700, Michael Snyder wrote:
> > > Well, I just discovered that gdb is failing to detect the o32 abi
> > > when debugging the output of the native Irix compiler.  This patch
> > > seems to help.
> > >
> > > The idea here is, if it's not n32, then if it is MIPS_ARCH_2,
> > > then it must be o32.  However, I've no idea if that's right --
> > > I just know it works so far as I've been able to test it.
> > >
> > > Unfortunately, I haven't been able to test it against EABI,
> > > and I haven't been able to test it against gcc, because gcc
> > > doesn't generate o32.
> > 
> > GCC does generate O32. 
> 
> Really?  How?  It rejects "-mabi=o32".

I believe the GNU tools call it "32".  Yep, that's right.

> > GNU binutils won't use the ARCH/ABI bits in the
> > ELF header in a lot of cases, though; and it emits a better way to
> > identify the ABI.
> 
> Can you be more specific?

See the patch I added recently to recognize the ".mdebug.o32" and
similar sections; GCC emits these in every object file.

> > I don't think keying off MIPS II makes a heck of a lot of sense here...
> > depending on what SGI's tools put out you might want to default to O32
> > if no ABI tag bits are present, but that's a little shadier.
> 
> Andrew added code to make it default to n32 in Novermber 2000.
> I wouldn't want to overrule him...   ;-)

N32 makes more sense for IRIX anyway... there must be some marking
difference though.  If N32 is marked and O32 isn't perhaps the default
should change after all.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer