Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Eager <eager@eagercon.com>
Cc: gdb@sources.redhat.com
Subject: Re: PowerPC 405 support
Date: Sat, 24 Jun 2006 03:22:00 -0000	[thread overview]
Message-ID: <20060624025732.GA16111@nevyn.them.org> (raw)
In-Reply-To: <449CA2CE.3020100@eagercon.com>

On Fri, Jun 23, 2006 at 07:26:22PM -0700, Michael Eager wrote:
> 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?

I'm going to guess here, but probably this would be a better suited
question for binutils@.  GDB doesn't really have much knowledge about
PPC variants, just the bits it inherits from libopcodes.

-- 
Daniel Jacobowitz
CodeSourcery


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24  2:57 Michael Eager
2006-06-24  3:22 ` Daniel Jacobowitz [this message]
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=20060624025732.GA16111@nevyn.them.org \
    --to=drow@false.org \
    --cc=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