Next: MSP430 Opcodes, Previous: MSP430 Floating Point, Up: MSP430-Dependent [Contents][Index]

#### 9.29.4 MSP 430 Machine Directives

`.file`

  This directive is ignored; it is accepted for compatibility with other MSP 430 assemblers.

  > Warning: in other versions of the GNU assembler, `.file` is used for the directive called `.app-file` in the MSP 430 support.

`.line`

  This directive is ignored; it is accepted for compatibility with other MSP 430 assemblers.

`.arch`

  Sets the target microcontroller in the same way as the `-mmcu` command-line option.

`.cpu`

  Sets the target architecture in the same way as the `-mcpu` command-line option.

`.profiler`

  This directive instructs assembler to add new profile entry to the object file.

`.refsym`

  This directive instructs assembler to add an undefined reference to the symbol following the directive. The maximum symbol name length is 1023 characters. No relocation is created for this symbol; it will exist purely for pulling in object files from archives. Note that this reloc is not sufficient to prevent garbage collection; use a KEEP() directive in the linker file to preserve such objects.

`.mspabi_attribute`

  This directive tells the assembler what the MSPABI build attributes for this file are. This is used for validating the command line options passed to the assembler against the options the original source file was compiled with. The expected format is: ‘`.mspabi_attribute tag_name, tag_value`’ For example, to set the tag `OFBA_MSPABI_Tag_ISA` to `MSP430X`: ‘`.mspabi_attribute 4, 2`’

  See the MSP430 EABI, document slaa534 for the details on tag names and values.

Next: MSP430 Opcodes, Previous: MSP430 Floating Point, Up: MSP430-Dependent [Contents][Index]