From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, Kris Warkentin <kewarken@qnx.com>
Cc: kettenis@gnu.org,
"Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: Re: [Patch] arch recognition fix for osabi.c
Date: Thu, 19 Jun 2003 22:10:00 -0000 [thread overview]
Message-ID: <1030619220422.ZM4498@localhost.localdomain> (raw)
In-Reply-To: Daniel Jacobowitz <drow@mvista.com> "Re: [Patch] arch recognition fix for osabi.c" (Jun 19, 3:08pm)
On Jun 19, 3:08pm, Daniel Jacobowitz wrote:
> All calls to gdbarch_register_osabi in GDB except for two use mach ==
> 0. The two are mips-linux-tdep.c, which appears to be solving the same
> problem - what a coincidence:
> 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);
> }
> and x86-64. For x86-64 your change is correct since BFD will catch the
> different bits-per-word and return NULL. For mips-linux-tdep it would
> let you remove that loop, which I have a vague memory of being annoyed
> at when it became necessary.
Yes, I wrote that loop, and I too was annoyed when I had to write it.
Kevin
next prev parent reply other threads:[~2003-06-19 22:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 15:40 Kris Warkentin
2003-06-17 15:51 ` Daniel Jacobowitz
2003-06-17 16:04 ` Kris Warkentin
2003-06-19 12:25 ` Kris Warkentin
2003-06-19 13:18 ` Daniel Jacobowitz
2003-06-19 14:48 ` Kris Warkentin
2003-06-19 19:09 ` Daniel Jacobowitz
2003-06-19 22:10 ` Kevin Buettner [this message]
2003-07-11 15:04 ` [ping] " Kris Warkentin
2003-07-11 16:27 ` Mark Kettenis
2003-07-11 16:32 ` Daniel Jacobowitz
2003-07-18 14:13 ` Andrew Cagney
2003-07-18 14:19 ` 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=1030619220422.ZM4498@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
--cc=kewarken@qnx.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