Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] allow gdb to access altivec registers
Date: Thu, 27 Oct 2005 09:46:00 -0000	[thread overview]
Message-ID: <20051026152933.01ee4fa4@ironwood.lan> (raw)
In-Reply-To: <200510211547.23990.pgilliam@us.ibm.com>

On Fri, 21 Oct 2005 15:47:23 -0700
Paul Gilliam <pgilliam@us.ibm.com> wrote:

> How 'bout this?
> 
> 2005-10-17 __Paul Gilliam __<pgilliam@us.ibm.com>
> 
> 	* rs6000-tdep.c (rs6000_gdbarch_init): Assume that bfd_mach_ppc64 has
> 	altivec unit, just like bfd_mach_ppc.

This change is okay with me.  But do revise the ChangeLog entry to note that
this change affects GNU/Linux only.

Kevin


  reply	other threads:[~2005-10-26 22:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 20:31 Paul Gilliam
2005-10-17 21:05 ` Mark Kettenis
2005-10-17 21:06   ` Daniel Jacobowitz
2005-10-21 22:46     ` Paul Gilliam
2005-10-27  9:46       ` Kevin Buettner [this message]
2005-10-31 22:51         ` [PATCH] allow gdb to access altivec registers - OK to commit? Paul Gilliam
2005-11-01  0:27           ` Andreas Schwab
2005-11-02 20:44           ` Kevin Buettner

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=20051026152933.01ee4fa4@ironwood.lan \
    --to=kevinb@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