From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] W.I.P. AltiVec ppc registers support.
Date: Mon, 19 Nov 2001 22:53:00 -0000 [thread overview]
Message-ID: <1011129222000.ZM19585@ocotillo.lan> (raw)
Message-ID: <20011119225300.cOAPNU1Gq28jGQcjxB-MmUSjM1EApNmonfBaFcCsIpY@z> (raw)
In-Reply-To: Elena Zannoni <ezannoni@cygnus.com> "Re: [RFA] W.I.P. AltiVec ppc registers support." (Nov 29, 4:59pm)
On Nov 29, 4:59pm, Elena Zannoni wrote:
> > With regard to
> >
> > > Index: config/powerpc/nm-linux.h
> > [...]
> > > +#define FETCH_INFERIOR_REGISTERS
> >
> > I think this is a good thing. It *might not* be strictly necessary
> > for adding AltiVec support via PEEKUSER / POKEUSER, but it does give
> > us more control. Also doing this allows us to clean up the code in other
> > ways. E.g, the following bit from config/powerpc/nm-linux.h can be
> > removed:
> >
> > > extern int ppc_register_u_addr (int, int);
> > > #define REGISTER_U_ADDR(addr, blockend, regno) \
> > > (addr) = ppc_register_u_addr ((blockend),(regno));
> >
> > This in turn means that ppc_register_u_addr() can be made static
> > and that the ``ustart'' parameter can be removed. All calls to
> > register_addr() (in your new code) in ppc-linux-nat.c should be
> > changed to invoke ppc_register_u_addr() directly.
> >
>
> Unfortunately not. I thought the same, until I remembered about core
> file debugging. That function is called by fetch_core_registers() in
> core-aout.c.
Hmm... I wonder if Linux/PPC even needs this function in core-aout.c.
Daniel J. is the expert on this stuff. Daniel, doesn't Linux/PPC use
core-regset.c instead?
Kevin
next prev parent reply other threads:[~2001-11-29 22:21 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 18:09 Elena Zannoni
2001-11-18 13:27 ` Elena Zannoni
2001-11-18 14:11 ` Daniel Jacobowitz
2001-11-19 12:59 ` Andrew Cagney
2001-11-29 9:04 ` Andrew Cagney
2001-11-29 13:10 ` Daniel Jacobowitz
2001-11-19 16:00 ` Daniel Jacobowitz
2001-11-29 13:34 ` Kevin Buettner
2001-11-19 16:42 ` Kevin Buettner
2001-11-29 14:11 ` Kevin Buettner
2001-11-19 22:22 ` Kevin Buettner
2001-11-29 14:27 ` Elena Zannoni
2001-11-19 23:55 ` Elena Zannoni
2001-11-28 22:27 ` Daniel Jacobowitz
2001-12-02 10:28 ` Elena Zannoni
2001-12-02 12:19 ` Andrew Cagney
2001-12-02 14:59 ` Daniel Jacobowitz
2001-12-02 22:25 ` Andrew Cagney
2001-11-28 18:33 ` Daniel Jacobowitz
2001-11-18 13:40 ` Daniel Jacobowitz
2001-11-29 10:40 ` Kevin Buettner
2001-11-19 15:15 ` Kevin Buettner
2001-11-19 18:51 ` Elena Zannoni
2001-11-29 13:53 ` Elena Zannoni
2001-11-29 14:21 ` Kevin Buettner [this message]
2001-11-19 22:53 ` Kevin Buettner
2001-11-29 14:42 ` Elena Zannoni
2001-11-20 8:37 ` Elena Zannoni
2001-11-29 15:03 ` Andrew Cagney
2001-11-20 8:54 ` Andrew Cagney
2001-11-29 16:27 ` Kevin Buettner
2001-11-20 16:00 ` Kevin Buettner
2001-11-20 16:14 ` Andrew Cagney
2001-11-21 3:33 ` Daniel Jacobowitz
2001-11-29 17:41 ` Daniel Jacobowitz
2001-11-29 16:43 ` Andrew Cagney
2001-11-29 16:36 ` Elena Zannoni
2001-11-20 16:10 ` Elena Zannoni
2001-11-29 17:40 ` Daniel Jacobowitz
2001-11-20 18:00 ` Daniel Jacobowitz
2001-11-29 14:47 ` Daniel Jacobowitz
2001-11-20 8:37 ` Daniel Jacobowitz
2001-11-20 9:07 ` Kevin Buettner
2001-11-20 9:08 ` Andrew Cagney
2001-11-29 15:33 ` Andrew Cagney
2001-11-29 15:15 ` Kevin Buettner
2001-11-29 15:38 ` Daniel Jacobowitz
2001-11-20 9:13 ` Daniel Jacobowitz
2001-11-20 10:09 ` Kevin Buettner
2001-11-29 15:47 ` Kevin Buettner
2001-11-29 15:58 ` Andrew Cagney
2001-11-20 10:59 ` Andrew Cagney
2001-11-29 15:59 ` Daniel Jacobowitz
2001-11-20 11:07 ` Daniel Jacobowitz
2001-11-29 16:17 ` Andrew Cagney
2001-11-20 11:17 ` Andrew Cagney
2001-11-20 17:52 ` Daniel Jacobowitz
2001-11-29 17:39 ` Daniel Jacobowitz
2001-11-29 18:20 ` Andrew Cagney
2001-11-21 4:10 ` Andrew Cagney
2001-11-29 22:36 ` Daniel Jacobowitz
2001-11-21 5:56 ` Daniel Jacobowitz
2001-12-20 10:02 ` Elena Zannoni
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=1011129222000.ZM19585@ocotillo.lan \
--to=kevinb@redhat.com \
--cc=drow@mvista.com \
--cc=ezannoni@cygnus.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