This is a pre-alpha version of the GNU assembler, version 1.92.1

A number of things have changed and the wonderful world of gas looks
very different.  There's still a lot of irrelevant garbage lying
around that will be cleaned up soon.  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

At this point I believe gas to be ansi only code for most target
cpu's.  That is, there should be relatively few, if any host system
dependencies.

I believe hosting to work on the following:

	sun3
	sun4
	decstation
	rs6000
	at least some flavors of hpux
	sun386i
	most flavors of sysV
	vax ultrix

I believe that gas can currently be targetted for:

	sun3
	sun4
	ebmon29k
	nindy960
	i960-coff
	vxworks960
	vxworks68k
	sco386

Support for vax, ns32k, and vms are suffering from varying degrees of
bitrot.

----

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 THIS RELEASE gas should be reported directly to
raeburn@cygnus.com.  NOT to bug-gnu-utils@prep.ai.mit.edu.

If you report a bug in GAS, please remember to include:

A description of exactly what went wrong.

The type of machine GAS was running on (VAX, 68020, etc),

The Operating System GAS was running under.

The options given to GAS.

The actual input file that caused the problem.

It is silly to report a bug in GAS without including an input file for
GAS.  Don't ask us to generate the file just because you made it from
files you think we have access to.

1. You might be mistaken.
2. It might take us a lot of time to install things to regenerate that file.
3. We might get a different file from the one you got, and might not see any
bug.

To save us these delays and uncertainties, always send the input file
for the program that failed.

If the input file is very large, and you are on the internet, you may
want to make it avaliable for anonymous FTP instead of mailing it.  If you
do, include instructions for FTP'ing it in your bug report.
