binutils-gdb/gas/doc/c-visium.texi

91 lines
2.5 KiB
Plaintext
Raw Normal View History

@c Copyright (C) 2014-2019 Free Software Foundation, Inc.
@c This is part of the GAS manual.
@c For copying conditions, see the file as.texinfo.
@c man end
@ifset GENERIC
@page
@node Visium-Dependent
@chapter Visium Dependent Features
@end ifset
@ifclear GENERIC
@node Machine Dependencies
@chapter Visium Dependent Features
@end ifclear
@cindex Visium support
@menu
* Visium Options:: Options
* Visium Syntax:: Syntax
* Visium Opcodes:: Opcodes
@end menu
@node Visium Options
@section Options
@cindex Visium options
@cindex options for Visium
The Visium assembler implements one machine-specific option:
@c man begin OPTIONS
@table @gcctabopt
Fix use of "command line X" in binutils doc Binutils documentation uses a mix of spelling for the compound word "command-line X". According to [1]: "Sometimes compound words are written separately (nail polish), sometimes with a hyphen (short-sighted) and sometimes as one word (eyelashes). Often new compounds are written as two separate words and, as they become more familiar, they are either connected with a hyphen (-) or made into one word." I think command-line X is common enough in our industry that the two workds command and line should be connected. Since command-line is more common than commandline, I propose to update binutils documentation to consistently use "command-line" when this is used as an adjective to a noun (eg. command-line argument, command-line switch, command-line option and command-line flag). I've left occurences of "the command line" as is. I've also left gdb, sim and readline alone and have only touched public documentation (texi and NEWS files). [1] http://dictionary.cambridge.org/grammar/british-grammar/word-formation/compounds 2018-07-02 Thomas Preud'homme <thomas.preudhomme@arm.com> bfd/ * doc/bfdint.texi: Use command-line consistently when used in a compount word. * doc/bfdsumm.texi: Likewise. binutils/ * NEWS: Use command-line consistently when used in a compount word. * doc/binutils.texi: Likewise and fix trailing whitespace on same line. gas/ * NEWS: Use command-line consistently when used in a compount word. * doc/as.texi: Likewise. * doc/c-aarch64.texi: Likewise. * doc/c-alpha.texi: Likewise. * doc/c-arc.texi: Likewise. * doc/c-arm.texi: Likewise. * doc/c-avr.texi: Likewise. * doc/c-bfin.texi: Likewise. * doc/c-cris.texi: Likewise. * doc/c-epiphany.texi: Likewise. * doc/c-i386.texi: Likewise. * doc/c-ia64.texi: Likewise. * doc/c-lm32.texi: Likewise. * doc/c-m32r.texi: Likewise. * doc/c-m68k.texi: Likewise. * doc/c-mips.texi: Likewise. * doc/c-mmix.texi: Likewise. * doc/c-msp430.texi: Likewise. * doc/c-mt.texi: Likewise. * doc/c-nios2.texi: Likewise. * doc/c-ppc.texi: Likewise. * doc/c-pru.texi: Likewise. * doc/c-rl78.texi: Likewise. * doc/c-rx.texi: Likewise. * doc/c-tic6x.texi: Likewise. * doc/c-v850.texi: Likewise. * doc/c-vax.texi: Likewise. * doc/c-visium.texi: Likewise. * doc/c-xstormy16.texi: Likewise. * doc/c-xtensa.texi: Likewise. * doc/c-z80.texi: Likewise. * doc/c-z8k.texi: Likewise. * doc/internals.texi: Likewise. gprof/ * gprof.texi: Use command-line consistently when used in a compount word. ld/ * NEWS: Use command-line consistently when used in a compount word. * ld.texinfo: Likewise. * ldint.texinfo: Likewise.
2018-07-02 12:18:24 +02:00
@cindex @code{-mtune=@var{arch}} command-line option, Visium
@item -mtune=@var{arch}
This option specifies the target architecture. If an attempt is made to
assemble an instruction that will not execute on the target architecture,
the assembler will issue an error message.
The following names are recognized:
@code{mcm24}
@code{mcm}
@code{gr5}
@code{gr6}
@end table
@c man end
@node Visium Syntax
@section Syntax
@menu
* Visium Characters:: Special Characters
* Visium Registers:: Register Names
@end menu
@node Visium Characters
@subsection Special Characters
@cindex line comment character, Visium
@cindex Visium line comment character
Line comments are introduced either by the @samp{!} character or by the
@samp{;} character appearing anywhere on a line.
A hash character (@samp{#}) as the first character on a line also
marks the start of a line comment, but in this case it could also be a
logical line number directive (@pxref{Comments}) or a preprocessor
control command (@pxref{Preprocessing}).
@cindex line separator, Visium
@cindex statement separator, Visium
@cindex Visium line separator
The Visium assembler does not currently support a line separator character.
@node Visium Registers
@subsection Register Names
@cindex Visium registers
@cindex register names, Visium
Registers can be specified either by using their canonical mnemonic names
or by using their alias if they have one, for example @samp{sp}.
@node Visium Opcodes
@section Opcodes
All the standard opcodes of the architecture are implemented, along with the
following three pseudo-instructions: @code{cmp}, @code{cmpc}, @code{move}.
In addition, the following two illegal opcodes are implemented and used by the simulation:
@example
stop 5-bit immediate, SourceA
trace 5-bit immediate, SourceA
@end example