as: Xtensa Syntax

 
 9.54.2 Assembler Syntax
 -----------------------
 
 Block comments are delimited by '/*' and '*/'.  End of line comments may
 be introduced with either '#' or '//'.
 
    If a '#' appears as the first character of a line then the whole line
 is treated as a comment, but in this case the line could also be a
 logical line number directive (SeeComments) or a preprocessor
 control command (SeePreprocessing).
 
    Instructions consist of a leading opcode or macro name followed by
 whitespace and an optional comma-separated list of operands:
 
      OPCODE [OPERAND, ...]
 
    Instructions must be separated by a newline or semicolon (';').
 
    FLIX instructions, which bundle multiple opcodes together in a single
 instruction, are specified by enclosing the bundled opcodes inside
 braces:
 
      {
      [FORMAT]
      OPCODE0 [OPERANDS]
      OPCODE1 [OPERANDS]
      OPCODE2 [OPERANDS]
      ...
      }
 
    The opcodes in a FLIX instruction are listed in the same order as the
 corresponding instruction slots in the TIE format declaration.
 Directives and labels are not allowed inside the braces of a FLIX
 instruction.  A particular TIE format name can optionally be specified
 immediately after the opening brace, but this is usually unnecessary.
 The assembler will automatically search for a format that can encode the
 specified opcodes, so the format name need only be specified in rare
 cases where there is more than one applicable format and where it
 matters which of those formats is used.  A FLIX instruction can also be
 specified on a single line by separating the opcodes with semicolons:
 
      { [FORMAT;] OPCODE0 [OPERANDS]; OPCODE1 [OPERANDS]; OPCODE2 [OPERANDS]; ... }
 
    If an opcode can only be encoded in a FLIX instruction but is not
 specified as part of a FLIX bundle, the assembler will choose the
 smallest format where the opcode can be encoded and will fill unused
 instruction slots with no-ops.
 

Menu