From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc,rfa:ppc64] Add osabi wildcard support
Date: Wed, 29 Oct 2003 19:30:00 -0000 [thread overview]
Message-ID: <3FA01545.4070609@redhat.com> (raw)
In-Reply-To: <1031029033241.ZM4676@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
> On Oct 27, 6:54pm, Andrew Cagney wrote:
>
>
>> > preferences?
>> >
>> > At the moment, I prefer the explicit registration of architecture
>> > variants. I'd prefer to wait on adding the wildcard mechanism until a
>> > more compelling need for it is demonstrated.
>
>>
>> Per the discussion between myself and daniel, the current proposal is to
>> add:
>>
>> > > gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_ppc, ...
>> > > gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_ppc64, ...
>>
>> >
>> > plus, I believe, either
>> > + gdbarch_register_osabi (bfd_arch_rs6000, bfd_mach_rs6k);
>>
>> to the linux file. Is that pre-approved?
>
>
> Yes.
I've checked this in. No more mysterious message during startup!
thanks,
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1167 bytes --]
2003-10-29 Andrew Cagney <cagney@redhat.com>
* ppc-linux-tdep.c (_initialize_ppc_linux_tdep): Instead of the
default PPC machine, register 32-bit and 64-bit PPC, and rs6k.
Index: ppc-linux-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/ppc-linux-tdep.c,v
retrieving revision 1.45
diff -u -r1.45 ppc-linux-tdep.c
--- ppc-linux-tdep.c 24 Oct 2003 20:24:06 -0000 1.45
+++ ppc-linux-tdep.c 29 Oct 2003 19:21:33 -0000
@@ -1083,7 +1083,13 @@
void
_initialize_ppc_linux_tdep (void)
{
- gdbarch_register_osabi (bfd_arch_powerpc, 0, GDB_OSABI_LINUX,
- ppc_linux_init_abi);
+ /* Register for all sub-familes of the POWER/PowerPC: 32-bit and
+ 64-bit PowerPC, and the older rs6k. */
+ gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_ppc, GDB_OSABI_LINUX,
+ ppc_linux_init_abi);
+ gdbarch_register_osabi (bfd_arch_powerpc, bfd_mach_ppc64, GDB_OSABI_LINUX,
+ ppc_linux_init_abi);
+ gdbarch_register_osabi (bfd_arch_rs6000, bfd_mach_rs6k, GDB_OSABI_LINUX,
+ ppc_linux_init_abi);
add_core_fns (&ppc_linux_regset_core_fns);
}
prev parent reply other threads:[~2003-10-29 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 23:25 Andrew Cagney
2003-10-23 23:41 ` Daniel Jacobowitz
2003-10-24 0:38 ` Andrew Cagney
2003-10-24 0:52 ` Daniel Jacobowitz
2003-10-24 14:47 ` Andrew Cagney
2003-10-24 14:31 ` Andrew Cagney
2003-10-24 14:55 ` Daniel Jacobowitz
2003-10-28 21:59 ` Kevin Buettner
2003-10-28 23:56 ` Andrew Cagney
2003-10-29 3:33 ` Kevin Buettner
2003-10-29 19:30 ` Andrew Cagney [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=3FA01545.4070609@redhat.com \
--to=ac131313@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