Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: let gdbarch define FP0_REGNUM on rs6000
Date: Tue, 04 May 2004 13:52:00 -0000	[thread overview]
Message-ID: <4097A012.2050409@gnu.org> (raw)
In-Reply-To: <vt2ad0phxz0.fsf@zenia.home>

> 2004-05-03  Jim Blandy  <jimb@redhat.com>
> 
> 	* config/rs6000/tm-rs6000.h (FP0_REGNUM): Delete.  Let gdbarch.h
> 	define this.
> 	* rs6000-tdep.c (rs6000_gdbarch_init): Set gdbarch_fp0_regnum.
> 
> diff -cr src.no-gplast-fplast/gdb/config/rs6000/tm-rs6000.h src/gdb/config/rs6000/tm-rs6000.h
> *** gdb/config/rs6000/tm-rs6000.h	2004-05-03 17:32:42.000000000 -0500
> --- gdb/config/rs6000/tm-rs6000.h	2004-05-03 17:39:34.000000000 -0500
> ***************
> *** 64,78 ****
>   #define	PROCESS_LINENUMBER_HOOK()	aix_process_linenos ()
>   extern void aix_process_linenos (void);
>   
> - /* Register numbers of various important registers.
> -    Note that some of these values are "real" register numbers,
> -    and correspond to the general registers of the machine,
> -    and some are "phony" register numbers which are too large
> -    to be actual register numbers as far as the user is concerned
> -    but do serve to get the desired values when passed to read_register.  */
> - 
> - #define FP0_REGNUM 32		/* Floating point register 0 */

Note that FP0_REGNUM is on the deprecate hit list, it's superseeded by 
things like reggroups and regsets.  As with other code, you should 
s/FP0_REGNUM/RS6000_FP0_REGNUM/ where possible.

Andrew



  reply	other threads:[~2004-05-04 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 23:55 Jim Blandy
2004-05-04 13:52 ` Andrew Cagney [this message]
2004-05-04 15:20   ` Jim Blandy
2004-05-04 16:01     ` Kevin Buettner
2004-05-04 20:45       ` Jim Blandy
2004-05-04 22:03         ` Kevin Buettner
2004-05-05  1:47           ` 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=4097A012.2050409@gnu.org \
    --to=cagney@gnu.org \
    --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