From: Aldy Hernandez <aldyh@redhat.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: gcc external <gcc@gcc.gnu.org>
Subject: rs6000 NON_SPECIAL_REGS
Date: Sun, 16 Dec 2001 19:55:00 -0000 [thread overview]
Message-ID: <1008561037.20065.344.camel@litecycle.cc.andrews.edu> (raw)
is there a reason why NON_SPECIAL_REGS is not the exact bit opposite of
SPECIAL_REGS?
{ 0xffffffff, 0xffffffff, 0x00000008, 0x00000000 }, /* NON_SPECIAL_REGS */ \
{ 0x00000000, 0x00000000, 0x00000007, 0x00000000 }, /* SPECIAL_REGS */ \
aldy
next reply other threads:[~2001-12-17 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 19:55 Aldy Hernandez [this message]
2001-12-16 20:04 ` David Edelsohn
2001-12-16 21:59 ` Aldy Hernandez
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=1008561037.20065.344.camel@litecycle.cc.andrews.edu \
--to=aldyh@redhat.com \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).