Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] mips n64 support, part 1
Date: Thu, 01 Aug 2002 12:21:00 -0000	[thread overview]
Message-ID: <20020801192154.GA18466@nevyn.them.org> (raw)
In-Reply-To: <1020801191336.ZM28539@localhost.localdomain>

On Thu, Aug 01, 2002 at 12:13:36PM -0700, Kevin Buettner wrote:
> On Aug 1,  3:06pm, Daniel Jacobowitz wrote:
> 
> > On Thu, Aug 01, 2002 at 03:02:18PM -0400, Andrew Cagney wrote:
> > > >@@ -4352,7 +4354,11 @@ mips_gdbarch_init (struct gdbarch_info i
> > > > 	  break;
> > > > 	case bfd_mach_mips8000:
> > > > 	case bfd_mach_mips10000:
> > > >-	  mips_abi = MIPS_ABI_N32;
> > > >+	  if (bfd_get_flavour (info.abfd) == bfd_target_elf_flavour
> > > >+	      && elf_elfheader (info.abfd)->e_ident[EI_CLASS] == ELFCLASS64)
> > > >+	    mips_abi = MIPS_ABI_N64;
> > > >+	  else
> > > >+	    mips_abi = MIPS_ABI_N32;
> > > > 	  break;
> > > > 	}
> > > >     }
> > > 
> > > This bit should at least have a comment explaining the assumptions 
> > > behind it -- have you actually seen this code being triggered?  I don't 
> > > think the code is ever reached (unless the executable is very old) as 
> > > the earlier:
> > > 
> > >   /* GCC creates a pseudo-section whose name describes the ABI.  */
> > >   if (mips_abi == MIPS_ABI_UNKNOWN && info.abfd != NULL)
> > >     bfd_map_over_sections (info.abfd, mips_find_abi_section, &mips_abi);
> > > 
> > > should catch most modern cases.
> > 
> > Kevin is using IRIX CC, I believe.
> 
> Yes.
> 
> > The marker sections are GCC-specific.
> 
> Actually, I think they're platform specific.  In the tests I did yesterday,
> I didn't see the marker sections in binaries created by gcc either.
> 
> I'll add a comment though.

Blah.  They appear to be conditioned on TARGET_GAS, for whatever
reason; Eric added that in Sept. 2001, not long after they were
originally added.

Hmm...
        (mips_asm_file_start): Add new section to pass abi to gdb.

Just curious - did Red Hat's internal tree have code in GDB to read
this, before I added it to the community tree?  There was about nine
months worth of lag there.

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


      reply	other threads:[~2002-08-01 19:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 11:28 Kevin Buettner
2002-07-31 11:56 ` Daniel Jacobowitz
2002-07-31 12:00   ` Kevin Buettner
2002-07-31 12:50     ` Kevin Buettner
2002-08-01 11:52 ` Andrew Cagney
2002-08-01 12:02 ` Andrew Cagney
2002-08-01 12:06   ` Daniel Jacobowitz
2002-08-01 12:13     ` Kevin Buettner
2002-08-01 12:21       ` Daniel Jacobowitz [this message]

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=20020801192154.GA18466@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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