Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: rs6000: no more legacy regcache
Date: Fri, 28 May 2004 21:03:00 -0000	[thread overview]
Message-ID: <20040528140331.423d0a8b@saguaro> (raw)
In-Reply-To: <vt2aczs5qta.fsf@zenia.home>

On 28 May 2004 13:50:41 -0500
Jim Blandy <jimb@redhat.com> wrote:

> This causes no regressions on powerpc-unknown-linux-gnu, and fixes
> several failures in gdb.base/store.exp on powerpc-ibm-aix4.3.3.0.
> It allows powerpc-eabispe to run on the simulator at all.  And I think
> it clears the way for removing the register offset stuff in
> rs6000-tdep.c.
> 
> 2004-05-27  Jim Blandy  <jimb@redhat.com>
> 
> 	* rs6000-tdep.c: Use the modern gdbarch methods for handling the
> 	register set, so our regcache isn't declared "legacy" and our E500
> 	pseudoregister read and write functions aren't ignored.
> 	(rs6000_register_byte, rs6000_register_raw_size,
> 	rs6000_register_virtual_type, rs6000_register_convertible,
> 	rs6000_register_convert_to_virtual,
> 	rs6000_register_convert_to_raw): Deleted.
> 	(rs6000_register_type, rs6000_convert_register_p,
> 	rs6000_register_to_value, rs6000_value_to_register): New
> 	functions.
> 	(rs6000_gdbarch_init): Don't register
> 	gdbarch_deprecated_register_size,
> 	gdbarch_deprecated_register_bytes,
> 	gdbarch_deprecated_register_byte,
> 	gdbarch_deprecated_register_raw_size,
> 	gdbarch_deprecated_register_virtual_type,
> 	gdbarch_deprecated_register_convertible,
> 	gdbarch_deprecated_register_convert_to_virtual, or
> 	gdbarch_deprecated_register_convert_to_raw methods.  Instead,
> 	register gdbarch_register_type, gdbarch_convert_register_p,
> 	gdbarch_register_to_value, and gdbarch_value_to_register methods.

Okay.

Kevin


  reply	other threads:[~2004-05-28 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 18:51 Jim Blandy
2004-05-28 21:03 ` Kevin Buettner [this message]
2004-05-28 23:29   ` Jim Blandy

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=20040528140331.423d0a8b@saguaro \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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