Directives-i960 - Using as
Description: Using as

Next: Opcodes for i960, Previous: Floating Point-i960, Up: i960-Dependent

#### 9.15.3 i960 Machine Directives

`.bss` symbol`,` length`,` align
  Reserve length bytes in the bss section for a local symbol, aligned to the power of two specified by align. length and align must be positive absolute expressions. This directive differs from ‘`.lcomm`’ only in that it permits you to specify an alignment. See `.lcomm`.

`.extended` flonums
  `.extended` expects zero or more flonums, separated by commas; for each flonum, ‘`.extended`’ emits an ieee extended-format (80-bit) floating-point number.

`.leafproc` call-lab`,` bal-lab
  You can use the ‘`.leafproc`’ directive in conjunction with the optimized `callj` instruction to enable faster calls of leaf procedures. If a procedure is known to call no other procedures, you may define an entry point that skips procedure prolog code (and that does not depend on system-supplied saved context), and declare it as the bal-lab using ‘`.leafproc`’. If the procedure also has an entry point that goes through the normal prolog, you can specify that entry point as call-lab.

  A ‘`.leafproc`’ declaration is meant for use in conjunction with the optimized call instruction ‘`callj`’; the directive records the data needed later to choose between converting the ‘`callj`’ into a `bal` or a `call`.

  call-lab is optional; if only one argument is present, or if the two arguments are identical, the single argument is assumed to be the `bal` entry point.

`.sysproc` name`,` index
  The ‘`.sysproc`’ directive defines a name for a system procedure. After you define it using ‘`.sysproc`’, you can use name to refer to the system procedure identified by index when calling procedures with the optimized call instruction ‘`callj`’.

  Both arguments are required; index must be between 0 and 31 (inclusive).