diff options
author | rth <rth@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-10-11 07:07:30 +0000 |
---|---|---|
committer | rth <rth@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-10-11 07:07:30 +0000 |
commit | 2c7f203c73818b36bcf6d49d7c0b429eab5a7ff9 (patch) | |
tree | 65279fa1cd98240f2ba4d2902ef69c88fa458bd8 /gcc/doc/md.texi | |
parent | d0cf8d386017196fb866c5bccab1640e0f9f876d (diff) | |
download | gcc-2c7f203c73818b36bcf6d49d7c0b429eab5a7ff9.tar.gz |
* c-parse.in (asm_operand): Allow named operands.
* genconfig.c (max_recog_operands): Set to 29.
* local-alloc.c (requires_inout): Skip multiple digits.
* recog.c (asm_operand_ok): Likewise.
(preprocess_constraints): Use strtoul for matching constraints.
(constrain_operands): Likewise.
* regmove.c (find_matches): Likewise.
* reload.c (find_reloads): Likewise.
* stmt.c (parse_output_constraint): Don't reject in-out
constraint on operands > 9. Reject '[' in constraint.
(expand_asm_operands): Handle named operands. Use strtoul
for matching constraints.
(check_operand_nalternatives): Split out from expand_asm_operands.
(check_unique_operand_names): New.
(resolve_operand_names, resolve_operand_name_1): New.
* doc/extend.texi (Extended Asm): Document named operands.
* doc/md.texi (Simple Constraints): Document matching constraints
on operands > 9.
* parse.y (asm_operand): Allow named operands.
* semantics.c (finish_asm_stmt): Tweek for changed location
of the operand constrant.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@46179 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/md.texi')
-rw-r--r-- | gcc/doc/md.texi | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi index 685f5150630..7a62eaf25c0 100644 --- a/gcc/doc/md.texi +++ b/gcc/doc/md.texi @@ -894,6 +894,13 @@ An operand that matches the specified operand number is allowed. If a digit is used together with letters within the same alternative, the digit should come last. +This number is allowed to be more than a single digit. If multiple +digits are encountered consecutavely, they are interpreted as a single +decimal integer. There is scant chance for ambiguity, since to-date +it has never been desirable that @samp{10} be interpreted as matching +either operand 1 @emph{or} operand 0. Should this be desired, one +can use multiple alternatives instead. + @cindex matching constraint @cindex constraint, matching This is called a @dfn{matching constraint} and what it really means is |