Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Deprecate read_register_gen() / write_register_gen()
Date: Sat, 02 Nov 2002 08:22:00 -0000	[thread overview]
Message-ID: <3DC3FBCC.8050801@redhat.com> (raw)
In-Reply-To: <20021102145850.GA24106@nevyn.them.org>

> On Sat, Nov 02, 2002 at 09:48:03AM -0500, Andrew Cagney wrote:
> 
>> These functions are now really redundant - equivalent regcache variants 
>> are available.  Apart from the fringes (-tdep files) there are hardly 
>> any references left.
> 
> 
> When you deprecate without removing, would you mind adding a pointer to
> the replacement interfaces in headers near the declaration?  Otherwise
> the remaining references are a pain for individual maintainers to clean
> up later.

I forgot :-( I'll add something but it's going to be pretty wishy washy 
:-(  The problem is that the obvious change, vis:
	read_register_gen (regnum, buf);
to:
	regcache_cooked_read (current_regcache, regnum, buf)
is wrong.  Invariably, the containing function is what really needs an 
overhaul, vis:

static void
mips_push_register (CORE_ADDR * sp, int regno)
{
   ....
   deprecated_read_register_gen (regno, buffer);
   write_memory (*sp, buffer + offset, regsize);
}

(this should be parameterized with a register cache).

Andrew



      reply	other threads:[~2002-11-02 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-02  6:48 Andrew Cagney
2002-11-02  6:58 ` Daniel Jacobowitz
2002-11-02  8:22   ` Andrew Cagney [this message]

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=3DC3FBCC.8050801@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.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