Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [rfc] Regcache revamp (vip)
Date: Mon, 19 Mar 2001 11:59:00 -0000	[thread overview]
Message-ID: <3AB6652F.1302DAF@cygnus.com> (raw)
In-Reply-To: <3AB2CE20.4AC725CF@cygnus.com>

>         o       The external interfaces
>                 register[], register_valid[]
>                 and register_buffer() are
>                 being documented as deprecated.

>         o       Other pseudo-register interfaces
>                 such as STORE_PSEUDO_REG()
>                 are put in the fireing line.

To update this list.  I think the following can be deprecated:

	register[]
	register_valid[]
	register_buffer()
		Replaced by, on the target side
		  supply_register()
		and on core-gdb side:
		  {read,write}_register_gen()

	STORE_PSEUDO_REGISTER
	FETCH_PSEUDO_REGISTER
		Now handed by the methods
		  gdbarch_{read,write}_register()
		which sits between core GDB and
		the register cache.

	REGISTER_CONVERTIBLE
	REGISTER_CONVERT_TO_RAW
	REGISTER_CONVERT_TO_VIRTUAL
		I think these three are redundant.
		gdbarch_register_{read,write} can
		do any conversion it likes.

	REGISTER_VIRTUAL_SIZE
	MAX_REGISTER_VIRTUAL_SIZE
	REGISTER_VIRTUAL_TYPE
		I think these can be replaced by the
		pair:
		  FRAME_REGISTER_TYPE(frame, regnum)
		  REGISTER_TYPE(regnum)

Scary!

If something gets deprecated it won't be immediatly deleted.  Instead it
will most likely get a rename in a desperate attempt to stop people
cloning it :-)

	Andrew


  parent reply	other threads:[~2001-03-19 11:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3AB2CE20.4AC725CF@cygnus.com>
2001-03-18 14:17 ` Andrew Cagney
2001-03-19 11:59 ` Andrew Cagney [this message]
2001-03-22 15:04 ` Jim Blandy
     [not found]   ` <3ABAAC0F.45A995A3@cygnus.com>
2001-03-23 17:26     ` 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=3AB6652F.1302DAF@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.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