From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC/RFA] Add regcache_raw_{supply,collect}
Date: Fri, 29 Aug 2003 10:23:00 -0000 [thread overview]
Message-ID: <200308291023.h7TANQge034379@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3F4EA302.90407@redhat.com> (message from Andrew Cagney on Thu, 28 Aug 2003 20:49:06 -0400)
Date: Thu, 28 Aug 2003 20:49:06 -0400
From: Andrew Cagney <ac131313@redhat.com>
BTW, in the ARI, I've the comment:
supply register
Replace supply_register() with something involving the regcache, or a TPID
so yep.
Missed that. Anyway, I think supplying the regcache is better than
supplying a TPID.
Can you at the same time re-implement supply_register and
regcache_collect to use these new methods. I'll then add
supply_register and regcache_collect to the deprecate list.
This is not entirely without a risk. I want to keep the new
interfaces "legacy-free", so they're not doing exactly the same thing
as the old interfaces. Therefore I chose to re-implement the old
interfaces in a seperate commit. The new functions are checked in now.
Mark
next prev parent reply other threads:[~2003-08-29 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 22:02 Mark Kettenis
2003-08-29 0:49 ` Andrew Cagney
2003-08-29 10:23 ` Mark Kettenis [this message]
2003-08-29 14:27 ` Andrew Cagney
2003-08-29 15:36 ` Andrew Cagney
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=200308291023.h7TANQge034379@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@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