+2001-09-17 graydon hoare <graydon@redhat.com>
+
+ * insn.scm (syntax-break-out): Change $ escape specifier
+ from \$ to $$, to reduce interactions with scheme and C escaping
+ conventions.
+ * doc/rtl.texi (Instructions): Document change.
+
2001-07-12 Jeff Johnston <jjohnstn@redhat.com>
* opc-itab.scm (@arch@_cgen_init_opcode_table): Unconditionally
Fields are denoted by @code{$operand} or
@code{$@{operand@}}@footnote{Support for @code{$@{operand@}} is
work-in-progress.}. If a @samp{$} is required in the syntax, it is
-specified with @samp{\$}. At most one white-space character may be
+specified with @samp{$$}. At most one white-space character may be
present and it must be a blank separating the instruction mnemonic from
the operands. This doesn't restrict the user's assembler, this is
@c Is this reasonable?
(begin
(cond
; Handle escaped syntax metacharacters
- ((char=? #\\ (string-ref syntax 0))
- (set! result (cons (substring syntax 0 1) result))
- (set! result (cons (substring syntax 1 1) result))
+ ((and
+ (char=? #\$ (string-ref syntax 0))
+ (char=? #\$ (string-ref syntax 1)))
+ (set! result (cons "$" result))
(set! syntax (string-drop 2 syntax)))
; Handle operand reference
((char=? #\$ (string-ref syntax 0))