mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-12-14 21:03:31 +08:00
7be1c4891a
* config-gas.com: Delete. * makefile.vms: Delete. * vmsconf.sh: Delete. * config/atof-tahoe.c: Delete. * config/m88k-opcode.h: Delete. * config/obj-bout.c: Delete. * config/obj-bout.h: Delete. * config/obj-hp300.c: Delete. * config/obj-hp300.h: Delete. * config/tc-a29k.c: Delete. * config/tc-a29k.h: Delete. * config/tc-h8500.c: Delete. * config/tc-h8500.h: Delete. * config/tc-m88k.c: Delete. * config/tc-m88k.h: Delete. * config/tc-tahoe.c: Delete. * config/tc-tahoe.h: Delete. * config/tc-tic80.c: Delete. * config/tc-tic80.h: Delete. * config/tc-w65.c: Delete. * config/tc-w65.h: Delete. * config/te-aux.h: Delete. * config/te-delt88.h: Delete. * config/te-delta.h: Delete. * config/te-dpx2.h: Delete. * config/te-hp300.h: Delete. * config/te-ic960.h: Delete. * config/vms-a-conf.h: Delete. * doc/c-a29k.texi: Delete. * doc/c-h8500.texi: Delete. * doc/c-m88k.texi: Delete. * README: Remove obsolete examples, and list of supported targets. * Makefile.am: Remove a29k, h8500, m88k, tahoe, tic80, w65, bout and hp300 support. (DEP_FLAGS): Don't define BFD_ASSEMBLER. * configure.in: Remove --enable-bfd-assembler, need_bfd, primary_bfd_gas. * configure.tgt: Remove a29k, h8300-coff, h8500-*, i960 non-elf, m68k non bfd, m88k, or32-coff, tic80-*, vax non-bfd, w65k-*, *-nindy. * as.c: Remove all non-BFD_ASSEMBLER code, support for above targets. * as.h: Likewise. * dw2gencfi.c: Likewise. * dwarf2dbg.c: Likewise. * ehopt.c: Likewise. * input-file.c: Likewise. * listing.c: Likewise. * literal.c: Likewise. * messages.c: Likewise. * obj.h: Likewise. * output-file.c: Likewise. * read.c: Likewise. * stabs.c: Likewise. * struc-symbol.h: Likewise. * subsegs.c: Likewise. * subsegs.h: Likewise. * symbols.c: Likewise. * symbols.h: Likewise. * tc.h: Likewise. * write.c: Likewise. * write.h: Likewise. * config/aout_gnu.h: Likewise. * config/obj-aout.c: Likewise. * config/obj-aout.h: Likewise. * config/obj-coff.c: Likewise. * config/obj-coff.h: Likewise. * config/obj-evax.h: Likewise. * config/obj-ieee.h: Likewise. * config/tc-arm.c: Likewise. * config/tc-arm.h: Likewise. * config/tc-avr.c: Likewise. * config/tc-avr.h: Likewise. * config/tc-crx.h: Likewise. * config/tc-d10v.h: Likewise. * config/tc-d30v.h: Likewise. * config/tc-dlx.h: Likewise. * config/tc-fr30.h: Likewise. * config/tc-frv.h: Likewise. * config/tc-h8300.c: Likewise. * config/tc-h8300.h: Likewise. * config/tc-hppa.h: Likewise. * config/tc-i370.h: Likewise. * config/tc-i386.c: Likewise. * config/tc-i386.h: Likewise. * config/tc-i860.h: Likewise. * config/tc-i960.c: Likewise. * config/tc-i960.h: Likewise. * config/tc-ip2k.h: Likewise. * config/tc-iq2000.h: Likewise. * config/tc-m32c.h: Likewise. * config/tc-m32r.h: Likewise. * config/tc-m68hc11.h: Likewise. * config/tc-m68k.c: Likewise. * config/tc-m68k.h: Likewise. * config/tc-maxq.c: Likewise. * config/tc-maxq.h: Likewise. * config/tc-mcore.c: Likewise. * config/tc-mcore.h: Likewise. * config/tc-mn10200.h: Likewise. * config/tc-mn10300.c: Likewise. * config/tc-mn10300.h: Likewise. * config/tc-ms1.h: Likewise. * config/tc-msp430.c: Likewise. * config/tc-msp430.h: Likewise. * config/tc-ns32k.c: Likewise. * config/tc-ns32k.h: Likewise. * config/tc-openrisc.h: Likewise. * config/tc-or32.c: Likewise. * config/tc-or32.h: Likewise. * config/tc-ppc.c: Likewise. * config/tc-ppc.h: Likewise. * config/tc-s390.h: Likewise. * config/tc-sh.c: Likewise. * config/tc-sh.h: Likewise. * config/tc-sparc.c: Likewise. * config/tc-tic30.c: Likewise. * config/tc-tic30.h: Likewise. * config/tc-tic4x.c: Likewise. * config/tc-tic4x.h: Likewise. * config/tc-tic54x.c: Likewise. * config/tc-tic54x.h: Likewise. * config/tc-v850.h: Likewise. * config/tc-vax.c: Likewise. * config/tc-vax.h: Likewise. * config/tc-xstormy16.h: Likewise. * config/tc-xtensa.h: Likewise. * config/tc-z8k.c: Likewise. * config/tc-z8k.h: Likewise. * config/vms-a-conf.h * doc/Makefile.am: Likewise. * doc/all.texi: Likewise. * doc/as.texinfo: Likewise. * doc/Makefile.in: Regenerate. * Makefile.in: Regenerate. * configure: Regenerate. * config.in: Regenerate. * po/POTFILES.in: Regenerate.
165 lines
6.0 KiB
Plaintext
165 lines
6.0 KiB
Plaintext
README for GAS
|
|
|
|
A number of things have changed since version 1 and the wonderful
|
|
world of gas looks very different. There's still a lot of irrelevant
|
|
garbage lying around that will be cleaned up in time. Documentation
|
|
is scarce, as are logs of the changes made since the last gas release.
|
|
My apologies, and I'll try to get something useful.
|
|
|
|
Unpacking and Installation - Summary
|
|
====================================
|
|
|
|
See ../binutils/README.
|
|
|
|
To build just the assembler, make the target all-gas.
|
|
|
|
Documentation
|
|
=============
|
|
|
|
The GAS release includes texinfo source for its manual, which can be processed
|
|
into `info' or `dvi' forms.
|
|
|
|
The DVI form is suitable for printing or displaying; the commands for doing
|
|
this vary from system to system. On many systems, `lpr -d' will print a DVI
|
|
file. On others, you may need to run a program such as `dvips' to convert the
|
|
DVI file into a form your system can print.
|
|
|
|
If you wish to build the DVI file, you will need to have TeX installed on your
|
|
system. You can rebuild it by typing:
|
|
|
|
cd gas/doc
|
|
make as.dvi
|
|
|
|
The Info form is viewable with the GNU Emacs `info' subsystem, or the
|
|
stand-alone `info' program, available as part of the GNU Texinfo distribution.
|
|
To build the info files, you will need the `makeinfo' program. Type:
|
|
|
|
cd gas/doc
|
|
make info
|
|
|
|
Specifying names for hosts and targets
|
|
======================================
|
|
|
|
The specifications used for hosts and targets in the `configure'
|
|
script are based on a three-part naming scheme, but some short
|
|
predefined aliases are also supported. The full naming scheme encodes
|
|
three pieces of information in the following pattern:
|
|
|
|
ARCHITECTURE-VENDOR-OS
|
|
|
|
For example, you can use the alias `sun4' as a HOST argument or in a
|
|
`--target=TARGET' option. The equivalent full name is
|
|
`sparc-sun-sunos4'.
|
|
|
|
The `configure' script accompanying GAS does not provide any query
|
|
facility to list all supported host and target names or aliases.
|
|
`configure' calls the Bourne shell script `config.sub' to map
|
|
abbreviations to full names; you can read the script, if you wish, or
|
|
you can use it to test your guesses on abbreviations--for example:
|
|
|
|
% sh config.sub i386v
|
|
i386-unknown-sysv
|
|
% sh config.sub i786v
|
|
Invalid configuration `i786v': machine `i786v' not recognized
|
|
|
|
|
|
`configure' options
|
|
===================
|
|
|
|
Here is a summary of the `configure' options and arguments that are
|
|
most often useful for building GAS. `configure' also has several other
|
|
options not listed here.
|
|
|
|
configure [--help]
|
|
[--prefix=DIR]
|
|
[--srcdir=PATH]
|
|
[--host=HOST]
|
|
[--target=TARGET]
|
|
[--with-OPTION]
|
|
[--enable-OPTION]
|
|
|
|
You may introduce options with a single `-' rather than `--' if you
|
|
prefer; but you may abbreviate option names if you use `--'.
|
|
|
|
`--help'
|
|
Print a summary of the options to `configure', and exit.
|
|
|
|
`-prefix=DIR'
|
|
Configure the source to install programs and files under directory
|
|
`DIR'.
|
|
|
|
`--srcdir=PATH'
|
|
Look for the package's source code in directory DIR. Usually
|
|
`configure' can determine that directory automatically.
|
|
|
|
`--host=HOST'
|
|
Configure GAS to run on the specified HOST. Normally the
|
|
configure script can figure this out automatically.
|
|
|
|
There is no convenient way to generate a list of all available
|
|
hosts.
|
|
|
|
`--target=TARGET'
|
|
Configure GAS for cross-assembling programs for the specified
|
|
TARGET. Without this option, GAS is configured to assemble .o files
|
|
that run on the same machine (HOST) as GAS itself.
|
|
|
|
There is no convenient way to generate a list of all available
|
|
targets.
|
|
|
|
`--enable-OPTION'
|
|
These flags tell the program or library being configured to
|
|
configure itself differently from the default for the specified
|
|
host/target combination. See below for a list of `--enable'
|
|
options recognized in the gas distribution.
|
|
|
|
`configure' accepts other options, for compatibility with configuring
|
|
other GNU tools recursively; but these are the only options that affect
|
|
GAS or its supporting libraries.
|
|
|
|
The `--enable' options recognized by software in the gas distribution are:
|
|
|
|
`--enable-targets=...'
|
|
This causes one or more specified configurations to be added to those for
|
|
which BFD support is compiled. Currently gas cannot use any format other
|
|
than its compiled-in default, so this option is not very useful.
|
|
|
|
`--enable-bfd-assembler'
|
|
This causes the assembler to use the new code being merged into it to use
|
|
BFD data structures internally, and use BFD for writing object files.
|
|
For most targets, this isn't supported yet. For most targets where it has
|
|
been done, it's already the default. So generally you won't need to use
|
|
this option.
|
|
|
|
Compiler Support Hacks
|
|
======================
|
|
|
|
On a few targets, the assembler has been modified to support a feature
|
|
that is potentially useful when assembling compiler output, but which
|
|
may confuse assembly language programmers. If assembler encounters a
|
|
.word pseudo-op of the form symbol1-symbol2 (the difference of two
|
|
symbols), and the difference of those two symbols will not fit in 16
|
|
bits, the assembler will create a branch around a long jump to
|
|
symbol1, and insert this into the output directly before the next
|
|
label: The .word will (instead of containing garbage, or giving an
|
|
error message) contain (the address of the long jump)-symbol2. This
|
|
allows the assembler to assemble jump tables that jump to locations
|
|
very far away into code that works properly. If the next label is
|
|
more than 32K away from the .word, you lose (silently); RMS claims
|
|
this will never happen. If the -K option is given, you will get a
|
|
warning message when this happens.
|
|
|
|
|
|
REPORTING BUGS IN GAS
|
|
=====================
|
|
|
|
Bugs in gas should be reported to:
|
|
|
|
bug-binutils@gnu.org.
|
|
|
|
They may be cross-posted to gcc-bugs@gnu.org if they affect the use of
|
|
gas with gcc. They should not be reported just to gcc-bugs, since not
|
|
all of the maintainers read that list.
|
|
|
|
See ../binutils/README for what we need in a bug report.
|