From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: gdb-patches@sourceware.org, gdb-patches@sources.redhat.com
Subject: Re: [COMMITTED] allow gdb to access altivec registers - OK to commit?
Date: Wed, 02 Nov 2005 14:54:00 -0000 [thread overview]
Message-ID: <20051102135656.GA27057@nevyn.them.org> (raw)
In-Reply-To: <200511011705.40006.pgilliam@us.ibm.com>
On Tue, Nov 01, 2005 at 05:05:40PM -0800, Paul Gilliam wrote:
> On Tuesday 01 November 2005 16:16, Daniel Jacobowitz wrote:
> > > > + /* FIXME: pgilliam/2005-10-21: Assume all PowerPC 64-bit linux systems
> > > > + have altivec registers. If not, ptrace will fail the first time it's
> > > > + called to access one and will not be called again. This wart will
> > > > + be removed when Daniel Jacobowitz's proposal for autodetecting target
> > > > + registers is implimented. */
> >
> > Andreas already pointed out this typo; could you fix it, please?
>
> I fixed it before I committed the patch, but I didn't repost the corrected patch.
>
> Do you want me to post the corrected patch?
Don't bother, but please attach the corrected patch in the future.
--
Daniel Jacobowitz
CodeSourcery, LLC
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: gdb-patches@sourceware.org, gdb-patches@sources.redhat.com
Subject: Re: [COMMITTED] allow gdb to access altivec registers - OK to commit?
Date: Wed, 02 Nov 2005 14:52:00 -0000 [thread overview]
Message-ID: <20051102135656.GA27057@nevyn.them.org> (raw)
Message-ID: <20051102145200.77FF9HstOuxATDuafSB5FSuhfqLyyQZuPwVkQYGr3Bw@z> (raw)
In-Reply-To: <200511011705.40006.pgilliam@us.ibm.com>
On Tue, Nov 01, 2005 at 05:05:40PM -0800, Paul Gilliam wrote:
> On Tuesday 01 November 2005 16:16, Daniel Jacobowitz wrote:
> > > > + /* FIXME: pgilliam/2005-10-21: Assume all PowerPC 64-bit linux systems
> > > > + have altivec registers. If not, ptrace will fail the first time it's
> > > > + called to access one and will not be called again. This wart will
> > > > + be removed when Daniel Jacobowitz's proposal for autodetecting target
> > > > + registers is implimented. */
> >
> > Andreas already pointed out this typo; could you fix it, please?
>
> I fixed it before I committed the patch, but I didn't repost the corrected patch.
>
> Do you want me to post the corrected patch?
Don't bother, but please attach the corrected patch in the future.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-02 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 21:11 Paul Gilliam
2005-11-02 0:16 ` Daniel Jacobowitz
2005-11-02 1:03 ` Paul Gilliam
2005-11-02 4:28 ` Paul Gilliam
2005-11-02 14:54 ` Daniel Jacobowitz [this message]
2005-11-02 14:52 ` 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=20051102135656.GA27057@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-patches@sourceware.org \
--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