Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: gdb@sources.redhat.com
Subject: PowerPC 405 support
Date: Sat, 24 Jun 2006 02:57:00 -0000	[thread overview]
Message-ID: <449CA2CE.3020100@eagercon.com> (raw)

I was looking at adding support to GDB for a variant of
the PPC 405.  This variant has several added instructions
but is otherwise the same, i.e., has the same registers, etc.

I thought I'd add a processor type named Xppc405 or ppc405X
for this variant.  Then I noticed that the 405 is really
not supported as a variant, but the 403 is, and that the 403
has extensions (and at least one hack) for the 405.  There
are opcodes defined for PPC405, but this symbol is aliased
to PPC403.

It looks pretty straight-forward to create a ppc405 variant
and unalias it from the ppc403.  Then create a ppc405X
variant which builds on the ppc405.  Any reason not to do
this?

Alternately I could (a) add the variant's instructions
to the existing PPC405 definition and leave that as an
alias for the PPC403.  That would be quick, but seems dirty.

BTW, does anyone have documentation on the PPC403?  I
can't find any online and if I do unalias PPC405 from PPC403,
I'd like to make sure that the opcodes labeled PPC405 are
really only in the 405, and not also in the 403.


-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


             reply	other threads:[~2006-06-24  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24  2:57 Michael Eager [this message]
2006-06-24  3:22 ` Daniel Jacobowitz
2006-06-24  3:28   ` Michael Eager
2006-06-24  6:32     ` 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=449CA2CE.3020100@eagercon.com \
    --to=eager@eagercon.com \
    --cc=gdb@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