Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagercon.com>
To: tromey@redhat.com
Cc: Michael Snyder <msnyder@vmware.com>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	 Joel Brobecker <brobecker@adacore.com>
Subject: Re: Add register definitions for PowerPC 405
Date: Mon, 27 Jul 2009 09:03:00 -0000	[thread overview]
Message-ID: <4A6CFE37.9020404@eagercon.com> (raw)
In-Reply-To: <m3r5w5oie6.fsf@fleche.redhat.com>

Tom Tromey wrote:
>>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:
> 
>>> 2009-06-26  Michael Eager <eager@eagercon.com>
>>> * features/rs6000/powerpc-405.xml: New.
>>> * rs6000-tdep.c: Add include & initialize for
>>> powerpc-405.c, add 405 to variants.
>>> * features/rs6000/powerpc-405.c: Generate.
> 
> Michael> Committing on behalf of Michael Eager, who (I guess)
> Michael> doesn't have write-after-approval access.
> 
> I get a build failure with cvs head:
> 
> ../../src/gdb/rs6000-tdep.c:2953: error: ‘bfd_mach_ppc_405’ undeclared here (not in a function)
> 
> Was there a BFD part of this patch that did not go in?

Yes.  http://sourceware.org/ml/gdb-patches/2009-06/msg00754.html

Mike -- can you check this in for me?

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


  reply	other threads:[~2009-07-27  1:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 20:58 Michael Snyder
2009-07-21 22:31 ` Paul Pluzhnikov
2009-07-22  0:12   ` Michael Eager
2009-07-24 22:47 ` Tom Tromey
2009-07-27  9:03   ` Michael Eager [this message]
2009-07-27 14:57     ` Michael Snyder
2009-07-27 16:50       ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2009-06-26 19:21 Michael Eager
2009-06-29 17:23 ` Joel Brobecker

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=4A6CFE37.9020404@eagercon.com \
    --to=eager@eagercon.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=tromey@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