From: Richard Henderson <rth@cygnus.com>
To: law@cygnus.com
Cc: Bruno Haible <haible@ilog.fr>, egcs@cygnus.com, wilson@cygnus.com
Subject: Re: [patch] asms with more than 10 operands
Date: Mon, 06 Apr 1998 17:35:00 -0000 [thread overview]
Message-ID: <19980406114915.55261@dot.cygnus.com> (raw)
In-Reply-To: <7773.891818795@hurl.cygnus.com>
On Sun, Apr 05, 1998 at 05:26:35PM -0600, Jeffrey A Law wrote:
> I wouldn't mind defining it to mean all the digits are part of the
> operand number, specifying a number larger than MAX_OPERANDS is an
> error.
I would prefer to dispense with MAX_OPERANDS entirely. I can think
of no good reason to have one. Aside from new machines with more and
more registers, there have been occasions where I would have liked to
put a couple dozen struct offsets into the assembly with "i" constraints.
> To output a numeric literal after an operand would require
> either an escape or something similar.
You can split the string and use concatination ("%1""2"), just as
is required with the ISO \x sequence.
r~
next prev parent reply other threads:[~1998-04-06 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199803301403.QAA18105@halles.ilog.fr>
1998-04-05 21:29 ` Jeffrey A Law
1998-04-06 17:35 ` Richard Henderson [this message]
1998-04-07 19:34 ` Joern Rennecke
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=19980406114915.55261@dot.cygnus.com \
--to=rth@cygnus.com \
--cc=egcs@cygnus.com \
--cc=haible@ilog.fr \
--cc=law@cygnus.com \
--cc=wilson@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).