CRIS-Pseudos - Using as
Description: Using as

Previous: CRIS-Regs, Up: CRIS-Syntax

##### 9.7.4.4 Assembler Directives

There are a few CRIS-specific pseudo-directives in addition to the generic ones. See Pseudo Ops. Constants emitted by pseudo-directives are in little-endian order for CRIS. There is no support for floating-point-specific directives for CRIS.

`.dword EXPRESSIONS`
  The `.dword` directive is a synonym for `.int`, expecting zero or more EXPRESSIONS, separated by commas. For each expression, a 32-bit little-endian constant is emitted.
`.syntax ARGUMENT`
  The `.syntax` directive takes as ARGUMENT one of the following case-sensitive choices.
  `no_register_prefix`
    The `.syntax no_register_prefix` directive makes a ‘`$`’ character prefix on all registers optional. It overrides a previous setting, including the corresponding effect of the option `--no-underscore`. If this directive is used when ordinary symbols do not have a ‘`_`’ character prefix, care must be taken to avoid ambiguities whether an operand is a register or a symbol; using symbols with names the same as general or special registers then invoke undefined behavior.
  `register_prefix`
    This directive makes a ‘`$`’ character prefix on all registers mandatory. It overrides a previous setting, including the corresponding effect of the option `--underscore`.
  `leading_underscore`
    This is an assertion directive, emitting an error if the `--no-underscore` option is in effect.
  `no_leading_underscore`
    This is the opposite of the `.syntax leading_underscore` directive and emits an error if the option `--underscore` is in effect.
`.arch ARGUMENT`
  This is an assertion directive, giving an error if the specified ARGUMENT is not the same as the specified or default value for the `--march=architecture` option (see march-option).