From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: ppc-po-tdep.c?
Date: Fri, 12 Sep 2003 20:43:00 -0000 [thread overview]
Message-ID: <1030912204301.ZM717@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "ppc-po-tdep.c?" (Sep 12, 3:52pm)
On Sep 12, 3:52pm, Andrew Cagney wrote:
> What do you think of a second ABI file (ppc-po-tdep.c?) along the lines
> of ppc-sysv-tdep.c that would contain the "AIX" / "Apple" / "PowerOpen"
> / "SYSVr4 PPC64" ABIs (they are all a close fit).
I think this is a good idea. The name you've suggested is okay with
me also.
As I suggested to Jimi a few days ago, I'd like to eventually see the
generic PPC code moved to its own file. The remainder of
rs6000-tdep.c would then be AIX specific and this file could be
renamed to ppc-aix-tdep.c.
In "outline" form, this is what I'd eventually like to see:
Generic PPC ISA:
ppc-tdep.c - replaces rs6000-tdep.c for generic bits
ABI specific:
ppc-sysv-tdep.c
ppc-po-tdep.c - PowerOpen ABI specific bits; some of rs6000-tdep.c
is moved here.
OS specific:
ppc-aix-tdep.c
ppc-linux-tdep.c
ppcnbsd-tdep.c - I prefer ppc-nbsd-tdep.c though
Native support:
ppc-aix-nat.c - renamed from rs6000-nat.c
ppc-linux-nat.c
ppcnbsd-nat.c - I prefer ppc-nbsd-nat.c though
Kevin
next prev parent reply other threads:[~2003-09-12 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 19:52 ppc-po-tdep.c? Andrew Cagney
2003-09-12 20:43 ` Kevin Buettner [this message]
2003-09-12 21:58 ` ppc-po-tdep.c? Andrew Cagney
2003-09-13 17:03 ` ppc-po-tdep.c? Andrew Cagney
2003-09-15 17:05 ` ppc-po-tdep.c? Kevin Buettner
2003-09-15 21:35 ` ppc-po-tdep.c? Jim Blandy
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=1030912204301.ZM717@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@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