From: Alan Modra <alan@SPRI.Levels.UniSA.Edu.Au>
To: "H.J. Lu" <hjl@varesearch.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: An i386 fp register name patch
Date: Sat, 28 Aug 1999 06:05:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9908282145190.31737-100000@mullet.itr.unisa.edu.au> (raw)
In-Reply-To: <19990827191842.315213FC1@varesearch.com>
On Fri, 27 Aug 1999, H.J. Lu wrote:
> Here is a patch to handle spaces ina i386 FP register names. I am
> enclosing a testcase here.
Hello HJ,
As you probably know, we already allow spaces in lots of places. eg.
mov % al , 5 ( % ebp , % ebx , 1 )
Notice that no spaces are allowed *in* a register name, or for that
matter in an instruction mnemonic. eg.
mov $1, % a l
is illegal.
So there is a philosophical question as to whether "st(1)" is really an
indivisible register name token or not. You seem to say that the register
name is "st" with an index, so therefore we should allow spaces, eg.
"st ( 1 )". I'm inclined to say that "st(1)" is really just a name like
any other register name, so spaces shouldn't be allowed (or if we do
allow spaces here then why not in "% a l" - something I don't like).
Where did you run into a need for spaces in fp reg names? C asm macros?
next prev parent reply other threads:[~1999-08-28 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-27 12:18 H.J. Lu
1999-08-28 6:05 ` Alan Modra [this message]
1999-08-28 8:38 ` H.J. Lu
1999-08-29 14:05 ` Ian Lance Taylor
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=Pine.LNX.4.10.9908282145190.31737-100000@mullet.itr.unisa.edu.au \
--to=alan@spri.levels.unisa.edu.au \
--cc=binutils@sourceware.cygnus.com \
--cc=hjl@varesearch.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).