From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] ppc-linux-nat.c AltiVec regs ptrace
Date: Wed, 20 Feb 2002 18:57:00 -0000 [thread overview]
Message-ID: <20020220215702.B14034@nevyn.them.org> (raw)
In-Reply-To: <15476.22212.358982.6179@localhost.redhat.com>
On Wed, Feb 20, 2002 at 09:09:08PM -0500, Elena Zannoni wrote:
> Daniel Jacobowitz writes:
> > On Wed, Feb 20, 2002 at 07:28:27PM -0500, Elena Zannoni wrote:
> > > In case of 2.2.5 the powerpc version of the file gets installed. While
> > > for 2.2.1 the one with the definitions for PTRACE_GETFPXREGS is installed.
> > >
> > > Ok then, should we support the older version or not?
> > > If not we have two options:
> > >
> > > 1. if glibc gets a patch with the new PTRACE_GETVRREGS requests, then
> > > we can add another different configuration check.
> > >
> > > 2. We can just rely on the run time check. Which means I have to redo
> > > the patch again [where is that bucket].
> > >
> > > Actually doing just 2 would work also with the older version, I guess.
> > > Unless I am missing some other subtlety. Ok I'll change it.
> >
> > Sounds good to me. Might want to submit a patch to add GETVRREGS to
> > libc, also, I suppose...
>
> Yes, it's probably better.
>
> Here is a new patch.
>
> 2002-02-20 Elena Zannoni <ezannoni@redhat.com>
>
> * ppc-linux-nat.c (PTRACE_GETVRREGS, PTRACE_SETVRREGS): Define.
I like this much better, thank you!
My only concern is that you'll have a problem when glibc does define
them; might want to conditionally define these.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-21 2:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 12:21 Elena Zannoni
2002-02-20 12:39 ` Daniel Jacobowitz
2002-02-20 13:07 ` Elena Zannoni
2002-02-20 14:15 ` Daniel Jacobowitz
2002-02-20 14:34 ` Andrew Cagney
2002-02-20 15:07 ` Elena Zannoni
2002-02-20 15:46 ` Daniel Jacobowitz
2002-02-20 16:28 ` Elena Zannoni
2002-02-20 16:34 ` Daniel Jacobowitz
2002-02-20 18:09 ` Elena Zannoni
2002-02-20 18:57 ` Daniel Jacobowitz [this message]
2002-02-20 20:10 ` Elena Zannoni
2002-02-20 21:04 ` Kevin Buettner
2002-02-21 7:33 ` Elena Zannoni
2002-02-21 7:33 ` Kevin Buettner
2002-02-21 7:39 ` Elena Zannoni
2002-02-21 8:00 ` Daniel Jacobowitz
2002-02-21 13:25 ` Elena Zannoni
2002-02-21 13:46 ` 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=20020220215702.B14034@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@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