From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] add PowerPC 750 to list of BFD supported PowerPC architectures
Date: Mon, 17 Oct 2005 21:03:00 -0000 [thread overview]
Message-ID: <20051017210329.GA23496@nevyn.them.org> (raw)
In-Reply-To: <200510171354.18895.pgilliam@us.ibm.com>
On Mon, Oct 17, 2005 at 01:54:18PM -0700, Paul Gilliam wrote:
> This patch allows GDB to work with a PowerPC 750 chip. GDB already has what it needs, but BFD needs to know about it.
>
> Should I also submit this patch to bug-binutils@gnu.org?
Try binutils@sourceware.org.
What exactly does this fix? i.e. what doesn't work in GDB without it?
> 2005-10-17 Paul Gilliam <pgilliam@us.ibm.com>
>
> * bfd/cpu-powerpc.c: add ppc 750 to list of supported PowerPC chips.
Capital letter at the start; also describe where you're changing.
Path is relative to the nearest ChangeLog, in this case, bfd's.
* cpu-powerpc.c (bfd_powerpc_archs): Add powerpc:750.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-10-17 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 20:53 Paul Gilliam
2005-10-17 21:03 ` Daniel Jacobowitz [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=20051017210329.GA23496@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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