From: Doug Evans <dje@transmeta.com>
To: gdb@sources.redhat.com
Subject: allowing target to say which regs are pseudo regs
Date: Thu, 05 Apr 2001 09:56:00 -0000 [thread overview]
Message-ID: <200104051655.JAA29341@casey.transmeta.com> (raw)
Would it make sense to allow a target to say which regs are pseudo regs?
i.e. make real_register() and pseudo_register() architecture-provided routines
[well, to be more precise, you'd just have one routine of course]
It seems rather clumsy to force a target to have registers
[0,NUM_REGS) be "real" regs and [NUM_REGS,NUM_REGS+NUM_PSEUDO_REGS)
be "pseudo" regs. What's the difference other than
targets get to provide their own read/write routines for pseudo regs?
One would want to replace NUM_REGS and NUM_PSEUDO_REGS with
just NUM_REGS [or some such], and there'd be a set of corresponding
changes throughout the sources.
next reply other threads:[~2001-04-05 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 9:56 Doug Evans [this message]
2001-04-06 11:19 ` 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=200104051655.JAA29341@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=gdb@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