From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] mips n64 support, part 1
Date: Thu, 01 Aug 2002 12:06:00 -0000 [thread overview]
Message-ID: <20020801190652.GA13050@nevyn.them.org> (raw)
In-Reply-To: <3D4985BA.1080308@ges.redhat.com>
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. The marker sections are
GCC-specific.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-01 19:06 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 [this message]
2002-08-01 12:13 ` Kevin Buettner
2002-08-01 12:21 ` Daniel Jacobowitz
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=20020801190652.GA13050@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