From: Michael Hayes <m.hayes@elec.canterbury.ac.nz>
To: Stan Shebs <shebs@cygnus.com>
Cc: gdb@sourceware.cygnus.com
Subject: Proposal for handling large numbers of registers
Date: Fri, 06 Aug 1999 17:33:00 -0000 [thread overview]
Message-ID: <14251.31513.361599.969792@ongaonga.elec.canterbury.ac.nz> (raw)
In-Reply-To: <199908062333.QAA16667@andros.cygnus.com>
Stan Shebs writes:
> So I'm considering importing the idea of "register classes" from GCC.
> GCC uses the class idea to guide allocation and instruction selection,
> but we don't even need that much; just define the names of the classes
> and which registers belong to each.
I like this idea.
It would be nice if one could just cut the register class definitions
from gcc tm.h and paste them into gdb tm.h.
Ideally one could refer to the class names by their full name, such as
ADDR_REGS, or by their class letter, such as 'a'.
Michael.
next parent reply other threads:[~1999-08-06 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199908062333.QAA16667@andros.cygnus.com>
1999-08-06 17:33 ` Michael Hayes [this message]
1999-08-06 18:27 ` J.T. Conklin
1999-08-09 16:31 ` J.T. Conklin
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=14251.31513.361599.969792@ongaonga.elec.canterbury.ac.nz \
--to=m.hayes@elec.canterbury.ac.nz \
--cc=gdb@sourceware.cygnus.com \
--cc=shebs@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