Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Volkov <Andrew.Volkov@transas.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: [RFC/patch 5.1] change NUM_REALREGS to NUM_REGS
Date: Thu, 27 Dec 2001 09:02:00 -0000	[thread overview]
Message-ID: <2E74F312D6980D459F3A05492BA40F8D61DB38@clue.transas.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 185 bytes --]

The attached patch replace NUM_REALREGS macro to NUM_REGS, 
and NUM_REGS to NUM_REGS + NUM_PSEUDO_REGS.

I need this for H8300 maltiarching.

Any suggestions/comments ?

Andrey Volkov


[-- Attachment #2: remote-e7000.diff --]
[-- Type: application/octet-stream, Size: 885 bytes --]

--- remote-e7000.c.old	Mon Jul 16 00:34:13 2001
+++ remote-e7000.c	Thu Dec 27 19:16:06 2001
@@ -922,7 +922,7 @@
   fetch_regs_from_dump (gch, wanted);
 
   /* And supply the extra ones the simulator uses */
-  for (regno = NUM_REALREGS; regno < NUM_REGS; regno++)
+  for (regno = NUM_REGS; regno < NUM_REGS + NUM_PSEUDO_REGS; regno++)
     {
       int buf = 0;
 
@@ -946,7 +946,7 @@
 {
   int regno;
 
-  for (regno = 0; regno < NUM_REALREGS; regno++)
+  for (regno = 0; regno < NUM_REGS; regno++)
     e7000_store_register (regno);
 
   registers_changed ();
@@ -2059,7 +2059,7 @@
   fetch_regs_from_dump (gch, wanted_nopc);
 
   /* And supply the extra ones the simulator uses */
-  for (regno = NUM_REALREGS; regno < NUM_REGS; regno++)
+  for (regno = NUM_REGS; regno < NUM_REGS + NUM_PSEUDO_REGS; regno++)
     {
       int buf = 0;
       supply_register (regno, (char *) &buf);

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-27  9:02 Andrew Volkov [this message]
2002-01-02  8:58 ` Elena Zannoni
2002-01-10  6:03 Andrew Volkov

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=2E74F312D6980D459F3A05492BA40F8D61DB38@clue.transas.com \
    --to=andrew.volkov@transas.com \
    --cc=ezannoni@cygnus.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