Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: David Taylor <taylor@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: ARCH_NUM_REGS
Date: Thu, 22 Feb 2001 16:44:00 -0000	[thread overview]
Message-ID: <3A95B218.1E334FBC@apple.com> (raw)
In-Reply-To: <200102222230.RAA17311@texas.cygnus.com>

David Taylor wrote:
> 
> In addition to NUM_REGS and NUM_PSEUDO_REGS, there's the define
> ARCH_NUM_REGS -- which by default is the same as NUM_REGS.
> 
> One presumes that ARCH_NUM_REGS is meant to have slightly different
> semantics than NUM_REGS, but it isn't documented and it doesn't seem
> to be used in any consistent fashion that I've discerned.
> 
> So, what are the intended semantics of ARCH_NUM_REGS?

Check out m88k/tm-cxux.h, where the number of registers from the
inferior would depend on whether an 88110 was in use, as detected
by code in cxux-nat.c.  At the time, NUM_REGS had to be a constant,
so ARCH_NUM_REGS was its dynamically-sized counterpart.  This was
actually one of the problems that got me to thinking about GDB's
need to be able to vary the target architecture's characteristics
at runtime...

ARCH_NUM_REGS could probably be retired along with CX/UX support.
The OS was barely in existence two years ago, and may have
been discontinued by now.

Stan


      reply	other threads:[~2001-02-22 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 14:30 ARCH_NUM_REGS David Taylor
2001-02-22 16:44 ` Stan Shebs [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=3A95B218.1E334FBC@apple.com \
    --to=shebs@apple.com \
    --cc=gdb@sources.redhat.com \
    --cc=taylor@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