Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: [RFC] mips gdb fails to detect o32
Date: Wed, 07 Aug 2002 20:00:00 -0000	[thread overview]
Message-ID: <3D51DA64.8B93CC9@redhat.com> (raw)
In-Reply-To: <3D51DBDF.50401@ges.redhat.com>

Andrew Cagney 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.  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.
> >
> > 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.
> 
> Um, won't the final:
> 
>         if (mips_abi == MIPS_ABI_UNKNOWN)
>           mips_abi = MIPS_ABI_032;
> 
> kick in?

No, not if MIPS_ABI_DEFAULT is defined....


  reply	other threads:[~2002-08-08  3:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07 17:42 Michael Snyder
2002-08-07 17:46 ` Daniel Jacobowitz
2002-08-07 17:57   ` Michael Snyder
2002-08-07 18:01     ` Daniel Jacobowitz
2002-08-07 19:49 ` Andrew Cagney
2002-08-07 20:00   ` Michael Snyder [this message]
2002-08-07 20:11     ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D51DA64.8B93CC9@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=cagney@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox