Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: David Taylor <taylor@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] regcache.c (register_fetched) + related changes
Date: Tue, 27 Feb 2001 17:40:00 -0000	[thread overview]
Message-ID: <3A9C5696.2DA70024@cygnus.com> (raw)
In-Reply-To: <200102272224.RAA15833@texas.cygnus.com>

David Taylor wrote:

> I propose that we:
> 
> . add register_fetched

David,

The functionality of register_fetched() overlaps with
set_register_cached() and supply_register().  Rather than add a
redundant method, could an existing interface be used or the current
interfaces rationalized slightly?

Keep in mind that the long term goal is to tighten regcache's interface
signficantly.  That is, eliminate register_valid[], registers[] and
possibly even set_register_cached() replacing them with a small set of
functions such as:
	supply_register()
	supply_unavailable_register()
If you are thinking of proposing further changes then you may want to
keep that in mind.

With regard to regcache.h, yes the two clash.  It both moves code around
and changes the set_register_cached() interface.  If anything regcache.h
makes life easier because it is finally clear what the regcache
interfaces really are.

	Andrew


  parent reply	other threads:[~2001-02-27 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 14:25 David Taylor
2001-02-27 14:48 ` Michael Snyder
2001-02-27 15:21 ` Andrew Cagney
2001-02-27 17:40 ` Andrew Cagney [this message]
2001-02-27 15:27 David Taylor
2001-02-28 13:14 David Taylor
2001-02-28 15:17 ` Andrew Cagney
2001-02-28 16:01   ` Andrew Cagney
2001-02-28 18:27   ` Andrew Cagney
2001-03-01 10:34 David Taylor
2001-03-01 14:07 ` Andrew Cagney
2001-03-01 16:59 David Taylor
2001-03-02  9:06 ` Andrew Cagney
2001-03-02 11:49 ` Andrew Cagney
2001-03-13  8:52   ` 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=3A9C5696.2DA70024@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=taylor@cygnus.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