_dnl__ $Id$
\input texinfo @c -*-Texinfo-*-
@c Copyright (c) 1991 1992 Free Software Foundation, Inc.
-@c %**start of header
-@setfilename _AS__.info
+
+@c Set a bunch of variables; this should go into a separate config file
+@c sometime.
+
+@c Which CPU?
+_if__(_I80386__)
+@set cpu-i386
+_fi__(_I80386__)
+_if__(_A29K__)
+@set cpu-a29k
+_fi__(_A29K__)
+_if__(_I960__)
+@set cpu-i960
+_fi__(_I960__)
+_if__(_H8__)
+@set cpu-h8
+_fi__(_H8__)
+_if__(_M680X0__)
+@set cpu-m68k
+_fi__(_M680X0__)
+_if__(_Z8000__)
+@set cpu-z8k
+_fi__(_Z8000__)
+_if__(_SPARC__)
+@set cpu-sparc
+_fi__(_SPARC__)
+_if__(_VAX__)
+@set cpu-vax
+_fi__(_VAX__)
+_if__(_ALL_ARCH__)
+@set cpu-all
+_fi__(_ALL_ARCH__)
+
+@c Which format?
+_if__(_AOUT__)
+@set format-aout
+_fi__(_AOUT__)
+_if__(_BOUT__)
+@set format-bout
+_fi__(_BOUT__)
+_if__(_COFF__)
+@set format-coff
+_fi__(_COFF__)
+_if__(_ELF__)
+@set format-elf
+_fi__(_ELF__)
+
+@c Other miscellaneous parameters.
_if__(_GENERIC__)
-@settitle Using _AS__
+@set generic
_fi__(_GENERIC__)
-_if__(!_GENERIC__)
-@settitle Using _AS__ (_HOST__)
-_fi__(!_GENERIC__)
+_if__(_INTERNALS__)
+@set internals
+_fi__(_INTERNALS__)
+_if__(_DIFFTABKLUG__)
+@set have-diff-table-kludge
+_fi__(_DIFFTABKLUG__)
+_if__(_W32__)
+@set have-word32
+_fi__(_W32__)
+_if__(_W16__)
+@set have-word16
+_fi__(_W16__)
+_if__(_IEEEFLOAT__)
+@set have-ieee-float
+_fi__(_IEEEFLOAT__)
+
+@c Get around lameness in texinfo conditional constructs.
+@set cpu-h8-only
+@ifset generic
+@clear cpu-h8-only
+@end ifset
+@ifclear cpu-h8
+@clear cpu-h8-only
+@end ifclear
+@ifset cpu-all
+@clear cpu-h8-only
+@end ifset
+
+@ifset generic
+@set generic-or-m68k
+@end ifset
+@ifset cpu-m68k
+@set generic-or-m68k
+@end ifset
+
+@c Some string definitions.
+@set as _AS__
+@set gcc _GCC__
+@set ld _LD__
+@set gdb-name _GDBN__
+@set gdb-prog _GDBP__
+@set gdb-init _GDBINIT__
+
+@set host _HOST__
+@set mach-dep _MACH_DEP__
+
+
+@c %**start of header
+@setfilename @value{as}.info
+@ifset generic
+@settitle Using @value{as}
+@end ifset
+@ifclear generic
+@settitle Using @value{as} (@value{host})
+@end ifclear
@setchapternewpage odd
@c @smallbook
@c @cropmarks
_fi__(0)
@c
@ifinfo
-This file documents the GNU Assembler "_AS__".
+This file documents the GNU Assembler "@value{as}".
Copyright (C) 1991, 1992 Free Software Foundation, Inc.
@end ifinfo
@titlepage
-@title Using _AS__
+@title Using @value{as}
@subtitle The GNU Assembler
-_if__(!_GENERIC__)
+@ifclear generic
@subtitle for the _HOST__ family
-_fi__(!_GENERIC__)
+@end ifclear
@sp 1
@subtitle November 1992
@sp 1
\def\$#1${{#1}} % Kluge: collect RCS revision info without $...$
\xdef\manvers{\$Revision$} % For use in headers, footers too
{\parskip=0pt
-\hfill {\it Using {\tt _AS__}} \manvers\par
+\hfill {\it Using {\tt @value{as}}} \manvers\par
\hfill \TeX{}info \texinfoversion\par
\hfill Edited by Roland Pesch for Cygnus Support\par
}
@end tex
@vskip 0pt plus 1filll
-Copyright @copyright{} 1991, 1992 Free Software Foundation, Inc.
+Copyright @copyright{} 1991, 1992, 1993 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
@page
@ifinfo
@node Top
-@top Using _AS__
+@top Using @value{as}
-This file is a user guide to the GNU assembler @code{_AS__}.
-_if__(!_GENERIC__)
-This version of the file describes @code{_AS__} configured to generate
-code for _HOST__ architectures.
-_fi__(!_GENERIC__)
+This file is a user guide to the GNU assembler @code{@value{as}}.
+@ifclear generic
+This version of the file describes @code{@value{as}} configured to generate
+code for @value{host} architectures.
+@end ifclear
@menu
* Overview:: Overview
* Invoking:: Command-Line Options
@node Overview
@chapter Overview
@iftex
-This manual is a user guide to the GNU assembler @code{_AS__}.
-_if__(!_GENERIC__)
-This version of the manual describes @code{_AS__} configured to generate
-code for _HOST__ architectures.
-_fi__(!_GENERIC__)
+This manual is a user guide to the GNU assembler @code{@value{as}}.
+@ifclear generic
+This version of the manual describes @code{@value{as}} configured to generate
+code for @value{host} architectures.
+@end ifclear
@end iftex
@cindex invocation summary
@cindex option summary
@cindex summary of options
-Here is a brief summary of how to invoke @code{_AS__}. For details,
+Here is a brief summary of how to invoke @code{@value{as}}. For details,
@pxref{Invoking,,Comand-Line Options}.
@c We don't use deffn and friends for the following because they seem
@c to be limited to one line for the header.
@smallexample
- _AS__ [ -a | -al | -as ] [ -D ] [ -f ]
+ @value{as} [ -a | -al | -as ] [ -D ] [ -f ]
[ -I @var{path} ] [ -K ] [ -L ]
[ -o @var{objfile} ] [ -R ] [ -v ] [ -w ]
-_if__(_A29K__)
-@c am29k has no machine-dependent assembler options
-_fi__(_A29K__)
-_if__(_H8__)
-@c h8/300 has no machine-dependent assembler options
-_fi__(_H8__)
-_if__(_Z8000__)
-@c Z8000 has no machine-dependent assembler options
-_fi__(_Z8000__)
-_if__(_I960__)
+@c am29k, h8, z8k have no machine-dependent assembler options
+@ifset cpu-i960
@c see md_parse_option in tc-i960.c
[ -ACA | -ACA_A | -ACB | -ACC | -AKA | -AKB | -AKC | -AMC ]
[ -b ] [ -norelax ]
-_fi__(_I960__)
-_if__(_M680X0__)
+@end ifset
+@ifset cpu-m68k
[ -l ] [ -mc68000 | -mc68010 | -mc68020 ]
-_fi__(_M680X0__)
+@end ifset
[ -- | @var{files} @dots{} ]
@end smallexample
@table @code
-@item -a | -al | -as
-Turn on assembly listings; @samp{-al}, listing only, @samp{-as}, symbols
-only, @samp{-a}, everything.
+@item -a[dhlns]
+Turn on listings;
+@samp{-ad}, omit debugging pseudo-ops from listing,
+@samp{-ah}, include high-level source,
+@samp{-al}, assembly listing,
+@samp{-an}, no forms processing,
+@samp{-as}, symbols. These options may be combined; @emph{e.g.},
+@samp{-aln} for assembly listing without forms processing.
+By itself, @samp{-a} defaults to @samp{-ahls} --- that is, all listings
+turned on.
@item -D
This option is accepted only for script compatibility with calls to
-other assemblers; it has no effect on @code{_AS__}.
+other assemblers; it has no effect on @code{@value{as}}.
@item -f
``fast''---skip preprocessing (assume source is compiler output)
@item -K
_if__((!_GENERIC__) && !_DIFFTABKLUG__)
-This option is accepted but has no effect on the _HOST__ family.
+This option is accepted but has no effect on the @value{host} family.
_fi__((!_GENERIC__) && !_DIFFTABKLUG__)
_if__(_GENERIC__ || _DIFFTABKLUG__)
Issue warnings when difference tables altered for long displacements.
Keep (in symbol table) local symbols, starting with @samp{L}
@item -o @var{objfile}
-Name the object-file output from @code{_AS__}
+Name the object-file output from @code{@value{as}}
@item -R
Fold data section into text section
@item -- | @var{files} @dots{}
Standard input, or source files to assemble.
-@end table
@end table
-_if__(_I960__)
-The following options are available when _AS__ is configured for the
+@ifset cpu-i960
+The following options are available when @value{as} is configured for the
Intel 80960 processor.
@table @code
error if necessary.
@end table
-_fi__(_I960__)
+@end ifset
-_if__(_M680X0__)
-The following options are available when _AS__ is configured for the
+@ifset cpu-m68k
+The following options are available when @value{as} is configured for the
Motorola 68000 series.
@table @code
unit coprocessor. The default is to assume an MMU for 68020 and up.
@end table
-_fi__(_M680X0__)
+@end ifset
@menu
* Manual:: Structure of this Manual
-* GNU Assembler:: _AS__, the GNU Assembler
+* GNU Assembler:: @value{as}, the GNU Assembler
* Object Formats:: Object File Formats
* Command Line:: Command Line
* Input Files:: Input Files
@cindex manual, structure and purpose
This manual is intended to describe what you need to know to use
-@sc{gnu} @code{_AS__}. We cover the syntax expected in source files, including
+@sc{gnu} @code{@value{as}}. We cover the syntax expected in source files, including
notation for symbols, constants, and expressions; the directives that
-@code{_AS__} understands; and of course how to invoke @code{_AS__}.
+@code{@value{as}} understands; and of course how to invoke @code{@value{as}}.
-_if__(!_GENERIC__)
-We also cover special features in the _HOST__
-configuration of @code{_AS__}, including assembler directives.
-_fi__(!_GENERIC__)
-_if__(_GENERIC__)
+@ifclear generic
+We also cover special features in the @value{host}
+configuration of @code{@value{as}}, including assembler directives.
+@end ifclear
+@ifset generic
This manual also describes some of the machine-dependent features of
various flavors of the assembler.
-_fi__(_GENERIC__)
-_if__(_INTERNALS__)
+@end ifset
+@ifset internals
This manual also describes how the assembler works internally, and
provides some information that may be useful to people attempting to
port the assembler to another machine.
-_fi__(_INTERNALS__)
+@end ifset
@refill
@cindex machine instructions (not covered)
architecture; we do @emph{not} describe the instruction set, standard
mnemonics, registers or addressing modes that are standard to a
particular architecture.
-_if__(_GENERIC__)
+@ifset generic
You may want to consult the manufacturer's
machine architecture manual for this information.
-_fi__(_GENERIC__)
-_if__(_H8__&&!_GENERIC__)
+@end ifset
+@ifclear generic
+@ifset cpu-h8
For information on the H8/300 machine instruction set, see @cite{H8/300
Series Programming Manual} (Hitachi ADE--602--025).
-_fi__(_H8__&&!_GENERIC__)
-_if__(_Z8000__&&!_GENERIC__)
-For information on the Z8000 machine instruction set, see @cite{Z8000 CPU Technical Manual}
-_fi__(_Z8000__&&!_GENERIC__)
+@end ifset
+@ifset cpu-z8k
+For information on the Z8000 machine instruction set, see @cite{Z8000
+CPU Technical Manual}.
+@end ifset
+@end ifclear
@c I think this is premature---pesch@cygnus.com, 17jan1991
once this assumption is granted examples and definitions need less
qualification.
-@code{_AS__} is part of a team of programs that turn a high-level
+@code{@value{as}} is part of a team of programs that turn a high-level
human-readable series of instructions into a low-level
computer-readable series of instructions. Different versions of
-@code{_AS__} are used for different kinds of computer.
+@code{@value{as}} are used for different kinds of computer.
@end ignore
@c There used to be a section "Terminology" here, which defined
@c directives).
@node GNU Assembler
-@section _AS__, the GNU Assembler
+@section @value{as}, the GNU Assembler
GNU @code{as} is really a family of assemblers.
-_if__(!_GENERIC__)
-This manual describes @code{_AS__}, a member of that family which is
-configured for the _HOST__ architectures.
-_fi__(!_GENERIC__)
+@ifclear generic
+This manual describes @code{@value{as}}, a member of that family which is
+configured for the @value{host} architectures.
+@end ifclear
If you use (or have used) the GNU assembler on one architecture, you
should find a fairly similar environment when you use it on another
architecture. Each version has much in common with the others,
including object file formats, most assembler directives (often called
@dfn{pseudo-ops}) and assembler syntax.@refill
-_if__(_GENERIC__||!_H8__)
-@cindex purpose of @sc{gnu} @code{_AS__}
-@code{_AS__} is primarily intended to assemble the output of the GNU C
+@ifclear cpu-h8-only
+@cindex purpose of @sc{gnu} @code{@value{as}}
+@code{@value{as}} is primarily intended to assemble the output of the GNU C
compiler @code{_GCC__} for use by the linker @code{_LD__}. Nevertheless,
-we've tried to make @code{_AS__} assemble correctly everything that the native
+we've tried to make @code{@value{as}} assemble correctly everything that
+the native
assembler would.
-_fi__(_GENERIC__||!_H8__)
-_if__(_VAX__)
+@end ifclear
+@ifset cpu-vax
Any exceptions are documented explicitly (@pxref{_MACH_DEP__}).
-_fi__(_VAX__)
-_if__(_GENERIC__||_M680X0__)
-This doesn't mean @code{_AS__} always uses the same syntax as another
+@end ifset
+@ifset generic-or-m68k
+This doesn't mean @code{@value{as}} always uses the same syntax as another
assembler for the same architecture; for example, we know of several
incompatible versions of 680x0 assembly language syntax.
-_fi__(_GENERIC__||_M680X0__)
+@end ifset
-Unlike older assemblers, @code{_AS__} is designed to assemble a source
+Unlike older assemblers, @code{@value{as}} is designed to assemble a source
program in one pass of the source file. This has a subtle impact on the
@kbd{.org} directive (@pxref{Org,,@code{.org}}).
write assembly language programs; but directives for debugging symbols
are typically different in different file formats. @xref{Symbol
Attributes,,Symbol Attributes}.
-_if__(!_GENERIC__)
+@ifclear generic
_if__(!(_I960__||_A29K__))
_if__(_AOUT__ && (!_COFF__) && (!_ELF__))
-On the _HOST__, @code{_AS__} is configured to produce @code{a.out}
+On the @value{host}, @code{@value{as}} is configured to produce @code{a.out}
format object
files.@refill
_fi__(_AOUT__ && (!_COFF__) && (!_ELF__))
_if__((!_AOUT__) && _COFF__ && (!_ELF__))
-On the _HOST__, @code{_AS__} is configured to produce COFF format object
+On the @value{host}, @code{@value{as}} is configured to produce COFF format object
files.@refill
_fi__((!_AOUT__) && _COFF__ && (!_ELF__))
_fi__(!(_I960__||_A29K__))
_if__(_A29K__)
-On the _HOST__, @code{_AS__} can be configured to produce either
+On the @value{host}, @code{@value{as}} can be configured to produce either
@code{a.out} or COFF format object files.
_fi__(_A29K__)
-_if__(_I960__)
-On the _HOST__, @code{_AS__} can be configured to produce either
+@ifset cpu-i960
+On the @value{host}, @code{@value{as}} can be configured to produce either
@code{b.out} or COFF
format object files.
-_fi__(_I960__)
-_fi__(!_GENERIC__)
+@end ifset
+@end ifclear
@node Command Line
@section Command Line
@cindex command line conventions
-After the program name @code{_AS__}, the command line may contain
+After the program name @code{@value{as}}, the command line may contain
options and file names. Options may appear in any order, and may be
before, after, or between file names. The order of file names is
significant.
@cindex standard input, as input file
@kindex --
@file{--} (two hyphens) by itself names the standard input file
-explicitly, as one of the files for @code{_AS__} to assemble.
+explicitly, as one of the files for @code{@value{as}} to assemble.
@cindex options, command line
Except for @samp{--} any command line argument that begins with a
hyphen (@samp{-}) is an option. Each option changes the behavior of
-@code{_AS__}. No option changes the way another option works. An
+@code{@value{as}}. No option changes the way another option works. An
option is a @samp{-} followed by one or more letters; the case of
the letter is important. All options are optional.
standard). These two command lines are equivalent:
@smallexample
-_AS__ -o my-object-file.o mumble.s
-_AS__ -omy-object-file.o mumble.s
+@value{as} -o my-object-file.o mumble.s
+@value{as} -omy-object-file.o mumble.s
@end smallexample
@node Input Files
@cindex source program
@cindex files, input
We use the phrase @dfn{source program}, abbreviated @dfn{source}, to
-describe the program input to one run of @code{_AS__}. The program may
+describe the program input to one run of @code{@value{as}}. The program may
be in one or more files; how the source is partitioned into files
doesn't change the meaning of the source.
The source program is a concatenation of the text in all the files, in the
order specified.
-Each time you run @code{_AS__} it assembles exactly one source
+Each time you run @code{@value{as}} it assembles exactly one source
program. The source program is made up of one or more files.
(The standard input is also a file.)
-You give @code{_AS__} a command line that has zero or more input file
+You give @code{@value{as}} a command line that has zero or more input file
names. The input files are read (from left file name to right). A
command line argument (in any position) that has no special meaning
is taken to be an input file name.
-If you give @code{_AS__} no file names it attempts to read one input file
-from the @code{_AS__} standard input, which is normally your terminal. You
-may have to type @key{ctl-D} to tell @code{_AS__} there is no more program
+If you give @code{@value{as}} no file names it attempts to read one input file
+from the @code{@value{as}} standard input, which is normally your terminal. You
+may have to type @key{ctl-D} to tell @code{@value{as}} there is no more program
to assemble.
Use @samp{--} if you need to explicitly name the standard input file
in your command line.
-If the source is empty, @code{_AS__} will produce a small, empty object
+If the source is empty, @code{@value{as}} will produce a small, empty object
file.
@subheading Filenames and Line-numbers
``logical'' file. @xref{Errors, ,Error and Warning Messages}.
@dfn{Physical files} are those files named in the command line given
-to @code{_AS__}.
+to @code{@value{as}}.
@dfn{Logical files} are simply names declared explicitly by assembler
directives; they bear no relation to physical files. Logical file names
-help error messages reflect the original source file, when @code{_AS__}
+help error messages reflect the original source file, when @code{@value{as}}
source is itself synthesized from other files.
-@xref{App-File,,@code{.app-file}}.
+@xref{Appfile,,@code{.appfile}}.
@node Object
@section Output (Object) File
@cindex output file
@kindex a.out
@kindex .o
-Every time you run @code{_AS__} it produces an output file, which is
+Every time you run @code{@value{as}} it produces an output file, which is
your assembly language program translated into numbers. This file
is the object file, named
_if__(_BOUT__)
@code{b.out},
-_if__(_GENERIC__)
-if @code{_AS__} is configured for the Intel 80960, or
-_fi__(_GENERIC__)
+@ifset generic
+if @code{@value{as}} is configured for the Intel 80960, or
+@end ifset
_fi__(_BOUT__)
_if__(!_BOUT__)
@code{a.out},
_fi__(!_BOUT__)
-unless you tell @code{_AS__} to
+unless you tell @code{@value{as}} to
give it another name by using the @code{-o} option. Conventionally,
object file names end with @file{.o}. The default name of
@file{a.out} is used for historical reasons: older assemblers were
@cindex error messsages
@cindex warning messages
-@cindex messages from @code{_AS__}
-@code{_AS__} may write warnings and error messages to the standard error
+@cindex messages from @code{@value{as}}
+@code{@value{as}} may write warnings and error messages to the standard error
file (usually your terminal). This should not happen when a compiler
-runs @code{_AS__} automatically. Warnings report an assumption made so
-that @code{_AS__} could keep assembling a flawed program; errors report a
+runs @code{@value{as}} automatically. Warnings report an assumption made so
+that @code{@value{as}} could keep assembling a flawed program; errors report a
grave problem that stops the assembly.
@cindex format of warning messages
@noindent
@cindex line numbers, in warnings/errors
(where @b{NNN} is a line number). If a logical file name has
-been given (@pxref{App-File,,@code{.app-file}}) it is used for the
+been given (@pxref{Appfile,,@code{.appfile}}) it is used for the
filename, otherwise the
name of the current input file is used. If a logical line number was
given
@node Invoking
@chapter Command-Line Options
-@cindex options, all versions of @code{_AS__}
+@cindex options, all versions of @code{@value{as}}
This chapter describes command-line options available in @emph{all}
versions of the GNU assembler; @pxref{_MACH_DEP__}, for options specific
-_if__(!_GENERIC__)
-to the _HOST__.
-_fi__(!_GENERIC__)
-_if__(_GENERIC__)
+@ifclear generic
+to the @value{host}.
+@end ifclear
+@ifset generic
to particular machine architectures.
-_fi__(_GENERIC__)
+@end ifset
+
+If you are invoking @code{@value{as}} via the GNU C compiler (version 2), you
+can use the @samp{-Wa} option to pass arguments through to the
+assembler. The assembler arguments must be separated from each other
+(and the @samp{-Wa}) by commas. For example:
+
+@smallexample
+gcc -c -g -O -Wa,-alh,-L file.c
+@end smallexample
+
+will cause a listing to be emitted to standard output with high-level
+and assembly source.
+
+Many compiler command-line options, such as @samp{-R} and many
+machine-specific options, will be automatically be passed to the
+assembler by the compiler, so usually you do not need to use this
+@samp{-Wa} mechanism.
-@section Enable Listings: @code{-a}, @code{-al}, @code{-as}
+@section Enable Listings: @code{-a[dhlns]}
@kindex -a
+@kindex -ad
+@kindex -ah
@kindex -al
+@kindex -an
@kindex -as
@cindex listings, enabling
@cindex assembly listings, enabling
-These options enable listing output from the assembler. @samp{-a} by
-itself requests all listing output; @samp{-al} requests only the
-output-program listing, and @samp{-as} requests only a symbol table
-listing.
+
+These options enable listing output from the assembler. By itself,
+@samp{-a} requests high-level, assembly, and symbols listing.
+Other letters may be used to select specific options for the list:
+@samp{-ah} requests a high-level language listing,
+@samp{-al} requests an output-program assembly listing, and
+@samp{-as} requests a symbol table listing.
+High-level listings require that a compiler debugging option like
+@samp{-g} be used, and that assembly listings (@samp{-al}) be requested
+also.
+
+The @samp{-ad} option may be used to omit debugging pseudo-ops from the
+listing.
Once you have specified one of these options, you can further control
listing output and its appearance using the directives @code{.list},
@code{.nolist}, @code{.psize}, @code{.eject}, @code{.title}, and
@code{.sbttl}.
-
+The @samp{-an} option turns off all forms processing.
If you do not request listing output with one of the @samp{-a} options, the
listing-control directives have no effect.
+The letters after @samp{-a} may be combined into one option,
+@emph{e.g.}, @samp{-aln}.
+
@section @code{-D}
@kindex -D
This option has no effect whatsoever, but it is accepted to make it more
likely that scripts written for other assemblers will also work with
-@code{_AS__}.
+@code{@value{as}}.
@section Work Faster: @code{-f}
@quotation
@emph{Warning:} if the files actually need to be pre-processed (if they
-contain comments, for example), @code{_AS__} will not work correctly if
+contain comments, for example), @code{@value{as}} will not work correctly if
@samp{-f} is used.
@end quotation
@cindex search path for @code{.include}
@cindex @code{include} directive search path
Use this option to add a @var{path} to the list of directories
-@code{_AS__} will search for files specified in @code{.include}
+@code{@value{as}} will search for files specified in @code{.include}
directives (@pxref{Include,,@code{.include}}). You may use @code{-I} as
many times as necessary to include a variety of paths. The current
-working directory is always searched first; after that, @code{_AS__}
+working directory is always searched first; after that, @code{@value{as}}
searches any @samp{-I} directories in the same order as they were
specified (left to right) on the command line.
@kindex -K
_if__((!_GENERIC__) && (!_DIFFTABKLUG__))
-On the _HOST__ family, this option is allowed, but has no effect. It is
+On the @value{host} family, this option is allowed, but has no effect. It is
permitted for compatibility with the GNU assembler on other platforms,
where it can be used to warn when the assembler alters the machine code
-generated for @samp{.word} directives in difference tables. The _HOST__
+generated for @samp{.word} directives in difference tables. The @value{host}
family does not have the addressing limitations that sometimes lead to this
alteration on other platforms.
_fi__((!_GENERIC__) && (!_DIFFTABKLUG__))
_if__(_GENERIC__ || _DIFFTABKLUG__ )
@cindex difference tables, warning
@cindex warning for altered difference tables
-@code{_AS__} sometimes alters the code emitted for directives of the form
+@code{@value{as}} sometimes alters the code emitted for directives of the form
@samp{.word @var{sym1}-@var{sym2}}; @pxref{Word,,@code{.word}}.
You can use the @samp{-K} option if you want a warning issued when this
is done.
labels}. @xref{Symbol Names}. Normally you don't see such labels when
debugging, because they are intended for the use of programs (like
compilers) that compose assembler programs, not for your notice.
-Normally both @code{_AS__} and @code{_LD__} discard such labels, so you don't
+Normally both @code{@value{as}} and @code{_LD__} discard such labels, so you don't
normally debug with them.
-This option tells @code{_AS__} to retain those @samp{L@dots{}} symbols
+This option tells @code{@value{as}} to retain those @samp{L@dots{}} symbols
in the object file. Usually if you do this you also tell the linker
@code{_LD__} to preserve symbols whose names begin with @samp{L}.
@kindex -o
@cindex naming object file
@cindex object file name
-There is always one object file output when you run @code{_AS__}. By
+There is always one object file output when you run @code{@value{as}}. By
default it has the name
-_if__(_GENERIC__)
-_if__(_I960__)
+@ifset generic
+@ifset cpu-i960
@file{a.out} or @file{b.out}, depending on the target for which
-@code{_AS__} is configured.
-_fi__(_I960__)
+@code{@value{as}} is configured.
+@end ifset
_if__(!_I960__)
@file{a.out}.
_fi__(!_I960__)
-_fi__(_GENERIC__)
-_if__(!_GENERIC__)
-_if__(_I960__)
+@end ifset
+@ifclear generic
+@ifset cpu-i960
@file{b.out}.
-_fi__(_I960__)
+@end ifset
_if__(!_I960__)
@file{a.out}.
_fi__(!_I960__)
-_fi__(!_GENERIC__)
+@end ifclear
You use this option (which
takes exactly one filename) to give the object file a different name.
-Whatever the object file is called, @code{_AS__} will overwrite any
+Whatever the object file is called, @code{@value{as}} will overwrite any
existing file of the same name.
@section Join Data and Text Sections: @code{-R}
@cindex text and data sections, joining
@cindex joining text and data sections
@cindex merging text and data sections
-@code{-R} tells @code{_AS__} to write the object file as if all
+@code{-R} tells @code{@value{as}} to write the object file as if all
data-section data lives in the text section. This is only done at
the very last moment: your binary data are the same, but data
section parts are relocated differently. The data section part of
When you specify @code{-R} it would be possible to generate shorter
address displacements (because we don't have to cross between text and
data section). We refrain from doing this simply for compatibility with
-older versions of @code{_AS__}. In future, @code{-R} may work this way.
+older versions of @code{@value{as}}. In future, @code{-R} may work this way.
_if__(_COFF__)
-When @code{_AS__} is configured for COFF output,
+When @code{@value{as}} is configured for COFF output,
this option is only useful if you use sections named @samp{.text} and
@samp{.data}.
_fi__(_COFF__)
@kindex -v
@kindex -version
-@cindex @code{_AS__} version
-@cindex version of @code{_AS__}
+@cindex @code{@value{as}} version
+@cindex version of @code{@value{as}}
You can find out what version of as is running by including the
option @samp{-v} (which you can also spell as @samp{-version}) on the
command line.
@kindex -W
@cindex suppressing warnings
@cindex warnings, suppressing
-@code{_AS__} should never give a warning or error message when
+@code{@value{as}} should never give a warning or error message when
assembling compiler output. But programs written by people often
-cause @code{_AS__} to give a warning that a particular assumption was
+cause @code{@value{as}} to give a warning that a particular assumption was
made. All such warnings are directed to the standard error file.
If you use this option, no warnings are issued. This option only
affects the warning messages: it does not change any particular of how
-@code{_AS__} assembles your file. Errors, which stop the assembly, are
+@code{@value{as}} assembles your file. Errors, which stop the assembly, are
still reported.
@node Syntax
@cindex machine-independent syntax
@cindex syntax, machine-independent
This chapter describes the machine-independent syntax allowed in a
-source file. @code{_AS__} syntax is similar to what many other assemblers
+source file. @code{@value{as}} syntax is similar to what many other assemblers
use; it is inspired by the BSD 4.2
_if__(!_VAX__)
assembler. @refill
_fi__(!_VAX__)
_if__(_VAX__)
-assembler, except that @code{_AS__} does not assemble Vax bit-fields.
+assembler, except that @code{@value{as}} does not assemble Vax bit-fields.
_fi__(_VAX__)
@menu
@section Comments
@cindex comments
-There are two ways of rendering comments to @code{_AS__}. In both
+There are two ways of rendering comments to @code{@value{as}}. In both
cases the comment is equivalent to one space.
Anything from @samp{/*} through the next @samp{*/} is a comment.
_if__(_VAX__)
@samp{#} on the Vax;
_fi__(_VAX__)
-_if__(_I960__)
+@ifset cpu-i960
@samp{#} on the i960;
-_fi__(_I960__)
+@end ifset
_if__(_SPARC__)
@samp{!} on the SPARC;
_fi__(_SPARC__)
-_if__(_M680X0__)
+@ifset cpu-m68k
@samp{|} on the 680x0;
-_fi__(_M680X0__)
+@end ifset
_if__(_A29K__)
@samp{;} for the AMD 29K family;
_fi__(_A29K__)
see @ref{_MACH_DEP__}. @refill
@c FIXME What about i386, m88k, i860?
-_if__(_GENERIC__)
+@ifset generic
On some machines there are two different line comment characters. One
will only begin a comment if it is the first non-whitespace character on
a line, while the other will always begin a comment.
-_fi__(_GENERIC__)
+@end ifset
@kindex #
@cindex lines starting with @code{#}
# This is logical line # 36.
@end smallexample
This feature is deprecated, and may disappear from future versions
-of @code{_AS__}.
+of @code{@value{as}}.
@node Symbol Intro
@section Symbols
_fi__(!_H8__)
_if__(_H8__)
the two characters @samp{_.}
-_if__(_GENERIC__)
+@ifset generic
On most machines, you can also use @code{$} in symbol names; exceptions
are noted in @ref{_MACH_DEP__}.
-_fi__(_GENERIC__)
+@end ifset
_fi__(_H8__)
No symbol may begin with a digit. Case is significant.
There is no length limit: all characters are significant. Symbols are
@cindex statements, structure of
@cindex line separator character
@cindex statement separator character
-_if__(!_GENERIC__)
+@ifclear generic
_if__(!(_A29K__||_H8__))
A @dfn{statement} ends at a newline character (@samp{\n}) or at a
semicolon (@samp{;}). The newline or semicolon is considered part of
preceding statement. Newlines and dollar signs within character constants
are an exception: they don't end statements.
_fi__(_H8__)
-_fi__(!_GENERIC__)
-_if__(_GENERIC__)
+@end ifclear
+@ifset generic
A @dfn{statement} ends at a newline character (@samp{\n}) or line
separator character. (The line separator is usually @samp{;}, unless
this conflicts with the comment character; @pxref{_MACH_DEP__}.) The
newline or separator character is considered part of the preceding
statement. Newlines and separators within character constants are an
exception: they don't end statements.
-_fi__(_GENERIC__)
+@end ifset
@cindex newline, required at file end
@cindex EOF, newline must precede
@cindex statement on multiple lines
You may write a statement on more than one line if you put a
backslash (@kbd{\}) immediately in front of any newlines within the
-statement. When @code{_AS__} reads a backslashed newline both
+statement. When @code{@value{as}} reads a backslashed newline both
characters are ignored. You can even put backslashed newlines in
the middle of symbol names without changing the meaning of your
source program.
directive: typically valid for any computer. If the symbol begins with
a letter the statement is an assembly language @dfn{instruction}: it
will assemble into a machine language instruction.
-_if__(_GENERIC__)
-Different versions of @code{_AS__} for different computers will
+@ifset generic
+Different versions of @code{@value{as}} for different computers will
recognize different instructions. In fact, the same symbol may
represent a different instruction in a different computer's assembly
language.@refill
-_fi__(_GENERIC__)
+@end ifset
@cindex @code{:} (label)
@cindex label (@code{:})
into a string is to @dfn{escape} these characters: precede them with
a backslash @samp{\} character. For example @samp{\\} represents
one backslash: the first @code{\} is an escape which tells
-@code{_AS__} to interpret the second character literally as a backslash
-(which prevents @code{_AS__} from recognizing the second @code{\} as an
+@code{@value{as}} to interpret the second character literally as a backslash
+(which prevents @code{@value{as}} from recognizing the second @code{\} as an
escape character). The complete list of escapes follows.
@cindex escape codes, character
Any other character when escaped by @kbd{\} will give a warning, but
assemble as if the @samp{\} was not present. The idea is that if
you used an escape sequence you clearly didn't want the literal
-interpretation of the following character. However @code{_AS__} has no
-other interpretation, so @code{_AS__} knows it is giving you the wrong
+interpretation of the following character. However @code{@value{as}} has no
+other interpretation, so @code{@value{as}} knows it is giving you the wrong
code and warns you of the fact.
@end table
must write @kbd{'\\} where the first @code{\} escapes the second
@code{\}. As you can see, the quote is an acute accent, not a
grave accent. A newline
-_if__(!_GENERIC__)
+@ifclear generic
_if__(!(_A29K__||_H8__))
(or semicolon @samp{;})
_fi__(!(_A29K__||_H8__))
_if__(_H8__)
(or dollar sign @samp{$})
_fi__(_H8__)
-_fi__(!_GENERIC__)
+@end ifclear
immediately following an acute accent is taken as a literal character
and does not count as the end of a statement. The value of a character
constant in a numeric expression is the machine's byte-wide code for
-that character. @code{_AS__} assumes your character code is ASCII:
+that character. @code{@value{as}} assumes your character code is ASCII:
@kbd{'A} means 65, @kbd{'B} means 66, and so on. @refill
@node Numbers
@cindex constants, number
@cindex number constants
-@code{_AS__} distinguishes three kinds of numbers according to how they
+@code{@value{as}} distinguishes three kinds of numbers according to how they
are stored in the target machine. @emph{Integers} are numbers that
would fit into an @code{int} in the C language. @emph{Bignums} are
integers, but they are stored in more than 32 bits. @emph{Flonums}
@cindex precision, floating point
A @dfn{flonum} represents a floating point number. The translation is
indirect: a decimal floating point number from the text is converted by
-@code{_AS__} to a generic binary floating point number of more than
+@code{@value{as}} to a generic binary floating point number of more than
sufficient precision. This generic floating point number is converted
to a particular computer's floating point format (or formats) by a
-portion of @code{_AS__} specialized to that computer.
+portion of @code{@value{as}} specialized to that computer.
A flonum is written by writing (in order)
@itemize @bullet
@item
The digit @samp{0}.
@item
-A letter, to tell @code{_AS__} the rest of the number is a flonum.
-_if__(_GENERIC__)
+A letter, to tell @code{@value{as}} the rest of the number is a flonum.
+@ifset generic
@kbd{e} is recommended. Case is not important.
@ignore
@c FIXME: verify if flonum syntax really this vague for most cases
will work here, but that might be changed. Vax BSD 4.2 assembler seems
to allow any of @samp{defghDEFGH}.)
@end ignore
-_fi__(_GENERIC__)
+@end ifset
_if__(_A29K__||_H8__)
-_if__(_GENERIC__)
+@ifset generic
On the AMD 29K and H8/300 architectures, the letter must be:
-_fi__(_GENERIC__)
+@end ifset
One of the letters @samp{DFPRSX} (in upper or lower case).
_fi__(_A29K__||_H8__)
-_if__(_I960__)
-_if__(_GENERIC__)
+@ifset cpu-i960
+@ifset generic
On the Intel 960 architecture, the letter must be:
-_fi__(_GENERIC__)
+@end ifset
One of the letters @samp{DFT} (in upper or lower case).
-_fi__(_I960__)
+@end ifset
@item
An optional sign: either @samp{+} or @samp{-}.
@item
At least one of the integer part or the fractional part must be
present. The floating point number has the usual base-10 value.
-@code{_AS__} does all processing using integers. Flonums are computed
+@code{@value{as}} does all processing using integers. Flonums are computed
independently of any floating point hardware in the computer running
-@code{_AS__}.
+@code{@value{as}}.
_if__(_I960__&&!_GENERIC__)
@c Bit fields are written as a general facility but are also controlled
@var{mask}:@var{value}
@end example
@noindent
-the first will act as a mask; @code{_AS__} will bitwise-and it with the
+the first will act as a mask; @code{@value{as}} will bitwise-and it with the
second value.
The resulting number is then packed
-_if__(_GENERIC__)
+@ifset generic
@c this conditional paren in case bit fields turned on elsewhere than 960
(in host-dependent byte order)
-_fi__(_GENERIC__)
+@end ifset
into a field whose width depends on which assembler directive has the
bit-field as its argument. Overflow (a result from the bitwise and
requiring more binary digits to represent) is not an error; instead,
@menu
* Secs Background:: Background
* _LD__ Sections:: _LD__ Sections
-* _AS__ Sections:: _AS__ Internal Sections
+* @value{as} Sections:: @value{as} Internal Sections
* Sub-Sections:: Sub-Sections
* bss:: bss Section
@end menu
@cindex linker, and assembler
@cindex assembler, and linker
The linker @code{_LD__} reads many object files (partial programs) and
-combines their contents to form a runnable program. When @code{_AS__}
+combines their contents to form a runnable program. When @code{@value{as}}
emits an object file, the partial program is assumed to start at address
0. @code{_LD__} will assign the final addresses the partial program
occupies, so that different partial programs don't overlap. This is
actually an over-simplification, but it will suffice to explain how
-@code{_AS__} uses sections.
+@code{@value{as}} uses sections.
@code{_LD__} moves blocks of bytes of your program to their run-time
addresses. These blocks slide to their run-time addresses as rigid
the task of adjusting mentions of object-file addresses so they refer to
the proper run-time addresses.
_if__(_H8__)
-For the H8/300, @code{_AS__} pads sections if needed to ensure they end
+For the H8/300, @code{@value{as}} pads sections if needed to ensure they end
on a word (sixteen bit) boundary.
_fi__(_H8__)
-@cindex standard @code{_AS__} sections
-An object file written by @code{_AS__} has at least three sections, any
+@cindex standard @code{@value{as}} sections
+An object file written by @code{@value{as}} has at least three sections, any
of which may be empty. These are named @dfn{text}, @dfn{data} and
@dfn{bss} sections.
_if__(_COFF__)
-_if__(_GENERIC__)
+@ifset generic
When it generates COFF output,
-_fi__(_GENERIC__)
-@code{_AS__} can also generate whatever other named sections you specify
+@end ifset
+@code{@value{as}} can also generate whatever other named sections you specify
using the @samp{.section} directive (@pxref{Section,,@code{.section}}).
If you don't use any directives that place output in the @samp{.text}
or @samp{.data} sections, these sections will still exist, but will be empty.
data section follows, and the bss section follows the data section.
To let @code{_LD__} know which data will change when the sections are
-relocated, and how to change that data, @code{_AS__} also writes to the
+relocated, and how to change that data, @code{@value{as}} also writes to the
object file details of the relocation needed. To perform relocation
@code{_LD__} must know, each time an address in the object
file is mentioned:
@cindex addresses, format of
@cindex section-relative addressing
-In fact, every address @code{_AS__} ever uses is expressed as
+In fact, every address @code{@value{as}} ever uses is expressed as
@display
(@var{section}) + (@var{offset into section})
@end display
@noindent
-Further, every expression @code{_AS__} computes is of this section-relative
+Further, every expression @code{@value{as}} computes is of this section-relative
nature. @dfn{Absolute expression} means an expression with section
``absolute'' (@pxref{_LD__ Sections}). A @dfn{pass1 expression} means
-an expression with section ``pass1'' (@pxref{_AS__ Sections,,_AS__
+an expression with section ``pass1'' (@pxref{@value{as} Sections,,@value{as}
Internal Sections}). In this manual we use the notation @{@var{secname}
@var{N}@} to mean ``offset @var{N} into section @var{secname}''.
data and bss sections.
Some sections are manipulated by @code{_LD__}; others are invented for
-use of @code{_AS__} and have no meaning except during assembly.
+use of @code{@value{as}} and have no meaning except during assembly.
@node _LD__ Sections
@section _LD__ Sections
@item text section
@itemx data section
_fi__(_AOUT__||_BOUT__)
-These sections hold your program. @code{_AS__} and @code{_LD__} treat them as
+These sections hold your program. @code{@value{as}} and @code{_LD__} treat them as
separate but equal sections. Anything you can say of one section is
true another.
_if__(_AOUT__||_BOUT__)
@end tex
@c END TEXI2ROFF-KILL
-@node _AS__ Sections
-@section _AS__ Internal Sections
+@node @value{as} Sections
+@section @value{as} Internal Sections
-@cindex internal @code{_AS__} sections
+@cindex internal @code{@value{as}} sections
@cindex sections in messages, internal
-These sections are meant only for the internal use of @code{_AS__}. They
+These sections are meant only for the internal use of @code{@value{as}}. They
have no meaning at run-time. You don't really need to know about these
-sections for most purposes; but they can be mentioned in @code{_AS__}
+sections for most purposes; but they can be mentioned in @code{@value{as}}
warning messages, so it might be helpful to have an idea of their
-meanings to @code{_AS__}. These sections are used to permit the
+meanings to @code{@value{as}}. These sections are used to permit the
value of every expression in your assembly language program to be a
section-relative address.
@cindex bignum/flonum (internal section)
If a number can't be written as a C @code{int} constant (a bignum or a
flonum, but not an integer), it is recorded as belonging to this
-``section''. @code{_AS__} has to remember that a flonum or a bignum
+``section''. @code{@value{as}} has to remember that a flonum or a bignum
does not fit into 32 bits, and cannot be an argument (@pxref{Arguments})
in an expression: this is done by making a flonum or bignum be in a
-separate internal section. This is purely for internal @code{_AS__}
+separate internal section. This is purely for internal @code{@value{as}}
convenience; bignum/flonum section behaves similarly to absolute
section.
process. No compiler need emit such an expression.
@quotation
-@emph{Warning:} the second pass is currently not implemented. @code{_AS__}
+@emph{Warning:} the second pass is currently not implemented. @code{@value{as}}
will abort with an error message if one is required.
@end quotation
(@var{undefined symbol}) @minus{} (@var{undefined symbol})
@end display
-are permitted, and belong to the difference section. @code{_AS__}
+are permitted, and belong to the difference section. @code{@value{as}}
re-evaluates such expressions after the source file has been read and
the symbol table built. If by that time there are no undefined symbols
in the expression then the expression assumes a new section. The
_fi__((_AOUT__||_BOUT__)&&!_GENERIC__)
that you want to end up near to each other in the object
file, even though they are not contiguous in the assembler source.
-@code{_AS__} allows you to use @dfn{subsections} for this purpose.
+@code{@value{as}} allows you to use @dfn{subsections} for this purpose.
Within each section, there can be numbered subsections with
values from 0 to 8192. Objects assembled into the same subsection will
be grouped with other objects in the same subsection when they are all
Subsections are optional. If you don't use subsections, everything
will be stored in subsection number zero.
-_if__(_GENERIC__)
+@ifset generic
Each subsection is zero-padded up to a multiple of four bytes.
(Subsections may be padded a different amount on different flavors
-of @code{_AS__}.)
-_fi__(_GENERIC__)
-_if__(!_GENERIC__)
+of @code{@value{as}}.)
+@end ifset
+@ifclear generic
_if__(_H8__)
On the H8/300 platform, each subsection is zero-padded to a word
boundary (two bytes).
_fi__(_H8__)
-_if__(_I960__)
+@ifset cpu-i960
@c FIXME section padding (alignment)?
@c Rich Pixley says padding here depends on target obj code format; that
@c doesn't seem particularly useful to say without further elaboration,
@c so for now I say nothing about it. If this is a generic BFD issue,
@c these paragraphs might need to vanish from this manual, and be
@c discussed in BFD chapter of binutils (or some such).
-_fi__(_I960__)
+@end ifset
_if__(_A29K__)
On the AMD 29K family, no particular padding is added to section or
-subsection sizes; _AS__ forces no alignment on this platform.
+subsection sizes; @value{as} forces no alignment on this platform.
_fi__(_A29K__)
-_fi__(!_GENERIC__)
+@end ifclear
Subsections appear in your object file in numeric order, lowest numbered
to highest. (All this to be compatible with other people's assemblers.)
into, use a numeric argument to specify it, in a @samp{.text
@var{expression}} or a @samp{.data @var{expression}} statement.
_if__(_COFF__)
-_if__(_GENERIC__)
+@ifset generic
When generating COFF output, you
-_fi__(_GENERIC__)
-_if__(!_GENERIC__)
+@end ifset
+@ifclear generic
You
-_fi__(!_GENERIC__)
+@end ifclear
can also use an extra subsection
argument with arbitrary named sections: @samp{.section @var{name},
@var{expression}}.
Each section has a @dfn{location counter} incremented by one for every
byte assembled into that section. Because subsections are merely a
-convenience restricted to @code{_AS__} there is no concept of a subsection
+convenience restricted to @code{@value{as}} there is no concept of a subsection
location counter. There is no way to directly manipulate a location
counter---but the @code{.align} directive will change it, and any label
definition will capture its current value. The location counter of the
@quotation
@cindex debuggers, and symbol order
-@emph{Warning:} @code{_AS__} does not place symbols in the object file in
+@emph{Warning:} @code{@value{as}} does not place symbols in the object file in
the same order they were declared. This may break some debuggers.
@end quotation
_fi__(!_H8__)
_if__(_H8__)
@samp{_.}
-_if__(_GENERIC__)
+@ifset generic
(On most machines, you can also use @code{$} in symbol names; exceptions
are noted in @ref{_MACH_DEP__}.)
-_fi__(_GENERIC__)
+@end ifset
_fi__(_H8__)
That character may be followed by any string of digits, letters,
_if__(!_H8__)
underscores and dollar signs.
_fi__(!_H8__)
_if__(_H8__)
-_if__(_GENERIC__)
+@ifset generic
dollar signs (unless otherwise noted in @ref{_MACH_DEP__}),
-_fi__(_GENERIC__)
+@end ifset
and underscores.
_fi__(_H8__)
Case of letters is significant:
@table @code
@item L
-All local labels begin with @samp{L}. Normally both @code{_AS__} and
+All local labels begin with @samp{L}. Normally both @code{@value{as}} and
@code{_LD__} forget symbols that start with @samp{L}. These labels are
used for symbols you are never intended to see. If you give the
-@samp{-L} option then @code{_AS__} will retain these symbols in the
+@samp{-L} option then @code{@value{as}} will retain these symbols in the
object file. If you also instruct @code{_LD__} to retain these symbols,
you may use them in debugging.
@cindex current address
@cindex location counter
The special symbol @samp{.} refers to the current address that
-@code{_AS__} is assembling into. Thus, the expression @samp{melvin:
+@code{@value{as}} is assembling into. Thus, the expression @samp{melvin:
.long .} will cause @code{melvin} to contain its own address.
Assigning a value to @code{.} is treated the same as a @code{.org}
directive. Thus, the expression @samp{.=.+4} is the same as saying
Every symbol has, as well as its name, the attributes ``Value'' and
``Type''. Depending on output format, symbols can also have auxiliary
attributes.
-_if__(_INTERNALS__)
+@ifset internals
The detailed definitions are in _0__<a.out.h>_1__.
-_fi__(_INTERNALS__)
+@end ifset
-If you use a symbol without defining it, @code{_AS__} assumes zero for
+If you use a symbol without defining it, @code{@value{as}} assumes zero for
all these attributes, and probably won't warn you. This makes the
symbol an externally defined symbol, which is generally what you
would want.
@cindex @code{b.out} symbol attributes
@cindex symbol attributes, @code{b.out}
-These symbol attributes appear only when @code{_AS__} is configured for
+These symbol attributes appear only when @code{@value{as}} is configured for
one of the Berkeley-descended object output formats.
_fi__(_BOUT__&&!_GENERIC__)
_if__(_GENERIC__||!_BOUT__)
This is an arbitrary 16-bit value. You may establish a symbol's
descriptor value by using a @code{.desc} statement
(@pxref{Desc,,@code{.desc}}). A descriptor value means nothing to
-@code{_AS__}.
+@code{@value{as}}.
@node Symbol Other
@subsubsection Other
@cindex other attribute, of @code{a.out} symbol
-This is an arbitrary 8-bit value. It means nothing to @code{_AS__}.
+This is an arbitrary 8-bit value. It means nothing to @code{@value{as}}.
_fi__(_AOUT__||_BOUT__)
_if__(_COFF__)
@subsubsection Auxiliary Attributes
@cindex auxiliary attributes, COFF symbols
-The @code{_AS__} directives @code{.dim}, @code{.line}, @code{.scl},
+The @code{@value{as}} directives @code{.dim}, @code{.line}, @code{.scl},
@code{.size}, and @code{.tag} can generate auxiliary symbol table
information for COFF.
_fi__(_COFF__)
@cindex expressions, empty
An empty expression has no value: it is just whitespace or null.
Wherever an absolute expression is required, you may omit the
-expression and @code{_AS__} will assume a value of (absolute) 0. This
+expression and @code{@value{as}} will assume a value of (absolute) 0. This
is compatible with other assemblers.
@node Integer Exprs
Numbers are usually integers.
A number can be a flonum or bignum. In this case, you are warned
-that only the low order 32 bits are used, and @code{_AS__} pretends
+that only the low order 32 bits are used, and @code{@value{as}} pretends
these 32 bits are an integer. You may write integer-manipulating
instructions that act on exotic constants, compatible with other
assemblers.
@subsection Prefix Operator
@cindex prefix operators
-@code{_AS__} has the following @dfn{prefix operators}. They each take
+@code{@value{as}} has the following @dfn{prefix operators}. They each take
one argument, which must be absolute.
@c the tex/end tex stuff surrounding this small table is meant to make
* bout-ABORT:: @code{.ABORT}
_fi__(_BOUT__&&!_COFF__)
* Align:: @code{.align @var{abs-expr} , @var{abs-expr}}
-* App-File:: @code{.app-file @var{string}}
+* Appfile:: @code{.appfile @var{string}}
* Ascii:: @code{.ascii "@var{string}"}@dots{}
* Asciz:: @code{.asciz "@var{string}"}@dots{}
* Byte:: @code{.byte @var{expressions}}
This directive stops the assembly immediately. It is for
compatibility with other assemblers. The original idea was that the
assembly language source would be piped into the assembler. If the sender
-of the source quit, it could use this directive tells @code{_AS__} to
+of the source quit, it could use this directive tells @code{@value{as}} to
quit also. One day @code{.abort} will not be supported.
_if__(_COFF__)
@section @code{.ABORT}
@cindex @code{ABORT} directive
-When producing COFF output, @code{_AS__} accepts this directive as a
+When producing COFF output, @code{@value{as}} accepts this directive as a
synonym for @samp{.abort}.
_fi__(_COFF__)
@cindex @code{ABORT} directive
_fi__(!_COFF__)
-When producing @code{b.out} output, @code{_AS__} accepts this directive,
+When producing @code{b.out} output, @code{@value{as}} accepts this directive,
but ignores it.
_fi__(_BOUT__)
the padding bytes. It (and the comma) may be omitted. If it is
omitted, the padding bytes are zero.
-@node App-File
-@section @code{.app-file @var{string}}
+@node Appfile
+@section @code{.appfile @var{string}}
@cindex logical file name
@cindex file name, logical
-@cindex @code{app-file} directive
-@code{.app-file}
+@cindex @code{appfile} directive
+@code{.appfile}
_if__(!_A29K__)
(which may also be spelled @samp{.file})
_fi__(!_A29K__)
-tells @code{_AS__} that we are about to start a new
+tells @code{@value{as}} that we are about to start a new
logical file. @var{string} is the new file name. In general, the
filename is recognized whether or not it is surrounded by quotes @samp{"};
but if you wish to specify an empty file name is permitted,
you must give the quotes--@code{""}. This statement may go away in
-future: it is only recognized to be compatible with old @code{_AS__}
+future: it is only recognized to be compatible with old @code{@value{as}}
programs.@refill
@node Ascii
@section @code{.data @var{subsection}}
@cindex @code{data} directive
-@code{.data} tells @code{_AS__} to assemble the following statements onto the
+@code{.data} tells @code{@value{as}} to assemble the following statements onto the
end of the data subsection numbered @var{subsection} (which is an
absolute expression). If @var{subsection} is omitted, it defaults
to zero.
definition extends until the @code{.endef} directive is encountered.
_if__(_BOUT__)
-This directive is only observed when @code{_AS__} is configured for COFF
+This directive is only observed when @code{@value{as}} is configured for COFF
format output; when producing @code{b.out}, @samp{.def} is recognized,
but ignored.
_fi__(_BOUT__)
to the low 16 bits of an absolute expression.
_if__(_COFF__)
-The @samp{.desc} directive is not available when @code{_AS__} is
+The @samp{.desc} directive is not available when @code{@value{as}} is
configured for COFF output; it is only for @code{a.out} or @code{b.out}
-object format. For the sake of compatibility, @code{_AS__} will accept
+object format. For the sake of compatibility, @code{@value{as}} will accept
it, but produce no output, when configured for COFF.
_fi__(_COFF__)
_fi__(_AOUT__||_BOUT__)
_if__(_BOUT__)
@samp{.dim} is only meaningful when generating COFF format output; when
-@code{_AS__} is generating @code{b.out}, it accepts this directive but
+@code{@value{as}} is generating @code{b.out}, it accepts this directive but
ignores it.
_fi__(_BOUT__)
_fi__(_COFF__ || _BOUT__)
@cindex floating point numbers (double)
@code{.double} expects zero or more flonums, separated by commas. It
assembles floating point numbers.
-_if__(_GENERIC__)
+@ifset generic
The exact kind of floating point numbers emitted depends on how
-@code{_AS__} is configured. @xref{_MACH_DEP__}.
-_fi__(_GENERIC__)
+@code{@value{as}} is configured. @xref{_MACH_DEP__}.
+@end ifset
_if__((!_GENERIC__) && _IEEEFLOAT__)
-On the _HOST__ family @samp{.double} emits 64-bit floating-point numbers
+On the @value{host} family @samp{.double} emits 64-bit floating-point numbers
in @sc{ieee} format.
_fi__((!_GENERIC__) && _IEEEFLOAT__)
@section @code{.else}
@cindex @code{else} directive
-@code{.else} is part of the @code{_AS__} support for conditional
+@code{.else} is part of the @code{@value{as}} support for conditional
assembly; @pxref{If,,@code{.if}}. It marks the beginning of a section
of code to be assembled if the condition for the preceding @code{.if}
was false.
_if__(_BOUT__)
@samp{.endef} is only meaningful when generating COFF format output; if
-@code{_AS__} is configured to generate @code{b.out}, it accepts this
+@code{@value{as}} is configured to generate @code{b.out}, it accepts this
directive but ignores it.
_fi__(_BOUT__)
_fi__(_COFF__||_BOUT__)
@section @code{.endif}
@cindex @code{endif} directive
-@code{.endif} is part of the @code{_AS__} support for conditional assembly;
+@code{.endif} is part of the @code{@value{as}} support for conditional assembly;
it marks the end of a block of code that is only assembled
conditionally. @xref{If,,@code{.if}}.
@cindex @code{extern} directive
@code{.extern} is accepted in the source program---for compatibility
-with other assemblers---but it is ignored. @code{_AS__} treats
+with other assemblers---but it is ignored. @code{@value{as}} treats
all undefined symbols as external.
_if__(_GENERIC__||!_A29K__)
@cindex @code{file} directive
@cindex logical file name
@cindex file name, logical
-@code{.file} (which may also be spelled @samp{.app-file}) tells
-@code{_AS__} that we are about to start a new logical file.
+@code{.file} (which may also be spelled @samp{.appfile}) tells
+@code{@value{as}} that we are about to start a new logical file.
@var{string} is the new file name. In general, the filename is
recognized whether or not it is surrounded by quotes @samp{"}; but if
you wish to specify an empty file name, you must give the
quotes--@code{""}. This statement may go away in future: it is only
-recognized to be compatible with old @code{_AS__} programs.
+recognized to be compatible with old @code{@value{as}} programs.
_if__(_A29K__)
-In some configurations of @code{_AS__}, @code{.file} has already been
+In some configurations of @code{@value{as}}, @code{.file} has already been
removed to avoid conflicts with other assemblers. @xref{_MACH_DEP__}.
_fi__(_A29K__)
_fi__(_GENERIC__||!_A29K__)
other people's assemblers. The contents of each @var{repeat} bytes
is taken from an 8-byte number. The highest order 4 bytes are
zero. The lowest order 4 bytes are @var{value} rendered in the
-byte-order of an integer on the computer @code{_AS__} is assembling for.
+byte-order of an integer on the computer @code{@value{as}} is assembling for.
Each @var{size} bytes in a repetition is taken from the lowest order
@var{size} bytes of this number. Again, this bizarre behavior is
compatible with other people's assemblers.
@cindex @code{float} directive
This directive assembles zero or more flonums, separated by commas. It
has the same effect as @code{.single}.
-_if__(_GENERIC__)
+@ifset generic
The exact kind of floating point numbers emitted depends on how
-@code{_AS__} is configured.
+@code{@value{as}} is configured.
@xref{_MACH_DEP__}.
-_fi__(_GENERIC__)
+@end ifset
_if__((!_GENERIC__) && _IEEEFLOAT__)
-On the _HOST__ family, @code{.float} emits 32-bit floating point numbers
+On the @value{host} family, @code{.float} emits 32-bit floating point numbers
in @sc{ieee} format.
_fi__((!_GENERIC__) && _IEEEFLOAT__)
This expects zero or more @var{expressions}, and emits
a 16 bit number for each.
-_if__(_GENERIC__)
+@ifset generic
This directive is a synonym for @samp{.short}; depending on the target
architecture, it may also be a synonym for @samp{.word}.
-_fi__(_GENERIC__)
+@end ifset
_if__( _W32__ && !_GENERIC__ )
This directive is a synonym for @samp{.short}.
_fi__( _W32__ && !_GENERIC__ )
@cindex @code{ident} directive
This directive is used by some assemblers to place tags in object files.
-@code{_AS__} simply accepts the directive for source-file
+@code{@value{as}} simply accepts the directive for source-file
compatibility with such assemblers, but does not actually emit anything
for it.
_fi__(_AOUT__||_BOUT__||_COFF__)
@section @code{.lflags}
@cindex @code{lflags} directive (ignored)
-@code{_AS__} accepts this directive, for compatibility with other
+@code{@value{as}} accepts this directive, for compatibility with other
assemblers, but ignores it.
_if__(_GENERIC__ || !_A29K__)
_fi__(_A29K__ && (!_GENERIC__) && !_COFF__)
@cindex logical line number
_if__(_AOUT__||_BOUT__)
-Tell @code{_AS__} to change the logical line number. @var{line-number} must be
+Tell @code{@value{as}} to change the logical line number. @var{line-number} must be
an absolute expression. The next line will have that logical line
number. So any other statements on the current line (after a statement
separator
-_if__(_GENERIC__)
+@ifset generic
character)
-_fi__(_GENERIC__)
-_if__(!_GENERIC__)
+@end ifset
+@ifclear generic
_if__(! (_A29K__||_H8__) )
character @code{;})
_fi__(! (_A29K__||_H8__) )
_if__(_H8__)
character @samp{$})
_fi__(_H8__)
-_fi__(!_GENERIC__)
+@end ifclear
will be reported as on logical line number
@var{line-number} @minus{} 1.
One day this directive will be unsupported: it is used only
for compatibility with existing assembler programs. @refill
_if__(_GENERIC__ && _A29K__)
-@emph{Warning:} In the AMD29K configuration of _AS__, this command is
+@emph{Warning:} In the AMD29K configuration of @value{as}, this command is
only available with the name @code{.ln}, rather than as either
@code{.line} or @code{.ln}.
_fi__(_GENERIC__ && _A29K__)
_if__(_COFF__ && !_A29K__)
Even though this is a directive associated with the @code{a.out} or
-@code{b.out} object-code formats, @code{_AS__} will still recognize it
+@code{b.out} object-code formats, @code{@value{as}} will still recognize it
when producing COFF output, and will treat @samp{.line} as though it
were the COFF @samp{.ln} @emph{if} it is found outside a
@code{.def}/@code{.endef} pair.
@section @code{.ln @var{line-number}}
@cindex @code{ln} directive
-Tell @code{_AS__} to change the logical line number. @var{line-number}
+Tell @code{@value{as}} to change the logical line number. @var{line-number}
must be an absolute expression. The next line will have that logical
line number, so any other statements on the current line (after a
statement separator character @code{;}) will be reported as on logical
line number @var{line-number} @minus{} 1.
_if__(_BOUT__)
-This directive is accepted, but ignored, when @code{_AS__} is configured for
+This directive is accepted, but ignored, when @code{@value{as}} is configured for
@code{b.out}; its effect is only associated with COFF output format.
_fi__(_BOUT__)
_fi__(_COFF__&&!_AOUT__)
you can't use @code{.org} to cross sections: if @var{new-lc} has the
wrong section, the @code{.org} directive is ignored. To be compatible
with former assemblers, if the section of @var{new-lc} is absolute,
-@code{_AS__} will issue a warning, then pretend the section of @var{new-lc}
+@code{@value{as}} will issue a warning, then pretend the section of @var{new-lc}
is the same as the current subsection.
@code{.org} may only increase the location counter, or leave it
@c double negative used below "not undefined" because this is a specific
@c reference to "undefined" (as SEG_UNKNOWN is called in this manual)
@c section. pesch@cygnus.com 18feb91
-Because @code{_AS__} tries to assemble programs in one pass @var{new-lc}
+Because @code{@value{as}} tries to assemble programs in one pass @var{new-lc}
may not be undefined. If you really detest this restriction we eagerly await
a chance to share your improved assembler.
of 60. You may omit the comma and @var{columns} specification; the
default width is 200 columns.
-@code{_AS__} will generate formfeeds whenever the specified number of
+@code{@value{as}} will generate formfeeds whenever the specified number of
lines is exceeded (or whenever you explicitly request one, using
@code{.eject}).
_if__(_BOUT__)
The @samp{.scl} directive is primarily associated with COFF output; when
-configured to generate @code{b.out} output format, @code{_AS__} will
+configured to generate @code{b.out} output format, @code{@value{as}} will
accept this directive but ignore it.
_fi__(_BOUT__)
_fi__(_COFF__||_BOUT__)
@cindex COFF named section
Assemble the following code into end of subsection numbered
@var{subsection} in the COFF named section @var{name}. If you omit
-@var{subsection}, @code{_AS__} uses subsection number zero.
+@var{subsection}, @code{@value{as}} uses subsection number zero.
@samp{.section .text} is equivalent to the @code{.text} directive;
@samp{.section .data} is equivalent to the @code{.data} directive.
_fi__(_COFF__)
You may @code{.set} a symbol many times in the same assembly.
If the expression's section is unknowable during pass 1, a second
pass over the source program will be forced. The second pass is
-currently not implemented. @code{_AS__} will abort with an error
+currently not implemented. @code{@value{as}} will abort with an error
message if one is required.
If you @code{.set} a global symbol, the value stored in the object
@cindex floating point numbers (single)
This directive assembles zero or more flonums, separated by commas. It
has the same effect as @code{.float}.
-_if__(_GENERIC__)
+@ifset generic
The exact kind of floating point numbers emitted depends on how
-@code{_AS__} is configured. @xref{_MACH_DEP__}.
-_fi__(_GENERIC__)
+@code{@value{as}} is configured. @xref{_MACH_DEP__}.
+@end ifset
_if__((!_GENERIC__) && _IEEEFLOAT__)
-On the _HOST__ family, @code{.single} emits 32-bit floating point
+On the @value{host} family, @code{.single} emits 32-bit floating point
numbers in @sc{ieee} format.
_fi__((!_GENERIC__) && _IEEEFLOAT__)
_if__(_BOUT__)
@samp{.size} is only meaningful when generating COFF format output; when
-@code{_AS__} is generating @code{b.out}, it accepts this directive but
+@code{@value{as}} is generating @code{b.out}, it accepts this directive but
ignores it.
_fi__(_BOUT__)
_fi__(_COFF__||_BOUT__)
_fi__(_GENERIC__ || !_A29K__)
_if__(_A29K__)
-_if__(!_GENERIC__)
+@ifclear generic
@section @code{.space}
@cindex @code{space} directive
-_fi__(!_GENERIC__)
+@end ifclear
On the AMD 29K, this directive is ignored; it is accepted for
compatibility with other AMD 29K assemblers.
@cindex @code{stab@var{x}} directives
There are three directives that begin @samp{.stab}.
All emit symbols (@pxref{Symbols}), for use by symbolic debuggers.
-The symbols are not entered in the @code{_AS__} hash table: they
+The symbols are not entered in the @code{@value{as}} hash table: they
cannot be referenced elsewhere in the source file.
Up to five fields are required:
@table @var
_if__(_BOUT__)
@samp{.tag} is only used when generating COFF format output; when
-@code{_AS__} is generating @code{b.out}, it accepts this directive but
+@code{@value{as}} is generating @code{b.out}, it accepts this directive but
ignores it.
_fi__(_BOUT__)
_fi__(_COFF__||_BOUT__)
@section @code{.text @var{subsection}}
@cindex @code{text} directive
-Tells @code{_AS__} to assemble the following statements onto the end of
+Tells @code{@value{as}} to assemble the following statements onto the end of
the text subsection numbered @var{subsection}, which is an absolute
expression. If @var{subsection} is omitted, subsection number zero
is used.
_if__(_BOUT__)
@samp{.type} is associated only with COFF format output; when
-@code{_AS__} is configured for @code{b.out} output, it accepts this
+@code{@value{as}} is configured for @code{b.out} output, it accepts this
directive but ignores it.
_fi__(_BOUT__)
_fi__(_COFF__||_BOUT__)
entry.
_if__(_BOUT__)
-@samp{.val} is used only for COFF output; when @code{_AS__} is
+@samp{.val} is used only for COFF output; when @code{@value{as}} is
configured for @code{b.out}, it accepts this directive but ignores it.
_fi__(_BOUT__)
_fi__(_COFF__||_BOUT__)
This directive expects zero or more @var{expressions}, of any section,
separated by commas.
_if__((!_GENERIC__) && _W32__)
-For each expression, @code{_AS__} emits a 32-bit number.
+For each expression, @code{@value{as}} emits a 32-bit number.
_fi__((!_GENERIC__) && _W32__)
_if__((!_GENERIC__) && _W16__)
-For each expression, @code{_AS__} emits a 16-bit number.
+For each expression, @code{@value{as}} emits a 16-bit number.
_fi__((!_GENERIC__) && _W16__)
-_if__(_GENERIC__)
+@ifset generic
The size of the number emitted, and its byte order,
depends on what kind of computer will run the program.
-_fi__(_GENERIC__)
+@end ifset
@c on amd29k, i960, sparc the "special treatment to support compilers" doesn't
@c happen---32-bit addressability, period; no long/short jumps.
@emph{Warning: Special Treatment to support Compilers}
@end quotation
-_if__(_GENERIC__)
+@ifset generic
Machines with a 32-bit address space, but that do less than 32-bit
addressing, require the following special treatment. If the machine of
interest to you does 32-bit addressing (or doesn't require it;
@pxref{_MACH_DEP__}), you can ignore this issue.
-_fi__(_GENERIC__)
+@end ifset
In order to assemble compiler output into something that will work,
-@code{_AS__} will occasionlly do strange things to @samp{.word} directives.
+@code{@value{as}} will occasionlly do strange things to @samp{.word} directives.
Directives of the form @samp{.word sym1-sym2} are often emitted by
-compilers as part of jump tables. Therefore, when @code{_AS__} assembles a
+compilers as part of jump tables. Therefore, when @code{@value{as}} assembles a
directive of the form @samp{.word sym1-sym2}, and the difference between
-@code{sym1} and @code{sym2} does not fit in 16 bits, @code{_AS__} will
+@code{sym1} and @code{sym2} does not fit in 16 bits, @code{@value{as}} will
create a @dfn{secondary jump table}, immediately before the next label.
This secondary jump table will be preceded by a short-jump to the
first byte after the secondary table. This short-jump prevents the flow
minus the address of the long-jump to @code{sym4}; and so on, for as many
entries in the original jump table as necessary.
-_if__(_INTERNALS__)
-@emph{This feature may be disabled by compiling @code{_AS__} with the
+@ifset internals
+@emph{This feature may be disabled by compiling @code{@value{as}} with the
@samp{-DWORKING_DOT_WORD} option.} This feature is likely to confuse
assembly language programmers.
-_fi__(_INTERNALS__)
+@end ifset
_fi__(_GENERIC__ || _DIFFTABKLUG__)
@node Deprecated
They are included for compatibility with older assemblers.
@table @t
@item .abort
-@item .app-file
+@item .appfile
@item .line
@end table
@node _MACH_DEP__
-_if__(_GENERIC__)
+@ifset generic
@chapter Machine Dependent Features
@cindex machine dependencies
The machine instruction sets are (almost by definition) different on
-each machine where @code{_AS__} runs. Floating point representations
-vary as well, and @code{_AS__} often supports a few additional
+each machine where @code{@value{as}} runs. Floating point representations
+vary as well, and @code{@value{as}} often supports a few additional
directives or command-line options for compatibility with other
assemblers on a particular platform. Finally, some versions of
-@code{_AS__} support special pseudo-instructions for branch
+@code{@value{as}} support special pseudo-instructions for branch
optimization.
This chapter discusses most of these differences, though it does not
_if__(_H8__)
* H8/300-Dependent:: Hitachi H8/300 Dependent Features
_fi__(_H8__)
-_if__(_I960__)
+@ifset cpu-i960
* i960-Dependent:: Intel 80960 Dependent Features
-_fi__(_I960__)
-_if__(_M680X0__)
+@end ifset
+@ifset cpu-m68k
* M68K-Dependent:: M680x0 Dependent Features
-_fi__(_M680X0__)
+@end ifset
_if__(_SPARC__)
* Sparc-Dependent:: SPARC Dependent Features
_fi__(_SPARC__)
_fi__(_I80386__)
@end menu
-_fi__(_GENERIC__)
+@end ifset
_if__(_VAX__)
-_if__(_GENERIC__)
+@ifset generic
@node Vax-Dependent
-_fi__(_GENERIC__)
+@end ifset
_CHAPSEC__(0+_GENERIC__) VAX Dependent Features
@cindex VAX support
@cindex command-line options ignored, VAX
@cindex VAX command-line options ignored
-The Vax version of @code{_AS__} accepts any of the following options,
+The Vax version of @code{@value{as}} accepts any of the following options,
gives a warning message that the option was ignored and proceeds.
These options are for compatibility with scripts designed for other
people's assemblers.
@cindex @code{-V}, redundant on VAX
Some other assemblers use a temporary file. This option
commanded them to keep the information in active memory rather
-than in a disk file. @code{_AS__} always does this, so this
+than in a disk file. @code{@value{as}} always does this, so this
option is redundant.
@item @kbd{-J} (JUMPify Longer Branches)
@cindex @code{-t}, ignored on VAX
Some other assemblers may use a temporary file, and this option
takes a filename being the directory to site the temporary
-file. @code{_AS__} does not use a temporary disk file, so this
+file. @code{@value{as}} does not use a temporary disk file, so this
option makes no difference. @kbd{-t} needs exactly one
filename.
@end table
@c FIXME! look into "I think" below, correct if needed, delete.
The Vax version of the assembler accepts two options when
compiled for VMS. They are @kbd{-h}, and @kbd{-+}. The
-@kbd{-h} option prevents @code{_AS__} from modifying the
+@kbd{-h} option prevents @code{@value{as}} from modifying the
symbol-table entries for symbols that contain lowercase
-characters (I think). The @kbd{-+} option causes @code{_AS__} to
+characters (I think). The @kbd{-+} option causes @code{@value{as}} to
print warning messages if the FILENAME part of the object file,
or any symbol name is larger than 31 characters. The @kbd{-+}
option also insertes some code following the @samp{_main}
@cindex VAX bitfields not supported
@cindex bitfields, not supported on VAX
-Vax bit fields can not be assembled with @code{_AS__}. Someone
+Vax bit fields can not be assembled with @code{@value{as}}. Someone
can add the required code if they really need it.
_fi__(_VAX__)
_if__(_A29K__)
-_if__(_GENERIC__)
+@ifset generic
@node AMD29K-Dependent
-_fi__(_GENERIC__)
+@end ifset
_CHAPSEC__(0+_GENERIC__) AMD 29K Dependent Features
@cindex AMD 29K support
_CHAPSEC__(1+_GENERIC__) Options
@cindex AMD 29K options (none)
@cindex options for AMD29K (none)
-@code{_AS__} has no additional command-line options for the AMD
+@code{@value{as}} has no additional command-line options for the AMD
29K family.
@node AMD29K Syntax
@cindex AMD 29K special purpose registers
@cindex protected registers, AMD 29K
@cindex AMD 29K protected registers
-In addition, @code{_AS__} understands the following protected
+In addition, @code{@value{as}} understands the following protected
special-purpose register names for the AMD 29K family:
@smallexample
@quotation
@emph{Warning:} in other versions of the GNU assembler, @code{.file} is
-used for the directive called @code{.app-file} in the AMD 29K support.
+used for the directive called @code{.appfile} in the AMD 29K support.
@end quotation
@item .line
@cindex AMD 29K opcodes
@cindex opcodes for AMD 29K
-@code{_AS__} implements all the standard AMD 29K opcodes. No
+@code{@value{as}} implements all the standard AMD 29K opcodes. No
additional pseudo-instructions are needed on this family.
For information on the 29K machine instruction set, see @cite{Am29000
_fi__(_A29K__)
_if__(_H8__)
-_if__(_GENERIC__)
+@ifset generic
@node H8/300-Dependent
-_fi__(_GENERIC__)
+@end ifset
_CHAPSEC__(0+_GENERIC__) H8/300 Dependent Features
@cindex H8/300 support
@cindex H8/300 options (none)
@cindex options, H8/300 (none)
-@code{_AS__} has no additional command-line options for the Hitachi
+@code{@value{as}} has no additional command-line options for the Hitachi
H8/300 family.
@node H8/300 Syntax
@cindex addressing modes, H8/300
@cindex H8/300 addressing modes
-_AS__ understands the following addressing modes for the H8/300:
+@value{as} understands the following addressing modes for the H8/300:
@table @code
@item r@var{n}
Register direct
@itemx @code{@@}@var{aa}:8
@itemx @code{@@}@var{aa}:16
Absolute address @code{aa}. You may specify the @samp{:8} or @samp{:16}
-for clarity, if you wish; but @code{_AS__} neither requires this nor
+for clarity, if you wish; but @code{@value{as}} neither requires this nor
uses it---the address size required is taken from context.
@item #@var{xx}
@itemx #@var{xx}:8
@itemx #@var{xx}:16
Immediate data @var{xx}. You may specify the @samp{:8} or @samp{:16}
-for clarity, if you wish; but @code{_AS__} neither requires this nor
+for clarity, if you wish; but @code{@value{as}} neither requires this nor
uses it---the data size required is taken from context.
@item @code{@@}@code{@@}@var{aa}
@itemx @code{@@}@code{@@}@var{aa}:8
Memory indirect. You may specify the @samp{:8} for clarity, if you
-wish; but @code{_AS__} neither requires this nor uses it.
+wish; but @code{@value{as}} neither requires this nor uses it.
@end table
@node H8/300 Floating Point
@cindex machine directives, H8/300 (none)
@cindex @code{word} directive, H8/300
@cindex @code{int} directive, H8/300
-@code{_AS__} has no machine-dependent directives for the H8/300.
+@code{@value{as}} has no machine-dependent directives for the H8/300.
However, on this platform the @samp{.int} and @samp{.word} directives
generate 16-bit numbers.
For detailed information on the H8/300 machine instruction set, see
@cite{H8/300 Series Programming Manual} (Hitachi ADE--602--025).
-@code{_AS__} implements all the standard H8/300 opcodes. No additional
+@code{@value{as}} implements all the standard H8/300 opcodes. No additional
pseudo-instructions are needed on this family.
The following table summarizes the opcodes and their arguments:
@cindex H8/300 size suffixes
Four H8/300 instructions (@code{add}, @code{cmp}, @code{mov},
@code{sub}) are defined with variants using the suffixes @samp{.b} and
-@samp{.w} to specify the size of a memory operand. @code{_AS__}
+@samp{.w} to specify the size of a memory operand. @code{@value{as}}
supports these suffixes, but does not require them; since one of the
-operands is always a register, @code{_AS__} can deduce the correct size.
+operands is always a register, @code{@value{as}} can deduce the correct size.
For example, since @code{r0} refers to a 16-bit register,
@example
mov.w r0,@@foo
@end example
-If you use the size suffixes, @code{_AS__} will issue a warning if
+If you use the size suffixes, @code{@value{as}} will issue a warning if
there's a mismatch between the suffix and the register size.
_fi__(_H8__)
-_if__(_I960__)
-_if__(_GENERIC__)
+@ifset cpu-i960
+@ifset generic
@node i960-Dependent
-_fi__(_GENERIC__)
+@end ifset
_CHAPSEC__(0+_GENERIC__) Intel 80960 Dependent Features
@cindex i960 support
@samp{-ACA} is equivalent to @samp{-ACA_A}; @samp{-AKC} is equivalent to
@samp{-AMC}. Synonyms are provided for compatibility with other tools.
-If none of these options is specified, @code{_AS__} will generate code for any
+If none of these options is specified, @code{@value{as}} will generate code for any
instruction or feature that is supported by @emph{some} version of the
960 (even if this means mixing architectures!). In principle,
-@code{_AS__} will attempt to deduce the minimal sufficient processor
+@code{@value{as}} will attempt to deduce the minimal sufficient processor
type if none is specified; depending on the object code format, the
processor type may be recorded in the object file. If it is critical
-that the @code{_AS__} output match a specific architecture, specify that
+that the @code{@value{as}} output match a specific architecture, specify that
architecture explicitly.
@item -b
displacements greater than 13 bits (or that have external targets) are
replaced with the corresponding compare (or @samp{chkbit}) and branch
instructions. You can use the @samp{-norelax} option to specify that
-@code{_AS__} should generate errors instead, if the target displacement
+@code{@value{as}} should generate errors instead, if the target displacement
is larger than 13 bits.
This option does not affect the Compare-and-Jump instructions; the code
@cindex floating point, i960 (@sc{ieee})
@cindex i960 floating point (@sc{ieee})
-@code{_AS__} generates @sc{ieee} floating-point numbers for the directives
+@code{@value{as}} generates @sc{ieee} floating-point numbers for the directives
@samp{.float}, @samp{.double}, @samp{.extended}, and @samp{.single}.
@node Directives-i960
the most appropriate form of subroutine call: @samp{call},
@samp{bal}, or @samp{calls}. If the assembly source contains
enough information---a @samp{.leafproc} or @samp{.sysproc} directive
-defining the operand---then @code{_AS__} will translate the
+defining the operand---then @code{@value{as}} will translate the
@code{callj}; if not, it will simply emit the @code{callj}, leaving it
for the linker to resolve.
@cindex compare and jump expansions, i960
@cindex i960 compare and jump expansions
-Whether @code{_AS__} gives an error or expands the instruction depends
+Whether @code{@value{as}} gives an error or expands the instruction depends
on two choices you can make: whether you use the @samp{-norelax} option,
and whether you use a ``Compare and Branch'' instruction or a ``Compare
and Jump'' instruction. The ``Jump'' instructions are @emph{always}
expanded if necessary; the ``Branch'' instructions are expanded when
necessary @emph{unless} you specify @code{-norelax}---in which case
-@code{_AS__} gives an error instead.
+@code{@value{as}} gives an error instead.
These are the Compare-and-Branch instructions, their ``Jump'' variants,
and the instruction pairs they may expand into:
cmpobne& cmpojne& cmpo; bne\cr}
@end tex
@c END TEXI2ROFF-KILL
-_fi__(_I960__)
+@end ifset
-_if__(_M680X0__)
-_if__(_GENERIC__)
+@ifset cpu-m68k
+@ifset generic
@node M68K-Dependent
-_fi__(_GENERIC__)
+@end ifset
_CHAPSEC__(0+_GENERIC__) M680x0 Dependent Features
@cindex M680x0 support
@cindex options, M680x0
@cindex M680x0 options
-The Motorola 680x0 version of @code{_AS__} has two machine dependent options.
+The Motorola 680x0 version of @code{@value{as}} has two machine dependent options.
One shortens undefined references from 32 to 16 bits, while the
-other is used to tell @code{_AS__} what kind of machine it is
+other is used to tell @code{@value{as}} what kind of machine it is
assembling for.
@cindex @code{-l} option, M680x0
You can use the @kbd{-l} option to shorten the size of references to
undefined symbols. If the @kbd{-l} option is not given, references to
-undefined symbols will be a full long (32 bits) wide. (Since @code{_AS__}
-cannot know where these symbols will end up, @code{_AS__} can only allocate
-space for the linker to fill in later. Since @code{_AS__} doesn't know how
+undefined symbols will be a full long (32 bits) wide. (Since @code{@value{as}}
+cannot know where these symbols will end up, @code{@value{as}} can only allocate
+space for the linker to fill in later. Since @code{@value{as}} doesn't know how
far away these symbols will be, it allocates as much space as it can.)
If this option is given, the references will only be one word wide (16
bits). This may be useful if you want the object file to be as small as
@cindex @code{-m68000} and related options
@cindex architecture options, M680x0
@cindex M680x0 architecture options
-The 680x0 version of @code{_AS__} is most frequently used to assemble
+The 680x0 version of @code{@value{as}} is most frequently used to assemble
programs for the Motorola MC68020 microprocessor. Occasionally it is
used to assemble programs for the mostly similar, but slightly different
-MC68000 or MC68010 microprocessors. You can give @code{_AS__} the options
+MC68000 or MC68010 microprocessors. You can give @code{@value{as}} the options
@samp{-m68000}, @samp{-mc68000}, @samp{-m68010}, @samp{-mc68010},
@samp{-m68020}, and @samp{-mc68020} to tell it what processor is the
target.
@cindex syntax, M680x0
@cindex M680x0 size modifiers
@cindex size modifiers, M680x0
-The 680x0 version of @code{_AS__} uses syntax similar to the Sun assembler.
+The 680x0 version of @code{@value{as}} uses syntax similar to the Sun assembler.
Size modifiers are appended directly to the end of the opcode without an
intervening period. For example, write @samp{movl} rather than
@samp{move.l}.
-_if__(_INTERNALS__)
-If @code{_AS__} is compiled with SUN_ASM_SYNTAX defined, it will also allow
+@ifset internals
+If @code{@value{as}} is compiled with SUN_ASM_SYNTAX defined, it will also allow
Sun-style local labels of the form @samp{1$} through @samp{$9}.
-_fi__(_INTERNALS__)
+@end ifset
In the following table @dfn{apc} stands for any of the address
registers (@samp{a0} through @samp{a7}), nothing, (@samp{}), the
@end smallexample
For the cases of non-PC relative displacements and long displacements on
-the 68000 or 68010, @code{_AS__} will issue a longer code fragment in terms of
+the 68000 or 68010, @code{@value{as}} will issue a longer code fragment in terms of
@var{NX}, the opposite condition to @var{XX}. For example, for the
non-PC relative case:
@smallexample
@end smallexample
Other than for word and byte displacements, when the source reads
-@samp{db@var{XX} foo}, @code{_AS__} will emit
+@samp{db@var{XX} foo}, @code{@value{as}} will emit
@smallexample
db@var{XX} oo1
bra oo2
fjugt fjule fjult fjun
@end smallexample
-For branch targets that are not PC relative, @code{_AS__} emits
+For branch targets that are not PC relative, @code{@value{as}} emits
@smallexample
fb@var{NX} oof
jmp foo
beginning of a line, it is treated as a comment unless it looks like
@samp{# line file}, in which case it is treated normally.
-_fi__(_M680X0__)
+@end ifset
_if__(0)
@c pesch@cygnus.com: conditionalize on something other than 0 when filled in.
@section 32x32
@section Options
-The 32x32 version of @code{_AS__} accepts a @kbd{-m32032} option to
+The 32x32 version of @code{@value{as}} accepts a @kbd{-m32032} option to
specify thiat it is compiling for a 32032 processor, or a
@kbd{-m32532} to specify that it is compiling for a 32532 option.
The default (if neither is specified) is chosen when the assembler
@subsection Syntax
I don't know anything about the 32x32 syntax assembled by
-@code{_AS__}. Someone who undersands the processor (I've never seen
+@code{@value{as}}. Someone who undersands the processor (I've never seen
one) and the possible syntaxes should write this section.
@subsection Floating Point
-The 32x32 uses @sc{ieee} floating point numbers, but @code{_AS__} will only
+The 32x32 uses @sc{ieee} floating point numbers, but @code{@value{as}} will only
create single or double precision values. I don't know if the 32x32
understands extended precision numbers.
_fi__(0)
_if__(_SPARC__)
-_if__(_GENERIC__)
+@ifset generic
@node Sparc-Dependent
-_fi__(_GENERIC__)
+@end ifset
_CHAPSEC__(0+_GENERIC__) SPARC Dependent Features
@cindex SPARC support
@cindex SPARC machine directives
@cindex machine directives, SPARC
-The Sparc version of @code{_AS__} supports the following additional
+The Sparc version of @code{@value{as}} supports the following additional
machine directives:
@table @code
_fi__(_SPARC__)
_if__(_I80386__)
-_if__(_GENERIC__)
+@ifset generic
@node i386-Dependent
-_fi__(_GENERIC__)
+@end ifset
_CHAPSEC__(0+_GENERIC__) 80386 Dependent Features
@cindex i386 support
@cindex i386 syntax compatibility
@cindex syntax compatibility, i386
In order to maintain compatibility with the output of @code{_GCC__},
-@code{_AS__} supports AT&T System V/386 assembler syntax. This is quite
+@code{@value{as}} supports AT&T System V/386 assembler syntax. This is quite
different from Intel syntax. We mention these differences because
almost all 80386 documents used only Intel syntax. Notable differences
between the two syntaxes are:
Opcode names are suffixed with one character modifiers which specify the
size of operands. The letters @samp{b}, @samp{w}, and @samp{l} specify
byte, word, and long operands. If no suffix is specified by an
-instruction and it contains no memory operands then @code{_AS__} tries to
+instruction and it contains no memory operands then @code{@value{as}} tries to
fill in the missing suffix based on the destination register operand
(the last one by convention). Thus, @samp{mov %ax, %bx} is equivalent
to @samp{movw %ax, %bx}; also, @samp{mov $1, %bx} is equivalent to
@noindent
are called @samp{cbtw}, @samp{cwtl}, @samp{cwtd}, and @samp{cltd} in
-AT&T naming. @code{_AS__} accepts either naming for these instructions.
+AT&T naming. @code{@value{as}} accepts either naming for these instructions.
@cindex jump instructions, i386
@cindex call instructions, i386
default section register (see a 80386 manual for section register
defaults). Note that section overrides in AT&T syntax @emph{must} have
be preceded by a @samp{%}. If you specify a section override which
-coincides with the default section register, @code{_AS__} will @emph{not}
+coincides with the default section register, @code{@value{as}} will @emph{not}
output any section register override prefixes to assemble the given
instruction. Thus, section overrides can be specified to emphasize which
section register is used for a given memory operand.
@end table
Absolute (as opposed to PC relative) call and jump operands must be
-prefixed with @samp{*}. If no @samp{*} is specified, @code{_AS__} will
+prefixed with @samp{*}. If no @samp{*} is specified, @code{@value{as}} will
always choose PC relative addressing for jump/call labels.
Any instruction that has a memory operand @emph{must} specify its size (byte,
@cindex @code{fwait instruction}, i386
Since the 80387 automatically synchronizes with the 80386 @samp{fwait}
instructions are almost never needed (this is not the case for the
-80286/80287 and 8086/8087 combinations). Therefore, @code{_AS__} suppresses
+80286/80287 and 8086/8087 combinations). Therefore, @code{@value{as}} suppresses
the @samp{fwait} instruction whenever it is implicitly selected by one
of the @samp{fn@dots{}} instructions. For example, @samp{fsave} and
@samp{fnsave} are treated identically. In general, all the @samp{fn@dots{}}
_fi__(_I80386__)
_if__(_Z8000__)
-_if__(_GENERIC__)
+@ifset generic
@node Z8000-Dependent
-_fi__(_GENERIC__)
+@end ifset
_CHAPSEC__(0+_GENERIC__) Z8000 Dependent Features
@cindex Z8000 support
-The Z8000 _AS__ supports both members of the Z8000 family: the
+The Z8000 @value{as} supports both members of the Z8000 family: the
unsegmented Z8002, with 16 bit addresses, and the segmented Z8001 with
24 bit addresses.
@cindex Z8000 options
@cindex options, Z8000
-@code{_AS__} has no additional command-line options for the Zilog
+@code{@value{as}} has no additional command-line options for the Zilog
Z8000 family.
@node Z8000 Syntax
@cindex addressing modes, Z8000
@cindex Z800 addressing modes
-_AS__ understands the following addressing modes for the Z8000:
+@value{as} understands the following addressing modes for the Z8000:
@table @code
@item r@var{n}
@cindex Z8000 directives
@cindex directives, Z8000
-The Z8000 port of _AS__ includes these additional assembler directives,
+The Z8000 port of @value{as} includes these additional assembler directives,
for compatibility with other Z8000 assemblers. As shown, these do not
-begin with @samp{.} (unlike the ordinary _AS__ directives).
+begin with @samp{.} (unlike the ordinary @value{as} directives).
@table @code
@item segm
We had these goals, in descending priority:
@table @b
@item Accuracy.
-For every program composed by a compiler, @code{_AS__} should emit
+For every program composed by a compiler, @code{@value{as}} should emit
``correct'' code. This leaves some latitude in choosing addressing
modes, order of @code{relocation_info} structures in the object
file, @emph{etc}.
@item Speed, for usual case.
-By far the most common use of @code{_AS__} will be assembling compiler
+By far the most common use of @code{@value{as}} will be assembling compiler
emissions.
@item Upward compatibility for existing assembler code.
ask the compiler to write out human-readable code just so the
assembler can parse it back to binary.
-Assuming you use @code{_AS__} for human written programs: here are
+Assuming you use @code{@value{as}} for human written programs: here are
some ideas:
@itemize @bullet
@item
Document (here) @code{APP}.
@item
Take advantage of knowing no spaces except after opcode
-to speed up @code{_AS__}. (Modify @code{app.c} to flush useless spaces:
+to speed up @code{@value{as}}. (Modify @code{app.c} to flush useless spaces:
only keep space/tabs at begin of line or between 2
symbols.)
@item
@item
Split the assembler into parts so it can gobble direct binary
from @emph{e.g.} @code{cc}. It is silly for@code{cc} to compose text
-just so @code{_AS__} can parse it back to binary.
+just so @code{@value{as}} can parse it back to binary.
@item
Rewrite hash functions: I want a more modular, faster library.
@item
@end itemize
@section Sources
-@c The following files in the @file{_AS__} directory
+@c The following files in the @file{@value{as}} directory
@c are symbolic links to other files, of
@c the same name, in a different directory.
@c @itemize @bullet
@c @file{flonum_print.c}
@c @end itemize
-Here is a list of the source files in the @file{_AS__} directory.
+Here is a list of the source files in the @file{@value{as}} directory.
@table @file
@item app.c
little routines should probably all be put in one file.)
@item as.c
-Here you will find the main program of the assembler @code{_AS__}.
+Here you will find the main program of the assembler @code{@value{as}}.
@item expr.c
This is a branch office of @file{read.c}. This understands
-expressions, arguments. Inside @code{_AS__}, arguments are called
+expressions, arguments. Inside @code{@value{as}}, arguments are called
(expression) @emph{operands}. This is confusing, because we also talk
(elsewhere) about instruction @emph{operands}. Also, expression
operands are called @emph{quantities} explicitly to avoid confusion
@item input-file.c
This contains Operating system dependent source file reading
routines. Since error messages often say where we are in reading
-the source file, they live here too. Since @code{_AS__} is intended to
+the source file, they live here too. Since @code{@value{as}} is intended to
run under GNU and Unix only, this might be worth flushing. Anyway,
almost all C compilers support stdio.
@item output-file.c
This contains operating system dependent functions that write an
-object file for @code{_AS__}. See @file{input-file.c} above.
+object file for @code{@value{as}}. See @file{input-file.c} above.
@item read.c
-This implements all the directives of @code{_AS__}. This also deals
+This implements all the directives of @code{@value{as}}. This also deals
with passing input lines to the machine dependent part of the
assembler.
@item atof-ieee.c
This contains code to turn a flonum into a ieee literal constant.
-This is used by tye 680x0, 32x32, sparc, and i386 versions of @code{_AS__}.
+This is used by tye 680x0, 32x32, sparc, and i386 versions of @code{@value{as}}.
@item i386-opcode.h
This is the opcode-table for the i386 version of the assembler.
Vax opcode table.
@item vax.c
-Vax specific parts of @code{_AS__}. Also includes the former files
+Vax specific parts of @code{@value{as}}. Also includes the former files
@file{vax-ins-parse.c}, @file{vax-reg-parse.c} and @file{vip-op.c}.
@item atof-vax.c
Macros and function headers for reading in source files.
@item struct-symbol.h
-Structure definition and macros for dealing with the _AS__
+Structure definition and macros for dealing with the @value{as}
internal form of a symbol.
@item subsegs.h
@c REALLY OLD dump tape~dots{})
@c
@c The ~file{test/} directory is used for regression testing.
-@c After you modify ~@code{_AS__}, you can get a quick go/nogo
-@c confidence test by running the new ~@code{_AS__} over the source
+@c After you modify ~@code{@value{as}}, you can get a quick go/nogo
+@c confidence test by running the new ~@code{@value{as}} over the source
@c files in this directory. You use a shell script ~file{test/do}.
@c
@c The tests in this suite are evolving. They are not comprehensive.
@c They have, however, caught hundreds of bugs early in the debugging
-@c cycle of ~@code{_AS__}. Most test statements in this suite were naturally
-@c selected: they were used to demonstrate actual ~@code{_AS__} bugs rather
+@c cycle of ~@code{@value{as}}. Most test statements in this suite were naturally
+@c selected: they were used to demonstrate actual ~@code{@value{as}} bugs rather
@c than being written ~i{a prioi}.
@c
@c Another testing suggestion: over 30 bugs have been found simply by
-@c running examples from this manual through ~@code{_AS__}.
+@c running examples from this manual through ~@code{@value{as}}.
@c Some examples in this manual are selected
-@c to distinguish boundary conditions; they are good for testing ~@code{_AS__}.
+@c to distinguish boundary conditions; they are good for testing ~@code{@value{as}}.
@c
@c ~subsubsection Regression Testing
@c Each regression test involves assembling a file and comparing the
-@c actual output of ~@code{_AS__} to ``known good'' output files. Both
+@c actual output of ~@code{@value{as}} to ``known good'' output files. Both
@c the object file and the error/warning message file (stderr) are
-@c inspected. Optionally the ~@code{_AS__} exit status may be checked.
+@c inspected. Optionally the ~@code{@value{as}} exit status may be checked.
@c Discrepencies are reported. Each discrepency means either that
-@c you broke some part of ~@code{_AS__} or that the ``known good'' files
+@c you broke some part of ~@code{@value{as}} or that the ``known good'' files
@c are now out of date and should be changed to reflect the new
@c definition of ``good''.
@c
@c deleted. Likewise ~file{stdouterr} is removed if it exactly
@c matches a file ~file{stdouterr.good}. If file
@c ~file{status.good} is present, containing a decimal number
-@c before a newline, the exit status of ~@code{_AS__} is compared
+@c before a newline, the exit status of ~@code{@value{as}} is compared
@c to this number. If the status numbers are not equal, a file
@c ~file{status} is written to the directory, containing the
@c actual status as a decimal number followed by newline.
instructions, their opcodes, and what addressing modes they
support. If you do this right, the assembler and GDB can share
this file, and you'll only have to write it once. Note that
-while you're writing @code{_AS__}, you may want to use an
+while you're writing @code{@value{as}}, you may want to use an
independent program (if you have access to one), to make sure
-that @code{_AS__} is emitting the correct bytes. Since @code{_AS__}
+that @code{@value{as}} is emitting the correct bytes. Since @code{@value{as}}
and @code{GDB} share the opcode table, an incorrect opcode
table entry may make invalid bytes look OK when you disassemble
them with @code{GDB}.
@item int md_parse_option(char **optionPTR, int *argcPTR, char ***argvPTR)
This routine is called once for each option on the command line
-that the machine-independent part of @code{_AS__} does not
+that the machine-independent part of @code{@value{as}} does not
understand. This function should return non-zero if the option
pointed to by @var{optionPTR} is a valid option. If it is not
a valid option, this routine should return zero. The variables
@var{message} and any arguments it was passed.
@item as_bad(char *message,@dots{})
-This function should be called when @code{_AS__} encounters
-conditions that are bad enough that @code{_AS__} should not
+This function should be called when @code{@value{as}} encounters
+conditions that are bad enough that @code{@value{as}} should not
produce an object file, but should continue reading input and
printing warning and bad error messages.
pieces of object code cannot be determined until after assembly
is finished. (This means that the addresses of symbols cannot be
determined until assembly is finished.) In order to do this,
-@code{_AS__} stores the output bytes as @dfn{frags}.
+@code{@value{as}} stores the output bytes as @dfn{frags}.
Here is the definition of a frag (from @file{as.h})
@smallexample
@item fr_next
This is the next frag in the singly-linked list. This is
usually only needed by the machine-independent part of
-@code{_AS__}.
+@code{@value{as}}.
@end table
_fi__(0)
@cindex license
@cindex GPL
-@cindex copying @code{_AS__}
+@cindex copying @code{@value{as}}
@center Version 2, June 1991
@display
projects / binutils-gdb.git / commitdiff