diff options
Diffstat (limited to 'gas')
36 files changed, 6118 insertions, 1149 deletions
diff --git a/gas/Makefile-intel b/gas/Makefile-intel new file mode 100755 index 0000000..54487c2 --- /dev/null +++ b/gas/Makefile-intel @@ -0,0 +1,146 @@ +#----------------------------------------------------------------------------- +# Makefile for gas960 +# +# $Id$ +#----------------------------------------------------------------------------- + +# The following two lines should be uncommented for system V (i386v). +#__i386v__#USG = -DUSG +#__i386v__#LIBS = -lmalloc -lPW + +# The following two lines should be uncommented for HP-UX +#__hp9000__#USG = -DUSG + +# The following line should be uncommented for Macintosh A/UX. +#__mac-aux__#USG = -DUSG + +#Always build with static libraries on Sun systems +#__sun3__#LDFLAGS = -Bstatic +#__sun386i__#LDFLAGS = -Bstatic +#__sun4__#LDFLAGS = -Bstatic + +# Essential under System V, harmless elsewhere +SHELL = /bin/sh + +TARG = gas960 +OPT = -g +IPATH = ../../include +CFLAGS = ${OPT} ${USG} -DI80960 -I${IPATH} + + +OBJS = app.o append.o as.o atof-generic.o bignum-copy.o expr.o \ + flonum-const.o flonum-copy.o flonum-mult.o frags.o gdb-blocks.o \ + gdb-file.o gdb-lines.o gdb-symbols.o gdb.o hash.o hex-value.o \ + input-file.o input-scrub.o messages.o obstack.o output-file.o read.o \ + strstr.o subsegs.o symbols.o version.o write.o xmalloc.o xrealloc.o + +# Note that we use the 386 floating-point support for the i80960 +I960OBJ = i960.o i960-opcode.o atof-i386.o + +gas960: ${OBJS} ${I960OBJ} VERSION + make ver960.o + ${CC} -o gas960 ${LDFLAGS} ${OBJS} ${I960OBJ} ver960.o ${LIBS} + +hash.o: hash.c + ${CC} -c ${CFLAGS} -Derror=as_fatal hash.c + +xmalloc.o: xmalloc.c + ${CC} -c ${CFLAGS} -Derror=as_fatal xmalloc.c + +xrealloc.o: xrealloc.c + ${CC} -c ${CFLAGS} -Derror=as_fatal xrealloc.c + +app.o: as.h + +as.o: ${IPATH}/b.out.h as.h read.h struc-symbol.h write.h +atof-generic.o: flonum.h +bignum-copy.o: bignum.h +expr.o: ${IPATH}/b.out.h as.h expr.h flonum.h obstack.h read.h +expr.o: struc-symbol.h symbols.h +flonum-const.o: flonum.h +flonum-copy.o: flonum.h +flonum-mult.o: flonum.h +flonum-normal.o:flonum.h +flonum-print.o: flonum.h +frags.o: ${IPATH}/b.out.h as.h frags.h obstack.h struc-symbol.h subsegs.h +gdb.o: as.h +gdb-blocks.o: as.h +gdb-lines.o: as.h frags.h obstack.h +gdb-symbols.o: ${IPATH}/b.out.h as.h struc-symbol.h +hash.o: hash.h +i960.o: as.h ${IPATH}/b.out.h expr.h flonum.h frags.h hash.h +i960.o: i960-opcode.h md.h obstack.h struc-symbol.h write.h +i960-opcode.o: i960-opcode.h +input-file.o: input-file.h +input-scrub.o: as.h input-file.h read.h +messages.o: as.h +obstack.o: obstack.h +read.o: ${IPATH}/b.out.h as.h expr.h flonum.h frags.h hash.h md.h +read.o: obstack.h read.h struc-symbol.h symbols.h +subsegs.o: ${IPATH}/b.out.h as.h frags.h obstack.h struc-symbol.h subsegs.h +subsegs.o: write.h +symbols.o: ${IPATH}/b.out.h as.h frags.h hash.h obstack.h struc-symbol.h +symbols.o: symbols.h +write.o: ${IPATH}/b.out.h as.h md.h obstack.h struc-symbol.h subsegs.h +write.o: symbols.h write.h + +flonum.h: bignum.h + +#----------------------------------------------------------------------------- +# 'STANDARD' GNU/960 TARGETS BELOW THIS POINT +# +# 'VERSION' file must be present and contain a string of the form "x.y" +#----------------------------------------------------------------------------- + +ver960.c: FORCE + rm -f ver960.c + echo "char ${TARG}_ver[]= \"${TARG} `cat VERSION`, `date`\";" > ver960.c + + +# This target should be invoked before building a new release. +# 'VERSION' file must be present and contain a string of the form "x.y" +# +roll: + @V=`cat VERSION` ; \ + MAJ=`sed 's/\..*//' VERSION` ; \ + MIN=`sed 's/.*\.//' VERSION` ; \ + V=$$MAJ.`expr $$MIN + 1` ; \ + rm -f VERSION ; \ + echo $$V >VERSION ; \ + echo Version $$V + +# Dummy target to force execution of dependent targets. +# +FORCE: + +# 'G960BASE' will be defined at invocation +install: + make ${TARG} OPT=-O + strip ${TARG} + rm -f ${G960BASE}/bin/${TARG} + mv ${TARG} ${G960BASE}/bin/${TARG} + +clean: + rm -f ${TARG} *.o core + +# Target to uncomment host-specific lines in this makefile. Such lines must +# have the following string beginning in column 1: #__<hostname>__# +# Original Makefile is backed up as 'Makefile.old'. +# +# Invoke with: make make HOST=xxx +# +make: + -@if test $(HOST)x = x ; then \ + echo 'Specify "make make HOST=???"'; \ + exit 1; \ + fi ; \ + grep -s "^#The next line was generated by 'make make'" Makefile; \ + if test $$? = 0 ; then \ + echo "Makefile has already been processed with 'make make'";\ + exit 1; \ + fi ; \ + mv -f Makefile Makefile.old; \ + echo "#The next line was generated by 'make make'" >Makefile ; \ + echo "HOST=$(HOST)" >>Makefile ; \ + echo >>Makefile ; \ + sed "s/^#__$(HOST)__#//" < Makefile.old >>Makefile diff --git a/gas/Makefile.generic b/gas/Makefile.generic new file mode 100755 index 0000000..1bf57a3 --- /dev/null +++ b/gas/Makefile.generic @@ -0,0 +1,586 @@ +host = generic +target = generic +# Makefile for GNU Assembler +# Copyright (C) 1987, 1988, 1990, 1991 Free Software Foundation, Inc. + +#This file is part of GNU GAS. + +#GNU GAS is free software; you can redistribute it and/or modify +#it under the terms of the GNU General Public License as published by +#the Free Software Foundation; either version 1, or (at your option) +#any later version. + +#GNU GAS is distributed in the hope that it will be useful, +#but WITHOUT ANY WARRANTY; without even the implied warranty of +#MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +#GNU General Public License for more details. + +#You should have received a copy of the GNU General Public License +#along with GNU GAS; see the file COPYING. If not, write to +#the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. + +# $Id$ + +# The targets for external use include: +# all, doc, proto, install, uninstall, includes, TAGS, +# clean, cleanconfig, realclean, stage1, stage2, stage3, stage4. + +# Variables that exist for you to override. +# See below for how to change them for certain systems. + +ALLOCA = +CFLAGS = -g $(XCFLAGS) # -I$(srcdir)/../include +INTERNAL_CFLAGS = $(CROSS) +OLDCC = cc +BISON = bison +BISONFLAGS = -v +AR = ar +OLDAR_FLAGS = qc +AR_FLAGS = rc +SHELL = /bin/sh +# on sysV, define this as cp. +INSTALL = install -c +# These permit overriding just for certain files. +INSTALL_PROGRAM = $(INSTALL) +INSTALL_FILE = $(INSTALL) + +# Define this as & to perform parallel make on a Sequent. +# Note that this has some bugs, and it seems currently necessary +# to compile all the gen* files first by hand to avoid erroneous results. +P = + +# How to invoke ranlib. +RANLIB = ranlib +# Test to use to see whether ranlib exists on the system. +RANLIB_TEST = [ -f /usr/bin/ranlib -o -f /bin/ranlib ] + +# CFLAGS for use with OLDCC, for compiling gnulib. +# NOTE: -O does not work on some Unix systems! +CCLIBFLAGS = -O + +# Version of ar to use when compiling gnulib. +OLDAR = ar + +version=`./gcc -dumpversion` + +# Directory where sources are, from where we are. +srcdir = . +# Common prefix for installation directories. +# NOTE: This directory must exist when you start installation. +prefix = /usr/local +# Directory in which to put the executable for the command `gcc' +bindir = $(prefix)/bin +# Directory in which to put the directories used by the compiler. +libdir = $(prefix)/lib +# Directory in which the compiler finds executables, libraries, etc. +libsubdir = $(libdir)/gcc/$(target)/$(version) +# Number to put in man-page filename. +manext = 1 +# Directory in which to put man pages. +mandir = $(prefix)/man/man$(manext) + +# Additional system libraries to link with. +CLIB= + +# Change this to a null string if obstacks are installed in the +# system library. +OBSTACK=obstack.o + +# Specify the rule for actually making gnulib. +GNULIB = gnulib.portable + +# Specify the rule for actually making gnulib2. +GNULIB2 = gnulib2.portable + +# List of extra C and assembler files to add to gnulib. +# Assembler files should have names ending in `.asm'. +LIBFUNCS_EXTRA = + +# Program to convert libraries. +LIBCONVERT = + +# Control whether header files are installed. +INSTALL_HEADERS=install-headers + +# Change this to empty to prevent installing limits.h +LIMITS_H = limits.h + +# Directory to link to, when using the target `maketest'. +DIR = ../gcc + +# For better debugging under COFF, define SEPARATE_AUX_OUTPUT in config.h +# and define the following variable as `aux-output2.c' in make-... +AUX_OUTPUT2 = + +# Flags to use when cross-building GCC. +# Prefix to apply to names of object files when using them +# to run on the machine we are compiling on. +HOST_PREFIX= +# Prefix to apply to names of object files when compiling them +# to run on the machine we are compiling on. +# The default for this variable is chosen to keep these rules +# out of the way of the other rules for compiling the same source files. +HOST_PREFIX_1=loser- +HOST_CC=$(CC) +HOST_CFLAGS=$(ALL_CFLAGS) +HOST_LDFLAGS=$(LDFLAGS) +HOST_CPPFLAGS=$(CPPFLAGS) + +# Choose the real default target. +ALL=bootstrap + +# End of variables for you to override. + +# Lists of files for various purposes. + +REAL_SOURCES = \ + $(srcdir)/app.c \ + $(srcdir)/as.c \ + $(srcdir)/atof-generic.c \ + $(srcdir)/bignum-copy.c \ + $(srcdir)/cond.c \ + $(srcdir)/expr.c \ + $(srcdir)/flonum-const.c \ + $(srcdir)/flonum-copy.c \ + $(srcdir)/flonum-mult.c \ + $(srcdir)/frags.c \ + $(srcdir)/hash.c \ + $(srcdir)/hex-value.c \ + $(srcdir)/input-file.c \ + $(srcdir)/input-scrub.c \ + $(srcdir)/messages.c \ + $(srcdir)/output-file.c \ + $(srcdir)/read.c \ + $(srcdir)/strstr.c \ + $(srcdir)/subsegs.c \ + $(srcdir)/symbols.c \ + $(srcdir)/version.c \ + $(srcdir)/write.c \ + $(srcdir)/xmalloc.c \ + $(srcdir)/xrealloc.c + +# in an expedient order +LINKED_SOURCES = \ + targ-cpu.c \ + obj-format.c \ + atof-targ.c + +SOURCES = $(LINKED_SOURCES) $(REAL_SOURCES) + +REAL_HEADERS = \ + $(srcdir)/as.h \ + $(srcdir)/bignum.h \ + $(srcdir)/expr.h \ + $(srcdir)/flonum.h \ + $(srcdir)/frags.h \ + $(srcdir)/hash.h \ + $(srcdir)/input-file.h \ + $(srcdir)/tc.h \ + $(srcdir)/obj.h \ + $(srcdir)/read.h \ + $(srcdir)/reloc.h \ + $(srcdir)/struc-symbol.h \ + $(srcdir)/subsegs.h \ + $(srcdir)/symbols.h \ + $(srcdir)/syscalls.h \ + $(srcdir)/write.h + +LINKED_HEADERS = \ + a.out.gnu.h \ + a.out.h \ + host.h \ + targ-env.h \ + targ-cpu.h \ + obj-format.h \ + atof-targ.h + +HEADERS = $(LINKED_HEADERS) $(REAL_HEADERS) + +OBJS = \ + targ-cpu.o \ + obj-format.o \ + atof-targ.o \ + app.o \ + as.o \ + atof-generic.o \ + bignum-copy.o \ + cond.o \ + expr.o \ + flonum-const.o \ + flonum-copy.o \ + flonum-mult.o \ + frags.o \ + hash.o \ + hex-value.o \ + input-file.o \ + input-scrub.o \ + messages.o \ + output-file.o \ + read.o \ + strstr.o \ + subsegs.o \ + symbols.o \ + version.o \ + write.o \ + xmalloc.o \ + xrealloc.o + +# Definition of `all' is here so that new rules inserted by sed +# do not specify the default target. +# The real definition is under `all.internal'. + +all: $(ALL) + +# sed inserts variable overrides after the following line. +#### + +# Now figure out from those variables how to compile and link. + +# This is the variable actually used when we compile. +ALL_CFLAGS = $(INTERNAL_CFLAGS) $(CFLAGS) + +# Even if ALLOCA is set, don't use it if compiling with GCC. +USE_ALLOCA= `if [ x"${CC}" = x"${OLDCC}" ] ; then echo ${ALLOCA}; else true; fi` +USE_HOST_ALLOCA= `if [ x"${CC}" = x"${OLDCC}" ] ; then echo ${HOST_PREFIX}${ALLOCA}; else true; fi` + +# Dependency on obstack, alloca, malloc or whatever library facilities +# are not installed in the system libraries. +# We don't use USE_ALLOCA because backquote expansion doesn't work in deps. +LIBDEPS= $(OBSTACK) $(ALLOCA) $(MALLOC) + +# Likewise, for use in the tools that must run on this machine +# even if we are cross-building GCC. +# We don't use USE_ALLOCA because backquote expansion doesn't work in deps. +HOST_LIBDEPS= $(HOST_PREFIX)$(OBSTACK) $(HOST_PREFIX)$(ALLOCA) $(HOST_PREFIX)$(MALLOC) + +# How to link with both our special library facilities +# and the system's installed libraries. +LIBS = $(OBSTACK) $(USE_ALLOCA) $(MALLOC) $(CLIB) + +# Likewise, for use in the tools that must run on this machine +# even if we are cross-building GCC. +HOST_LIBS = $(HOST_PREFIX)$(OBSTACK) $(USE_HOST_ALLOCA) $(HOST_PREFIX)$(MALLOC) $(CLIB) + +# Specify the directories to be searched for header files. +# Both . and srcdir are used, in that order, +# so that tm.h and config.h will be found in the compilation +# subdirectory rather than in the source directory. +INCLUDES = -I. -I$(srcdir) -I$(srcdir)/config +SUBDIR_INCLUDES = -I.. -I../$(srcdir) -I../$(srcdir)/config + +# Always use -I$(srcdir)/config when compiling. +.c.o: + $(CC) -c $(ALL_CFLAGS) $(CPPFLAGS) $(INCLUDES) $< + +# This tells GNU make version 3 not to export all the variables +# defined in this file into the environment. +.NOEXPORT: + +# Files to be copied away after each stage in building. +STAGE_GCC=gcc +STAGESTUFF = *.o gas + +# The files that "belong" in CONFIG_H are deliberately omitted +# because having them there would not be useful in actual practice. +# All they would do is cause complete recompilation every time +# one of the machine description files is edited. +# That may or may not be what one wants to do. +# If it is, rm *.o is an easy way to do it. +# CONFIG_H = config.h tm.h +CONFIG_H = + +gas: $(OBJS) $(LIBDEPS) + $(CC) $(ALL_CFLAGS) $(LDFLAGS) -o gas $(OBJS) $(LIBS) + +all.internal: native +# This is what is made with the host's compiler if making a cross assembler. +native: config.status gas + +config.status: + @echo You must configure gas. Look at the INSTALL file for details. + @false + +compilations: ${OBJS} + +# Compiling object files from source files. + +# Note that dependencies on obstack.h are not written +# because that file is not part of GAS. + +app.o : app.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h +as.o : as.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h +atof-generic.o : atof-generic.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h +bignum-copy.o : bignum-copy.c as.h host.h \ + targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h +cond.o : cond.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + obstack.h +debug.o : debug.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + subsegs.h +expr.o : expr.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + obstack.h +flonum-const.o : flonum-const.c flonum.h bignum.h +flonum-copy.o : flonum-copy.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h +flonum-mult.o : flonum-mult.c flonum.h bignum.h +frags.o : frags.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + subsegs.h obstack.h +hash.o : hash.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h +hex-value.o : hex-value.c +input-file.o : input-file.c as.h host.h \ + targ-env.h obj-format.h targ-cpu.h \ + struc-symbol.h reloc.h write.h flonum.h bignum.h expr.h \ + frags.h hash.h read.h symbols.h tc.h obj.h input-file.h +input-scrub.o : input-scrub.c /usr/include/errno.h /usr/include/sys/errno.h \ + as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + input-file.h +messages.o : messages.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h +obstack.o : obstack.c obstack.h +output-file.o : output-file.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + output-file.h +read.o : read.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + obstack.h +strstr.o : strstr.c +subsegs.o : subsegs.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + subsegs.h obstack.h +symbols.o : symbols.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + obstack.h subsegs.h +version.o : version.c +write.o : write.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h symbols.h tc.h obj.h \ + subsegs.h obstack.h output-file.h +xmalloc.o : xmalloc.c +xrealloc.o : xrealloc.c +atof-targ.o : atof-targ.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h \ + symbols.h tc.h obj.h +obj-format.o : obj-format.c as.h host.h targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h \ + symbols.h tc.h obj.h obstack.h +targ-cpu.o : targ-cpu.c targ-env.h obj-format.h \ + targ-cpu.h struc-symbol.h reloc.h \ + write.h flonum.h bignum.h expr.h frags.h hash.h read.h \ + symbols.h tc.h obj.h obstack.h + +# Normally this target is not used; but it is used if you +# define ALLOCA=alloca.o. In that case, you must get a suitable alloca.c +# from the GNU Emacs distribution. +# Note some machines won't allow $(CC) without -S on this source file. +alloca.o: alloca.c + $(CC) $(ALL_CFLAGS) $(CPPFLAGS) -S `echo $(srcdir)/alloca.c | sed 's,^\./,,'` + as alloca.s -o alloca.o + +# Compile the libraries to be used by gen*. +# If we are not cross-building, gen* use the same .o's that cc1 will use, +# and HOST_PREFIX_1 is `foobar', just to ensure these rules don't conflict +# with the rules for rtl.o, alloca.o, etc. +$(HOST_PREFIX_1)alloca.o: alloca.c + rm -f $(HOST_PREFIX)alloca.c + cp $(srcdir)/alloca.c $(HOST_PREFIX)alloca.c + $(HOST_CC) -c $(HOST_CFLAGS) $(HOST_CPPFLAGS) $(INCLUDES) $(HOST_PREFIX)alloca.c + +$(HOST_PREFIX_1)obstack.o: obstack.c + rm -f $(HOST_PREFIX)obstack.c + cp $(srcdir)/obstack.c $(HOST_PREFIX)obstack.c + $(HOST_CC) -c $(HOST_CFLAGS) $(HOST_CPPFLAGS) $(INCLUDES) $(HOST_PREFIX)obstack.c + +$(HOST_PREFIX_1)malloc.o: malloc.c + rm -f $(HOST_PREFIX)malloc.c + cp $(srcdir)/malloc.c $(HOST_PREFIX)malloc.c + $(HOST_CC) -c $(HOST_CFLAGS) $(HOST_CPPFLAGS) $(INCLUDES) $(HOST_PREFIX)malloc.c + +# Remake the info files. + +doc: $(srcdir)/gas.info + +$(srcdir)/gas.info: $(srcdir)/gas.texinfo + makeinfo `echo $(srcdir)/gas.texinfo | sed 's,^\./,,'` + + +# Deletion of files made during compilation. +# There are three levels of this: `clean', `cleanconfig' and `realclean'. +# `clean' deletes what you want to delete ordinarily to save space. +# This is most, but not all, of the files made by compilation. +# `cleanconfig' also deletes everything depending +# on the choice of config files. +# `realclean' also deletes everything that could be regenerated automatically. + +clean: + -rm -f $(STAGESTUFF) +# Delete the temporary source copies for cross compilation. + -rm -f $(HOST_PREFIX_1)alloca.c $(HOST_PREFIX_1)malloc.c + -rm -f $(HOST_PREFIX_1)obstack.c +# Delete the stamp files except stamp-gnulib2. + -rm -f core + +# Like clean but also delete the links made to configure gas. +cleanconfig: clean + -rm -f config.status Makefile host.h targ-env.h + -rm -f targ-cpu.h targ-cpu.c + -rm -f obj-format.h obj-format.c + -rm -f atof-targ.c + +# Get rid of every file that's generated from some other file (except INSTALL). +realclean: cleanconfig + -rm -f gas.aux gas.cps gas.fns gas.info gas.kys gas.pgs gas.tps gas.vrs + -rm -f TAGS + -rm -f gas.info* gas.?? gas.??s gas.log gas.toc gas.*aux + -rm -f *.dvi + +# Entry points `install', `includes' and `uninstall'. + +# Copy the files into directories where they will be run. +install: + $(INSTALL_PROGRAM) gas $(bindir)/as + +# Create the installation directory. +install-dir: + -mkdir $(libdir) + -mkdir $(libdir)/gcc + -mkdir $(libdir)/gcc/$(target) + -mkdir $(libdir)/gcc/$(target)/$(version) + +# Install the compiler executables built during cross compilation. +install-cross: native install-dir + -if [ -f cc1 ] ; then $(INSTALL_PROGRAM) cc1 $(libsubdir)/cc1; else true; fi + -if [ -f cc1plus ] ; then $(INSTALL_PROGRAM) cc1plus $(libsubdir)/cc1plus; else true; fi + $(INSTALL_PROGRAM) cpp $(libsubdir)/cpp + ./gcc -dumpspecs > $(libsubdir)/specs + $(INSTALL_PROGRAM) gcc $(bindir)/gcc + +# Install the man pages. +install-man: install-dir $(srcdir)/gcc.1 protoize.1 unprotoize.1 + $(INSTALL_FILE) $(srcdir)/gcc.1 $(mandir)/gcc.$(manext) + chmod a-x $(mandir)/gcc.$(manext) + $(INSTALL_FILE) $(srcdir)/protoize.1 $(mandir)/protoize.$(manext) + chmod a-x $(mandir)/protoize.$(manext) + $(INSTALL_FILE) $(srcdir)/unprotoize.1 $(mandir)/unprotoize.$(manext) + chmod a-x $(mandir)/unprotoize.$(manext) + +# Cancel installation by deleting the installed files. +uninstall: + -rm -rf $(libsubdir) + -rm -rf $(bindir)/gas + -rm -rf $(mandir)/gas.$(manext) + + +# These exist for maintenance purposes. + +tags TAGS: force + etags $(REAL_SOURCES) $(REAL_HEADERS) README Makefile config/*.[hc] + +bootstrap: gas force + $(MAKE) stage1 + $(MAKE) CC="$(CC)" CFLAGS="-O -Bstage1/ $(CFLAGS)" libdir=$(libdir) ALLOCA= gas + $(MAKE) stage2 + $(MAKE) CC="$(CC)" CFLAGS="-O -Bstage2/ $(CFLAGS)" libdir=$(libdir) ALLOCA= gas + for i in *.o; do cmp $$i stage2/$$i; done + +bootstrap2: force + $(MAKE) CC="$(CC)" CFLAGS="-O -Bstage1/ $(CFLAGS)" libdir=$(libdir) ALLOCA= gas + $(MAKE) stage2 + $(MAKE) CC="$(CC)" CFLAGS="-O -Bstage2/ $(CFLAGS)" libdir=$(libdir) ALLOCA= gas + for i in *.o; do cmp $$i stage2/$$i; done + +bootstrap3: force + $(MAKE) CC="$(CC)" CFLAGS="-O -Bstage2/ $(CFLAGS)" libdir=$(libdir) ALLOCA= gas + for i in *.o; do cmp $$i stage2/$$i; done + +# Copy the object files from a particular stage into a subdirectory. +stage1: force + -mkdir stage1 + -mv $(STAGESTUFF) stage1 + -(cd stage1 ; ln -s gas as) + +stage2: force + -mkdir stage2 + -mv $(STAGESTUFF) stage2 + -(cd stage2 ; ln -s gas as) + + +stage3: force + -mkdir stage3 + -mv $(STAGESTUFF) $(STAGE_GCC) stage3 + -rm -f stage3/gnulib + -cp gnulib stage3 + -if $(RANLIB_TEST) ; then $(RANLIB) stage3/gnulib; else true; fi + +stage4: force + -mkdir stage4 + -mv $(STAGESTUFF) $(STAGE_GCC) stage4 + -rm -f stage4/gnulib + -cp gnulib stage4 + -if $(RANLIB_TEST) ; then $(RANLIB) stage4/gnulib; else true; fi + +# Copy just the executable files from a particular stage into a subdirectory, +# and delete the object files. Use this if you're just verifying a version +# that is pretty sure to work, and you are short of disk space. +risky-stage1: force + -mkdir stage1 + -mv cc1 cpp cccp gcc stage1 + -rm -f stage1/gnulib + -cp gnulib stage1 && $(RANLIB) stage1/gnulib + -make clean + +risky-stage2: force + -mkdir stage2 + -mv cc1 cpp cccp gcc stage2 + -rm -f stage2/gnulib + -cp gnulib stage2 && $(RANLIB) stage2/gnulib + -make clean + +risky-stage3: force + -mkdir stage3 + -mv cc1 cpp cccp gcc stage3 + -rm -f stage3/gnulib + -cp gnulib stage3 && $(RANLIB) stage3/gnulib + -make clean + +risky-stage4: force + -mkdir stage4 + -mv cc1 cpp cccp gcc stage4 + -rm -f stage4/gnulib + -cp gnulib stage4 && $(RANLIB) stage4/gnulib + -make clean + +#In GNU Make, ignore whether `stage*' exists. +.PHONY: stage1 stage2 stage3 stage4 clean realclean TAGS bootstrap +.PHONY: risky-stage1 risky-stage2 risky-stage3 risky-stage4 + +force: + +Makefile: $(srcdir)/Makefile.in $(srcdir)/configure + $(srcdir)/configure.was -srcdir=$(srcdir) -host=$(host) $(target) diff --git a/gas/a.out.gnu.h b/gas/a.out.gnu.h new file mode 100755 index 0000000..a7f02a5 --- /dev/null +++ b/gas/a.out.gnu.h @@ -0,0 +1,461 @@ +#ifndef __A_OUT_GNU_H__ +#define __A_OUT_GNU_H__ + +#include "target.h" /* Figure out which target and host systems */ + +#define __GNU_EXEC_MACROS__ + +#ifndef __STRUCT_EXEC_OVERRIDE__ + +struct exec +{ + unsigned long a_info; /* Use macros N_MAGIC, etc for access */ + unsigned a_text; /* length of text, in bytes */ + unsigned a_data; /* length of data, in bytes */ + unsigned a_bss; /* length of uninitialized data area for file, in bytes */ + unsigned a_syms; /* length of symbol table data in file, in bytes */ + unsigned a_entry; /* start address */ + unsigned a_trsize; /* length of relocation info for text, in bytes */ + unsigned a_drsize; /* length of relocation info for data, in bytes */ +}; + +#endif /* __STRUCT_EXEC_OVERRIDE__ */ + +/* these go in the N_MACHTYPE field */ +/* These symbols could be defined by code from Suns...punt 'em */ +#undef M_OLDSUN2 +#undef M_68010 +#undef M_68020 +#undef M_SPARC +enum machine_type { + M_OLDSUN2 = 0, + M_68010 = 1, + M_68020 = 2, + M_SPARC = 3, + /* skip a bunch so we don't run into any of sun's numbers */ + M_386 = 100, + M_29K = 101, +}; + +#define N_MAGIC(exec) ((exec).a_info & 0xffff) +#define N_MACHTYPE(exec) ((enum machine_type)(((exec).a_info >> 16) & 0xff)) +#define N_FLAGS(exec) (((exec).a_info >> 24) & 0xff) +#define N_SET_INFO(exec, magic, type, flags) \ + ((exec).a_info = ((magic) & 0xffff) \ + | (((int)(type) & 0xff) << 16) \ + | (((flags) & 0xff) << 24)) +#define N_SET_MAGIC(exec, magic) \ + ((exec).a_info = (((exec).a_info & 0xffff0000) | ((magic) & 0xffff))) + +#define N_SET_MACHTYPE(exec, machtype) \ + ((exec).a_info = \ + ((exec).a_info&0xff00ffff) | ((((int)(machtype))&0xff) << 16)) + +#define N_SET_FLAGS(exec, flags) \ + ((exec).a_info = \ + ((exec).a_info&0x00ffffff) | (((flags) & 0xff) << 24)) + +/* Code indicating object file or impure executable. */ +#define OMAGIC 0407 +/* Code indicating pure executable. */ +#define NMAGIC 0410 +/* Code indicating demand-paged executable. */ +#define ZMAGIC 0413 + +#define N_BADMAG(x) \ + (N_MAGIC(x) != OMAGIC && N_MAGIC(x) != NMAGIC \ + && N_MAGIC(x) != ZMAGIC) + +#define _N_BADMAG(x) \ + (N_MAGIC(x) != OMAGIC && N_MAGIC(x) != NMAGIC \ + && N_MAGIC(x) != ZMAGIC) + +#define _N_HDROFF(x) (1024 - sizeof (struct exec)) + +#define N_TXTOFF(x) \ + (N_MAGIC(x) == ZMAGIC ? _N_HDROFF((x)) + sizeof (struct exec) : sizeof (struct exec)) + +#define N_DATOFF(x) (N_TXTOFF(x) + (x).a_text) + +#define N_TRELOFF(x) (N_DATOFF(x) + (x).a_data) + +#define N_DRELOFF(x) (N_TRELOFF(x) + (x).a_trsize) + +#define N_SYMOFF(x) (N_DRELOFF(x) + (x).a_drsize) + +#define N_STROFF(x) (N_SYMOFF(x) + (x).a_syms) + +/* Address of text segment in memory after it is loaded. */ +/* Don't load things at zero, it encourages zero-pointer bugs */ +#ifndef TEXT_START_ADDR +#define TEXT_START_ADDR 0x10000 +#endif +#define N_TXTADDR(x) TEXT_START_ADDR + +/* Address of data segment in memory after it is loaded. + Note that it is up to you to define SEGMENT_SIZE + on machines not listed here. */ +#ifndef SEGMENT_SIZE +#if defined(vax) || defined(hp300) || defined(pyr) +#define SEGMENT_SIZE page_size +#endif +#ifdef sony +#define SEGMENT_SIZE 0x2000 +#endif /* Sony. */ +#ifdef is68k +#define SEGMENT_SIZE 0x20000 +#endif +#if defined(m68k) && defined(PORTAR) +#define PAGE_SIZE 0x400 +#define SEGMENT_SIZE PAGE_SIZE +#endif +#endif + +#define _N_SEGMENT_ROUND(x) (((x) + SEGMENT_SIZE - 1) & ~(SEGMENT_SIZE - 1)) + +#define _N_TXTENDADDR(x) (N_TXTADDR(x)+(x).a_text) + +#ifndef N_DATADDR +#define N_DATADDR(x) \ + (N_MAGIC(x)==OMAGIC? (_N_TXTENDADDR(x)) \ + : (_N_SEGMENT_ROUND (_N_TXTENDADDR(x)))) +#endif + +/* Address of bss segment in memory after it is loaded. */ +#define N_BSSADDR(x) (N_DATADDR(x) + (x).a_data) + +struct nlist { + union { + char *n_name; + struct nlist *n_next; + long n_strx; + } n_un; + unsigned char n_type; + char n_other; + short n_desc; + unsigned long n_value; +}; + +#define N_UNDF 0 +#define N_ABS 2 +#define N_TEXT 4 +#define N_DATA 6 +#define N_BSS 8 +#define N_FN 15 + +#define N_EXT 1 +#define N_TYPE 036 +#define N_STAB 0340 + +/* The following type indicates the definition of a symbol as being + an indirect reference to another symbol. The other symbol + appears as an undefined reference, immediately following this symbol. + + Indirection is asymmetrical. The other symbol's value will be used + to satisfy requests for the indirect symbol, but not vice versa. + If the other symbol does not have a definition, libraries will + be searched to find a definition. */ +#define N_INDR 0xa + +/* The following symbols refer to set elements. + All the N_SET[ATDB] symbols with the same name form one set. + Space is allocated for the set in the text section, and each set + element's value is stored into one word of the space. + The first word of the space is the length of the set (number of elements). + + The address of the set is made into an N_SETV symbol + whose name is the same as the name of the set. + This symbol acts like a N_DATA global symbol + in that it can satisfy undefined external references. */ + +/* These appear as input to LD, in a .o file. */ +#define N_SETA 0x14 /* Absolute set element symbol */ +#define N_SETT 0x16 /* Text set element symbol */ +#define N_SETD 0x18 /* Data set element symbol */ +#define N_SETB 0x1A /* Bss set element symbol */ + +/* This is output from LD. */ +#define N_SETV 0x1C /* Pointer to set vector in data area. */ + +/* This structure describes a single relocation to be performed. + The text-relocation section of the file is a vector of these structures, + all of which apply to the text section. + Likewise, the data-relocation section applies to the data section. */ + +#if TARGET == TARGET_SPARC || TARGET == TARGET_AM29K +/* + * The following enum and struct were borrowed from + * sunOS /usr/include/sun4/a.out.h and extended to handle + * other machines. + */ + +enum reloc_type +{ + RELOC_8, RELOC_16, RELOC_32, RELOC_DISP8, + RELOC_DISP16, RELOC_DISP32, RELOC_WDISP30, RELOC_WDISP22, + RELOC_HI22, RELOC_22, RELOC_13, RELOC_LO10, + RELOC_SFA_BASE, RELOC_SFA_OFF13, RELOC_BASE10, RELOC_BASE13, + RELOC_BASE22, RELOC_PC10, RELOC_PC22, RELOC_JMP_TBL, + RELOC_SEGOFF16, RELOC_GLOB_DAT, RELOC_JMP_SLOT, RELOC_RELATIVE, + +/* 29K relocation types */ + RELOC_JUMPTARG, RELOC_CONST, RELOC_CONSTH, + + NO_RELOC +}; + +#define RELOC_TYPE_NAMES \ +"8", "16", "32", "DISP8", \ +"DISP16", "DISP32", "WDISP30", "WDISP22", \ +"HI22", "22", "13", "LO10", \ +"SFA_BASE", "SFAOFF13", "BASE10", "BASE13", \ +"BASE22", "PC10", "PC22", "JMP_TBL", \ +"SEGOFF16", "GLOB_DAT", "JMP_SLOT", "RELATIVE", \ +"JUMPTARG", "CONST", "CONSTH", \ +"NO_RELOC", \ +"XXX_28", "XXX_29", "XXX_30", "XXX_31" + +struct reloc_info_extended +{ + unsigned long r_address; + unsigned int r_index:24; +# define r_symbolnum r_index + unsigned r_extern:1; + unsigned :2; + enum reloc_type r_type:5; + long int r_addend; +}; + +/* Let programs know what they're dealing with */ +#define RELOC_EXTENDED 1 + +#undef relocation_info +#define relocation_info reloc_info_extended +#define RELOC_ADDRESS(r) ((r)->r_address) +#define RELOC_EXTERN_P(r) ((r)->r_extern) +#define RELOC_TYPE(r) ((r)->r_index) +#define RELOC_EXTENDED_TYPE(r) ((r)->r_type) +#define RELOC_SYMBOL(r) ((r)->r_index) +#define RELOC_MEMORY_SUB_P(r) 0 +#define RELOC_MEMORY_ADD_P(r) 0 +#define RELOC_ADD_EXTRA(r) ((r)->r_addend) +#define RELOC_PCREL_P(r) \ + ( ((r)->r_type >= RELOC_DISP8 && (r)->r_type <= RELOC_WDISP22) \ + || (r)->r_type == RELOC_JUMPTARG ) +#define RELOC_VALUE_RIGHTSHIFT(r) (reloc_target_rightshift[(r)->r_type]) +#define RELOC_TARGET_SIZE(r) (reloc_target_size[(r)->r_type]) +#define RELOC_TARGET_BITPOS(r) 0 +#define RELOC_TARGET_BITSIZE(r) (reloc_target_bitsize[(r)->r_type]) + +/* Note that these are very dependent on the order of the enums in + enum reloc_type (in a.out.h); if they change the following must be + changed */ +/* Also note that some of these may be incorrect; I have no information */ +#ifndef __STDC__ +#define const /**/ +#endif +static const int reloc_target_rightshift[] = { + 0, 0, 0, 0, + 0, 0, 2, 2, + 10, 0, 0, 0, + 0, 0, 0, 0, + 0, 0, 0, 0, + 0, 0, 0, 0, + 2, 0,16, /* 29K jumptarg, const, consth */ + 0, +}; +#define RELOC_SIZE_SPLIT16 13 +static const int reloc_target_size[] = { + 0, 1, 2, 0, + 1, 2, 2, 2, + 2, 2, 2, 2, + 2, 2, 2, 2, + 2, 2, 2, 2, + 2, 2, 2, 2, + RELOC_SIZE_SPLIT16, RELOC_SIZE_SPLIT16, RELOC_SIZE_SPLIT16, + 0, +}; +static const int reloc_target_bitsize[] = { + 8, 16, 32, 8, + 16, 32, 30, 22, + 22, 22, 13, 10, + 32, 32, 16, 0, + 0, 0, 0, 0, /* dunno */ + 0, 0, 0, 0, + 16, 16, 16, /* 29K jumptarg, const, consth */ + 0, +}; + +#define MAX_ALIGNMENT (sizeof (double)) + +#else /* Not SPARC or AM29K */ + +struct relocation_info +{ + /* Address (within segment) to be relocated. */ + int r_address; + /* The meaning of r_symbolnum depends on r_extern. */ + unsigned int r_symbolnum:24; + /* Nonzero means value is a pc-relative offset + and it should be relocated for changes in its own address + as well as for changes in the symbol or section specified. */ + unsigned int r_pcrel:1; + /* Length (as exponent of 2) of the field to be relocated. + Thus, a value of 2 indicates 1<<2 bytes. */ + unsigned int r_length:2; + /* 1 => relocate with value of symbol. + r_symbolnum is the index of the symbol + in file's the symbol table. + 0 => relocate with the address of a segment. + r_symbolnum is N_TEXT, N_DATA, N_BSS or N_ABS + (the N_EXT bit may be set also, but signifies nothing). */ + unsigned int r_extern:1; + /* Four bits that aren't used, but when writing an object file + it is desirable to clear them. */ + unsigned int r_pad:4; +}; +#endif + +/* + * Ok. Following are the relocation information macros. If your + * system should not be able to use the default set (below), you must + * define the following: + + * relocation_info: This must be typedef'd (or #define'd) to the type + * of structure that is stored in the relocation info section of your + * a.out files. Often this is defined in the a.out.h for your system. + * + * RELOC_ADDRESS (rval): Offset into the current section of the + * <whatever> to be relocated. *Must be an lvalue*. + * + * RELOC_EXTERN_P (rval): Is this relocation entry based on an + * external symbol (1), or was it fully resolved upon entering the + * loader (0) in which case some combination of the value in memory + * (if RELOC_MEMORY_ADD_P) and the extra (if RELOC_ADD_EXTRA) contains + * what the value of the relocation actually was. *Must be an lvalue*. + * + * RELOC_TYPE (rval): If this entry was fully resolved upon + * entering the loader, what type should it be relocated as? + * + * RELOC_EXTENDED_TYPE (rval): If this entry is for a machine using + * extended relocatino, what type of field is it? (For example, on RISC + * machines, odd-sized displacements or split displacements occur.) + * + * RELOC_SYMBOL (rval): If this entry was not fully resolved upon + * entering the loader, what is the index of it's symbol in the symbol + * table? *Must be a lvalue*. + * + * RELOC_MEMORY_ADD_P (rval): This should return true if the final + * relocation value output here should be added to memory, or if the + * section of memory described should simply be set to the relocation + * value. + * + * RELOC_ADD_EXTRA (rval): (Optional) This macro, if defined, gives + * an extra value to be added to the relocation value based on the + * individual relocation entry. *Must be an lvalue if defined*. + * + * RELOC_PCREL_P (rval): True if the relocation value described is + * pc relative. + * + * RELOC_VALUE_RIGHTSHIFT (rval): Number of bits right to shift the + * final relocation value before putting it where it belongs. + * + * RELOC_TARGET_SIZE (rval): log to the base 2 of the number of + * bytes of size this relocation entry describes; 1 byte == 0; 2 bytes + * == 1; 4 bytes == 2, and etc. This is somewhat redundant (we could + * do everything in terms of the bit operators below), but having this + * macro could end up producing better code on machines without fancy + * bit twiddling. Also, it's easier to understand/code big/little + * endian distinctions with this macro. + * + * RELOC_TARGET_BITPOS (rval): The starting bit position within the + * object described in RELOC_TARGET_SIZE in which the relocation value + * will go. + * + * RELOC_TARGET_BITSIZE (rval): How many bits are to be replaced + * with the bits of the relocation value. It may be assumed by the + * code that the relocation value will fit into this many bits. This + * may be larger than RELOC_TARGET_SIZE if such be useful. + * + * + * Things I haven't implemented + * ---------------------------- + * + * Values for RELOC_TARGET_SIZE other than 0, 1, or 2. + * + * Pc relative relocation for External references. + */ +#if TARGET == TARGET_SEQUENT +#define RELOC_ADDRESS(r) ((r)->r_address) +#define RELOC_EXTERN_P(r) ((r)->r_extern) +#define RELOC_TYPE(r) ((r)->r_symbolnum) +#define RELOC_SYMBOL(r) ((r)->r_symbolnum) +#define RELOC_MEMORY_SUB_P(r) ((r)->r_bsr) +#define RELOC_MEMORY_ADD_P(r) 1 +#undef RELOC_ADD_EXTRA +#define RELOC_PCREL_P(r) ((r)->r_pcrel || (r)->r_bsr) +#define RELOC_VALUE_RIGHTSHIFT(r) 0 +#define RELOC_TARGET_SIZE(r) ((r)->r_length) +#define RELOC_TARGET_BITPOS(r) 0 +#define RELOC_TARGET_BITSIZE(r) 32 +#endif + +/* Default macros */ +#ifndef RELOC_ADDRESS +#define RELOC_ADDRESS(r) ((r)->r_address) +#define RELOC_EXTERN_P(r) ((r)->r_extern) +#define RELOC_TYPE(r) ((r)->r_symbolnum) +#define RELOC_SYMBOL(r) ((r)->r_symbolnum) +#define RELOC_MEMORY_SUB_P(r) 0 +#define RELOC_MEMORY_ADD_P(r) 1 +#undef RELOC_ADD_EXTRA +#define RELOC_PCREL_P(r) ((r)->r_pcrel) +#define RELOC_VALUE_RIGHTSHIFT(r) 0 +#define RELOC_TARGET_SIZE(r) ((r)->r_length) +#define RELOC_TARGET_BITPOS(r) 0 +#define RELOC_TARGET_BITSIZE(r) 32 +#endif + +/* Maximum alignment required of a common'd variable. If a var of this + size or larger is allocated in BSS when nobody defines it, it gets + this alignment. */ + +#ifndef MAX_ALIGNMENT +#define MAX_ALIGNMENT (sizeof (int)) +#endif + + +/* Definitions for routines that read and write GNU a.out files */ + +enum objfile_kind { + OBJFILE_ERROR, + OBJFILE_UNKNOWN, + OBJFILE_SINGLE, + OBJFILE_ARCHIVE, +}; + +enum objfile_kind read_aout_header(); /* (desc, &header) read&swap header */ + +/* Read an a.out header from DESC and call rel_fn(DESC, header) + if it is an object file, lib_fn(DESC) if it is a library, else + call err_fn("msg") */ +void handle_aout_header(); /* (desc, rel_fn, lib_fn, err_fn) */ + +/* Byte-swapping definitions */ + +void swap_aoutheader(); /* BSD a.out header */ +short swap_getshort (); +void swap_putshort(); +long swap_getlong (); +void swap_putlong(); +void swap_reloc_info_in(); /* BSD relocation information */ +void swap_reloc_info_out(); /* BSD relocation information */ +void swap_nlists(); /* BSD symbol name lists */ +void swap_root_updates(); /* GDB Symseg */ + +/* Bring on the encapsulation, if configured in! */ +#ifdef COFF_ENCAPSULATE +#include "a.out.encap.h" +#endif + +#endif /* __A_OUT_GNU_H__ */ diff --git a/gas/config/a.out.h b/gas/config/a.out.h new file mode 100755 index 0000000..5043249 --- /dev/null +++ b/gas/config/a.out.h @@ -0,0 +1,150 @@ +/* This file describes the a.out file format + Copyright (C) 1987 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* $Id$ */ + +#ifdef USE_HP_INC_HDR +#include "../binutils/hp-include/a.out.h" +#else + +#ifdef USE_SYSTEM_HDR +#include "/usr/include/a.out.h" +#else + +#ifdef USE_HP_HDR +/* The `exec' structure and overall layout must be close to HP's when + we are running on an HP system, otherwise we will not be able to + execute the resulting file. */ + +struct exec +{ + unsigned short a_machtype; /* machine type */ + unsigned short a_magic; /* magic number */ + unsigned long a_spare1; + unsigned long a_spare2; + unsigned long a_text; /* length of text, in bytes */ + unsigned long a_data; /* length of data, in bytes */ + unsigned long a_bss; /* length of uninitialized data area for file, in bytes */ + unsigned long a_trsize; /* length of relocation info for text, in bytes */ + unsigned long a_drsize; /* length of relocation info for data, in bytes */ + unsigned long a_spare3; /* HP = pascal interface size */ + unsigned long a_spare4; /* HP = symbol table size */ + unsigned long a_spare5; /* HP = debug name table size */ + unsigned long a_entry; /* start address */ + unsigned long a_spare6; /* HP = source line table size */ + unsigned long a_spare7; /* HP = value table size */ + unsigned long a_syms; /* length of symbol table data in file, in bytes */ + unsigned long a_spare8; +}; + +#define N_MAGIC(exec) ((exec) . a_magic) +#define N_MACHTYPE(exec) ((exec) . a_machtype) +#define N_SET_MAGIC(exec, magic) (((exec) . a_magic) = (magic)) +#define N_SET_MACHTYPE(exec, machtype) (((exec) . a_machtype) = (machtype)) + +#define N_BADMAG(x) ((_N_BADMAG (x)) || (_N_BADMACH (x))) + +#define _N_BADMACH(x) \ +(((N_MACHTYPE (x)) != HP9000S200_ID) && \ + ((N_MACHTYPE (x)) != HP98x6_ID)) + +#define _N_BADMAG(x) \ + (((x).a_magic)!=OMAGIC && ((x).a_magic)!=NMAGIC && ((x).a_magic)!=ZMAGIC) + +#define HP98x6_ID 0x20A +#define HP9000S200_ID 0x20C + +#else + + /* A Generic machine. . . */ + +/* JF I'm not sure where this file came from. I put the permit.text message in + it anyway. This file came to me as part of the original VAX assembler, but had + no copyright notices in it. */ + +struct exec { + long a_magic; /* number identifies as .o file and gives type of such. */ + unsigned a_text; /* length of text, in bytes */ + unsigned a_data; /* length of data, in bytes */ + unsigned a_bss; /* length of uninitialized data area for file, in bytes */ + unsigned a_syms; /* length of symbol table data in file, in bytes */ + unsigned a_entry; /* start address */ + unsigned a_trsize; /* length of relocation info for text, in bytes */ + unsigned a_drsize; /* length of relocation info for data, in bytes */ +}; + +#define N_BADMAG(x) \ + (((x).a_magic)!=OMAGIC && ((x).a_magic)!=NMAGIC && ((x).a_magic)!=ZMAGIC) + +#endif + + /* From here down is common to both the HP and the generic machine */ +#define OMAGIC 0407 +#define NMAGIC 0410 +#define ZMAGIC 0413 + + +#define N_TXTOFF(x) \ + ((x).a_magic == ZMAGIC ? 1024 : sizeof(struct exec)) + +#define N_SYMOFF(x) \ + (N_TXTOFF(x) + (x).a_text + (x).a_data + (x).a_trsize + (x).a_drsize) + +#define N_STROFF(x) \ + (N_SYMOFF(x) + (x).a_syms) + +struct nlist { + union { + char *n_name; + struct nlist *n_next; + long n_strx; + } n_un; + char n_type; + char n_other; + short n_desc; + unsigned n_value; +}; + +#define N_UNDF 0 +#define N_ABS 2 +#define N_TEXT 4 +#define N_DATA 6 +#define N_BSS 8 +#define N_FN 31 /* JF: Someone claims this should be 31 instead of + 15. I just inherited this file; I didn't write + it. Who is right? */ + + +#define N_EXT 1 +#define N_TYPE 036 +#define N_STAB 0340 + +struct relocation_info { + int r_address; + unsigned r_symbolnum:24, + r_pcrel:1, + r_length:2, + r_extern:1, + r_bsr:1, /* OVE: used on ns32k based systems, if you want */ + r_disp:1, /* OVE: used on ns32k based systems, if you want */ + nuthin:2; +}; + +#endif +#endif diff --git a/gas/config/coff.gnu.h b/gas/config/coff.gnu.h new file mode 100755 index 0000000..281ac17 --- /dev/null +++ b/gas/config/coff.gnu.h @@ -0,0 +1,568 @@ +/*** coff information for 80960. Origins: Intel, AMD, etc., natch. */ + +/* + * At this point I'm sure this file is right for i960 and I'm pretty sure it's + * right for a29k, although it hasn't been tested rigorously. Please feel free + * to add your own machine's description here. Without that info, it isn't + * possible to build cross development tools from elsewhere nor is it easy to + * continue to support your machines format. + * + * The TC_foo ifdef's are mine. They are what gas uses. The other ifdef's + * remain for documentation from other scavenged files. xoxorich. + */ + +/* $Id$ */ + +/********************** FILE HEADER **********************/ + +struct filehdr { + unsigned short f_magic; /* magic number */ + unsigned short f_nscns; /* number of sections */ + long f_timdat; /* time & date stamp */ + long f_symptr; /* file pointer to symtab */ + long f_nsyms; /* number of symtab entries */ + unsigned short f_opthdr; /* sizeof(optional hdr) */ + unsigned short f_flags; /* flags */ +}; + +/* Bits for f_flags: + * F_RELFLG relocation info stripped from file + * F_EXEC file is executable (no unresolved externel references) + * F_LNNO line nunbers stripped from file + * F_LSYMS local symbols stripped from file + * F_AR32WR file has byte ordering of an AR32WR machine (e.g. vax) + */ +#define F_RELFLG (0x0001) +#define F_EXEC (0x0002) +#define F_LNNO (0x0004) +#define F_LSYMS (0x0008) + +#ifdef TC_I960 +#define F_AR32WR (0x0010) /* File has 32 bits per word, least + significant byte first. */ +#else /* TC_I960 */ +#define F_AR32WR (0x0100) +#endif /* TC_I960 */ + +#define F_MINMAL (0x0010) /* ??? */ +#define F_UPDATE (0x0020) /* ??? */ +#define F_SWABD (0x0040) /* ??? */ +#define F_AR16WR (0x0080) /* File has the byte ordering used by + the PDP*-11/70 processor. */ +#define F_AR32W (0x0200) /* File has 32 bits per word, most + significant byte first. */ + +/* + * Intel 80960 (I960) processor flags. + * F_I960TYPE == mask for processor type field. + */ + +#define F_I960TYPE (0xf000) +#define F_I960CORE (0x1000) +#define F_I960KB (0x2000) +#define F_I960SB (0x2000) +#define F_I960MC (0x3000) +#define F_I960XA (0x4000) +#define F_I960CA (0x5000) +#define F_I960KA (0x6000) +#define F_I960SA (0x6000) + +/* + * i80960 Magic Numbers + */ + +#define I960ROMAGIC (0x160) /* read-only text segments */ +#define I960RWMAGIC (0x161) /* read-write text segments */ + +#define I960BADMAG(x) (((x).f_magic != I960ROMAGIC) && ((x).f_magic != I960RWMAGIC)) + +#define SIPFBOMAGIC (0x17a) /* Am29000 (Byte 0 is MSB - Big Endian) */ +#define SIPRBOMAGIC (0x17b) /* Am29000 (Byte 0 is LSB - Little Endian) */ + +#define A29KBADMAG(x) (((x).f_magic != SIPFBOMAGIC) && ((x).f_magic != SIPRBOMAGIC)) + +#define FILHDR struct filehdr +#define FILHSZ sizeof(FILHDR) + + +/********************** AOUT "OPTIONAL HEADER" **********************/ + +typedef struct { + unsigned long phys_addr; + unsigned long bitarray; +} TAGBITS; + +/* These appear to be used only by exec(2). I don't know who cares + about them in a cross development environment. In any case, this + is my collection after researching the issue for a few hours. + Apparently, most have these have remained essentially unchanged + since v7 days, although a few new ones have been added. xoxorich. */ + +#define BAD0MAGIC (0401) /* (?) "lpd (UNIX/RT)" */ +#define BAD1MAGIC (0405) /* (?) overlay */ +#define OMAGIC (0407) /* old impure format. data immediately + follows text. both sections are rw. */ +#define NMAGIC (0410) /* split i&d, read-only text */ +#define A_MAGIC3 (0411) /* (?) "separated I&D" */ +#define ZMAGIC (0413) /* like NMAGIC, but demand loaded */ +#define PAGEMAGIC2 (0414) /* (?) like ZMAGIC, but address zero + explicitly unmapped. */ +#define REGMAGIC (0414) /* (?) a PAGEMAGIC2 alias? */ +#define PAGEMAGIC3 (0415) /* (?) like ZMAGIC, but address zero mapped. */ +#define A_MAGIC5 (0437) /* (?) "system overlay, separated I&D" */ + /* intended for non-unix cross development */ +#define SASMAGIC (010000) /* Single Address Space */ +#define MASMAGIC (020000) /* (?) "Multiple (separate I & D) Address Spaces" */ + +typedef struct aouthdr { + short magic; /* type of file */ + short vstamp; /* version stamp */ + unsigned long tsize; /* text size in bytes, padded to FW bdry*/ + unsigned long dsize; /* initialized data " " */ + unsigned long bsize; /* uninitialized data " " */ +#if U3B + unsigned long dum1; + unsigned long dum2; /* pad to entry point */ +#endif + unsigned long entry; /* entry pt. */ + unsigned long text_start; /* base of text used for this file */ + unsigned long data_start; /* base of data used for this file */ + /* CAREFUL: some formats omit the tagentries member. */ + unsigned long tagentries; /* number of tag entries to + follow (always zero for i960) */ +} AOUTHDR; + +/* return a pointer to the tag bits array */ + +#define TAGPTR(aout) ((TAGBITS *) (&(aout.tagentries)+1)) + +/* compute size of a header */ + +/*#define AOUTSZ(aout) (sizeof(AOUTHDR)+(aout.tagentries*sizeof(TAGBITS)))*/ +#define AOUTSZ (sizeof(AOUTHDR)) + + +/********************** STORAGE CLASSES **********************/ + +#define C_EFCN -1 /* physical end of function */ +#define C_NULL 0 +#define C_AUTO 1 /* automatic variable */ +#define C_EXT 2 /* external symbol */ +#define C_STAT 3 /* static */ +#define C_REG 4 /* register variable */ +#define C_EXTDEF 5 /* external definition */ +#define C_LABEL 6 /* label */ +#define C_ULABEL 7 /* undefined label */ +#define C_MOS 8 /* member of structure */ +#define C_ARG 9 /* function argument */ +#define C_STRTAG 10 /* structure tag */ +#define C_MOU 11 /* member of union */ +#define C_UNTAG 12 /* union tag */ +#define C_TPDEF 13 /* type definition */ +#define C_USTATIC 14 /* undefined static */ +#define C_ENTAG 15 /* enumeration tag */ +#define C_MOE 16 /* member of enumeration */ +#define C_REGPARM 17 /* register parameter */ +#define C_FIELD 18 /* bit field */ + +#ifdef TC_I960 +#define C_AUTOARG 19 /* auto argument */ +#define C_LASTENT 20 /* dummy entry (end of block) */ +#endif /* TC_I960 */ + +#ifdef TC_A29K +#define C_GLBLREG 19 /* global register */ +#define C_EXTREG 20 /* external global register */ +#define C_DEFREG 21 /* ext. def. of global register */ +#define C_STARTOF 22 /* as29 $SIZEOF and $STARTOF symbols */ +#endif /* TC_A29K */ + +#define C_BLOCK 100 /* ".bb" or ".eb" */ +#define C_FCN 101 /* ".bf" or ".ef" */ +#define C_EOS 102 /* end of structure */ +#define C_FILE 103 /* file name */ +#define C_LINE 104 /* line # reformatted as symbol table entry */ +#define C_ALIAS 105 /* duplicate tag */ +#define C_HIDDEN 106 /* ext symbol in dmert public lib. like static, + used to avoid name conflicts. */ + +#ifdef TC_I960 + /* New storage classes for 80960 */ +#define C_SCALL 107 /* Procedure reachable via system call */ + /* C_LEAFPROC is obsolete. Use C_LEAFEXT or C_LEAFSTAT */ +#define C_LEAFPROC 108 /* Leaf procedure, "call" via BAL */ +#define C_LEAFEXT 108 +#define C_OPTVAR 109 /* Optimized variable */ +#define C_DEFINE 110 /* Preprocessor #define */ +#define C_PRAGMA 111 /* Advice to compiler or linker */ +#define C_SEGMENT 112 /* 80960 segment name */ +#define C_LEAFSTAT 113 /* Static leaf */ +#endif /* TC_I960 */ + +#ifdef TC_A29K +#define C_SHADOW 107 /* shadow symbol */ +#endif /* TC_A29K */ + +/********************** SECTION HEADER **********************/ + +struct scnhdr { + char s_name[8]; /* section name */ + long s_paddr; /* physical address, aliased s_nlib */ + long s_vaddr; /* virtual address */ + long s_size; /* section size */ + long s_scnptr; /* file ptr to raw data for section */ + long s_relptr; /* file ptr to relocation */ + long s_lnnoptr; /* file ptr to line numbers */ + unsigned short s_nreloc; /* number of relocation entries */ + unsigned short s_nlnno; /* number of line number entries */ + long s_flags; /* flags */ + +#ifdef TC_I960 + unsigned long s_align; /* section alignment */ +#endif /* TC_I960 */ +}; + +#define SCNHDR struct scnhdr +#define SCNHSZ sizeof(SCNHDR) + +/* + * names of "special" sections + */ +#define _TEXT ".text" +#define _DATA ".data" +#define _BSS ".bss" + +/* + * s_flags "type" + */ + +/* + * In instances where it is necessary for a linker to + * produce an output file which contains text or data not + * based at virtual address 0, e.g. for a ROM, then the + * linker should accept address base information as command + * input and use PAD sections to skip over unused addresses. + * (at least for a29k. Maybe others.) + */ + +#define STYP_REG (0x0000) /* "regular" section: allocated, relocated, loaded */ +#define STYP_DSECT (0x0001) /* "dummy" section: not allocated, relocated, not loaded */ +#define STYP_NOLOAD (0x0002) /* "noload" section: allocated, relocated, not loaded */ +#define STYP_GROUP (0x0004) /* "grouped" section: formed of input sections */ +#define STYP_PAD (0x0008) /* "padding" section: not allocated, not relocated, loaded */ +#define STYP_COPY (0x0010) /* "copy" section: for decision function used by field update; not allocated, not relocated, + loaded; reloc & lineno entries processed normally */ +#define STYP_TEXT (0x0020) /* section contains text only */ +#define S_SHRSEG (0x0020) /* In 3b Update files (output of ogen), sections which appear in SHARED segments of the Pfile + will have the S_SHRSEG flag set by ogen, to inform dufr that updating 1 copy of the proc. will + update all process invocations. */ +#define STYP_DATA (0x0040) /* section contains data only */ +#define STYP_BSS (0x0080) /* section contains bss only */ +#define S_NEWFCN (0x0100) /* In a minimal file or an update file, a new function (as compared with a replaced function) */ +#define STYP_INFO (0x0200) /* comment section : not allocated not relocated, not loaded */ +#define STYP_OVER (0x0400) /* overlay section : relocated not allocated or loaded */ +#define STYP_LIB (0x0800) /* for .lib section : same as INFO */ +#define STYP_MERGE (0x2000) /* merge section -- combines with text, data or bss sections only */ +#define STYP_REVERSE_PAD (0x4000) /* section will be padded with no-op instructions wherever padding is necessary and there is a + word of contiguous bytes beginning on a word boundary. */ + +#ifdef TC_A29K +/* NOTE: The use of STYP_BSSREG for relocation is not yet defined. */ +#define STYP_BSSREG 0x1200 /* Global register area (like STYP_INFO) */ +#define STYP_ENVIR 0x2200 /* Environment (like STYP_INFO) */ +#define STYP_ABS 0x4000 /* Absolute (allocated, not reloc, loaded) */ +#define STYP_LIT 0x8020 /* Literal data (like STYP_TEXT) */ +#endif /* TC_A29K */ + +/********************** LINE NUMBERS **********************/ + +/* 1 line number entry for every "breakpointable" source line in a section. + * Line numbers are grouped on a per function basis; first entry in a function + * grouping will have l_lnno = 0 and in place of physical address will be the + * symbol table index of the function name. + */ +struct lineno { + union { + long l_symndx; /* symbol index of function name, iff l_lnno == 0*/ + long l_paddr; /* (physical) address of line number */ + } l_addr; + unsigned short l_lnno; /* line number */ +#ifdef TC_I960 + /* not used on a29k */ + char padding[2]; /* force alignment */ +#endif /* TC_I960 */ +}; + +#define LINENO struct lineno +#define LINESZ sizeof(LINENO) + + +/********************** SYMBOLS **********************/ + +#define SYMNMLEN 8 /* # characters in a symbol name */ +#define FILNMLEN 14 /* # characters in a file name */ +#define DIMNUM 4 /* # array dimensions in auxiliary entry */ + +struct syment { + union { + char _n_name[SYMNMLEN]; /* old COFF version */ + struct { + long _n_zeroes; /* new == 0 */ + long _n_offset; /* offset into string table */ + } _n_n; + char *_n_nptr[2]; /* allows for overlaying */ + } _n; + long n_value; /* value of symbol */ + short n_scnum; /* section number */ + +#ifdef TC_I960 + /* This isn't yet used on the i960. In some formats this + is two bytes of padding. In others, it is missing entirely. */ + unsigned short n_flags; /* copy of flags from filhdr */ +#endif /* TC_I960 */ + +#ifdef TC_A29K + unsigned short n_type; /* type and derived type */ +#else /* TC_A29K */ + /* at least i960 uses long */ + unsigned long n_type; /* type and derived type */ +#endif /* TC_A29K */ + + char n_sclass; /* storage class */ + char n_numaux; /* number of aux. entries */ + +#ifndef TC_A29K + char pad2[2]; /* force alignment */ +#endif /* TC_A29K */ +}; + +#define SYMENT struct syment +#define SYMESZ sizeof(SYMENT) /* This had better also be sizeof(AUXENT) */ + +#define n_name _n._n_name +#define n_ptr _n._n_nptr[1] +#define n_zeroes _n._n_n._n_zeroes +#define n_offset _n._n_n._n_offset + +/* + * Relocatable symbols have number of the section in which they are defined, + * or one of the following: + */ + +#define N_SCNUM ((short) 1-65535) /* section num where symbol defined */ +#define N_UNDEF ((short)0) /* undefined symbol */ +#define N_ABS ((short)-1) /* value of symbol is absolute */ +#define N_DEBUG ((short)-2) /* debugging symbol -- symbol value is meaningless */ +#define N_TV ((short)-3) /* indicates symbol needs preload transfer vector */ +#define P_TV ((short)-4) /* indicates symbol needs transfer vector (postload) */ + +/* + * Type of a symbol, in low 4 bits of the word + */ +#define T_NULL 0 /* type not assigned */ +#define T_VOID 1 /* function argument (only used by compiler) (but now + real void). */ +#define T_CHAR 2 /* character */ +#define T_SHORT 3 /* short integer */ +#define T_INT 4 /* integer */ +#define T_LONG 5 /* long integer */ +#define T_FLOAT 6 /* floating point */ +#define T_DOUBLE 7 /* double word */ +#define T_STRUCT 8 /* structure */ +#define T_UNION 9 /* union */ +#define T_ENUM 10 /* enumeration */ +#define T_MOE 11 /* member of enumeration */ +#define T_UCHAR 12 /* unsigned character */ +#define T_USHORT 13 /* unsigned short */ +#define T_UINT 14 /* unsigned integer */ +#define T_ULONG 15 /* unsigned long */ + +#ifdef TC_I960 +#define T_LNGDBL 16 /* long double */ +#endif /* TC_I960 */ + +/* + * derived types, in n_type + */ +#define DT_NON (0) /* no derived type */ +#define DT_PTR (1) /* pointer */ +#define DT_FCN (2) /* function */ +#define DT_ARY (3) /* array */ + +#ifndef TC_I960 + +#define N_BTMASK (0x0f) +#define N_TMASK (0x30) +#define N_BTSHFT (4) +#define N_TSHIFT (2) + +#else /* TC_I960 */ + +#define N_BTMASK (0x1f) +#define N_TMASK (0x60) +#define N_BTSHFT (5) +#define N_TSHIFT (2) + +#endif /* TC_I960 */ + +#define BTYPE(x) ((x) & N_BTMASK) + +#define ISPTR(x) (((x) & N_TMASK) == (DT_PTR << N_BTSHFT)) +#define ISFCN(x) (((x) & N_TMASK) == (DT_FCN << N_BTSHFT)) +#define ISARY(x) (((x) & N_TMASK) == (DT_ARY << N_BTSHFT)) + +#define DECREF(x) ((((x)>>N_TSHIFT)&~N_BTMASK)|((x)&N_BTMASK)) + +union auxent { + struct { + long x_tagndx; /* str, un, or enum tag indx */ + union { + struct { + unsigned short x_lnno; /* declaration line number */ + unsigned short x_size; /* str/union/array size */ + } x_lnsz; + long x_fsize; /* size of function */ + } x_misc; + union { + struct { /* if ISFCN, tag, or .bb */ + long x_lnnoptr; /* ptr to fcn line # */ + long x_endndx; /* entry ndx past block end */ + } x_fcn; + struct { /* if ISARY, up to 4 dimen. */ + unsigned short x_dimen[DIMNUM]; + } x_ary; + } x_fcnary; + unsigned short x_tvndx; /* tv index */ + } x_sym; + + /* This was just a struct x_file with x_fname only in a29k. xoxorich. */ + union { + char x_fname[FILNMLEN]; + struct { + long x_zeroes; + long x_offset; + } x_n; + } x_file; + + struct { + long x_scnlen; /* section length */ + unsigned short x_nreloc; /* # relocation entries */ + unsigned short x_nlinno; /* # line numbers */ + } x_scn; + + struct { + long x_tvfill; /* tv fill value */ + unsigned short x_tvlen; /* length of .tv */ + + /* This field was typo'd x_tvrna on a29k. xoxorich. */ + unsigned short x_tvran[2]; /* tv range */ + } x_tv; /* info about .tv section (in auxent of symbol .tv)) */ + +#ifdef TC_I960 + /****************************************** + * I960-specific *2nd* aux. entry formats + ******************************************/ + struct { + /* This is a very old typo that keeps getting propogated. */ +#define x_stdindx x_stindx + long x_stindx; /* sys. table entry */ + } x_sc; /* system call entry */ + + struct { + unsigned long x_balntry; /* BAL entry point */ + } x_bal; /* BAL-callable function */ + + struct { + unsigned long x_timestamp; /* time stamp */ + char x_idstring[20]; /* producer identity string */ + } x_ident; /* Producer ident info */ + + char a[sizeof(struct syment)]; /* force auxent/syment sizes to match */ +#endif /* TC_I960 */ +}; + +#define AUXENT union auxent +#define AUXESZ sizeof(AUXENT) /* This had better also be sizeof(SYMENT) */ + +#if VAX || I960 +# define _ETEXT "_etext" +#else +# define _ETEXT "etext" +#endif + +/********************** RELOCATION DIRECTIVES **********************/ + +struct reloc { + long r_vaddr; /* Virtual address of reference */ + long r_symndx; /* Index into symbol table */ + unsigned short r_type; /* Relocation type */ +#ifdef TC_I960 + /* not used for a29k */ + char pad[2]; /* Unused */ +#endif /* TC_I960 */ +}; + +#define RELOC struct reloc +#define RELSZ sizeof(RELOC) + +#ifdef TC_I960 +#define R_RELLONG (0x11) /* Direct 32-bit relocation */ +#define R_IPRSHORT (0x18) +#define R_IPRMED (0x19) /* 24-bit ip-relative relocation */ +#define R_IPRLONG (0x1a) +#define R_OPTCALL (0x1b) /* 32-bit optimizable call (leafproc/sysproc) */ +#define R_OPTCALLX (0x1c) /* 64-bit optimizable call (leafproc/sysproc) */ +#define R_GETSEG (0x1d) +#define R_GETPA (0x1e) +#define R_TAGWORD (0x1f) +#endif /* TC_I960 */ + +#ifdef TC_A29K +/* + * NOTE: All the "I" forms refer to Am29000 instruction + * formats. The linker is expected to know how the numeric + * information is split and/or aligned within the + * instruction word(s). R_BYTE works for instructions, too. + * + * If the parameter to a CONSTH instruction is a relocatable + * type, two relocation records are written. The first has + * an r_type of R_IHIHALF (33 octal) and a normal r_vaddr + * and r_symndx. The second relocation record has an r_type + * of R_IHCONST (34 octal), a normal r_vaddr (which is + * redundant), and an r_symndx containing the 32-bit + * constant offset to the relocation instead of the actual + * symbol table index. This second record is always + * written, even if the constant offset is zero. The + * constant fields of the instruction are set to zero. + */ + +#define R_ABS (0x00) /* reference is absolute */ +#define R_IREL (0x18) /* instruction relative (jmp/call) */ +#define R_IABS (0x19) /* instruction absolute (jmp/call) */ +#define R_ILOHALF (0x1a) /* instruction low half (const) */ +#define R_IHIHALF (0x1b) /* instruction high half (consth) part 1 */ +#define R_IHCONST (0x1c) /* instruction high half (consth) part 2 + constant offset of R_IHIHALF relocation */ +#define R_BYTE (0x1d) /* relocatable byte value */ +#define R_HWORD (0x1e) /* relocatable halfword value */ +#define R_WORD (0x1f) /* relocatable word value */ +#define R_IGLBLRC (0x20) /* instruction global register RC */ +#define R_IGLBLRA (0x21) /* instruction global register RA */ +#define R_IGLBLRB (0x22) /* instruction global register RB */ +#endif /* TC_A29K */ + + +#define DEFAULT_DATA_SECTION_ALIGNMENT 4 +#define DEFAULT_BSS_SECTION_ALIGNMENT 4 +#define DEFAULT_TEXT_SECTION_ALIGNMENT 16 +/* For new sections we havn't heard of before */ +#define DEFAULT_SECTION_ALIGNMENT 4 + + +/* + * Local Variables: + * comment-column: 0 + * End: + */ + +/* end of coff.gnu.h */ diff --git a/gas/config/ho-ansi.h b/gas/config/ho-ansi.h new file mode 100644 index 0000000..b7fc587 --- /dev/null +++ b/gas/config/ho-ansi.h @@ -0,0 +1,40 @@ +/* ho-ansi.h Host-specific header file for generic ansi environments. + Copyright (C) 1987, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* $Id$ */ + +#define M_ANSI 1 + +#include <stdlib.h> +#include <string.h> +#include <memory.h> + +#define sys_nerr _sys_nerr +#define sys_errlist _sys_errlist +#define bzero(b,l) (memset((b),0,(l))) + +/* + * $Log$ + * Revision 1.1 1991/04/04 18:15:38 rich + * Initial revision + * + * + */ + +/* end of ho-ansi.h */ diff --git a/gas/config/ho-cygnus.h b/gas/config/ho-cygnus.h new file mode 100755 index 0000000..9b39153 --- /dev/null +++ b/gas/config/ho-cygnus.h @@ -0,0 +1,41 @@ +/* ho-ansi.h Host-specific header file for generic ansi environments. + Copyright (C) 1987, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* $Id$ */ + +#define M_ANSI 1 + +#include <stdlib.h> +#include <string.h> +#include <stdio.h> +#include <ctype.h> + +#define sys_nerr _sys_nerr +#define sys_errlist _sys_errlist +#define bzero(s,l) (memset((s),0,(l))) + +/* + * $Log$ + * Revision 1.1 1991/04/04 18:15:40 rich + * Initial revision + * + * + */ + +/* end of ho-ansi.h */ diff --git a/gas/config/ho-generic.h b/gas/config/ho-generic.h new file mode 100644 index 0000000..40c49e9 --- /dev/null +++ b/gas/config/ho-generic.h @@ -0,0 +1,32 @@ +/* ho-generic.h Generic host-specific header file. + Copyright (C) 1987, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* $Id$ */ + +#define M_GENERIC 1 + +/* + * $Log$ + * Revision 1.1 1991/04/04 18:15:42 rich + * Initial revision + * + * + */ + +/* end of ho-generic.h */ diff --git a/gas/config/ho-hpux.h b/gas/config/ho-hpux.h new file mode 100644 index 0000000..751b4ee --- /dev/null +++ b/gas/config/ho-hpux.h @@ -0,0 +1,34 @@ +/* ho-hpux.h -- Header to compile the assembler under HP-UX + Copyright (C) 1988, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* $Id$ */ + +#include "ho-sysv.h" + +/* This header file contains the #defines specific + to HPUX changes sent me by cph@zurich.ai.mit.edu */ +#ifndef hpux +#define hpux +#endif + +#ifdef setbuffer +#undef setbuffer +#endif /* setbuffer */ + +#define setbuffer(stream, buf, size) diff --git a/gas/config/ho-i386.h b/gas/config/ho-i386.h new file mode 100644 index 0000000..94dd8c2 --- /dev/null +++ b/gas/config/ho-i386.h @@ -0,0 +1,28 @@ +/* ho-i386.h i386 specific header file. + Copyright (C) 1987, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* $Id$ */ + +#define HO_I386 1 + +#define NO_STDARG + +#include "ho-sysv.h" + +/* end of ho-i386.h */ diff --git a/gas/config/ho-sun3.h b/gas/config/ho-sun3.h new file mode 100644 index 0000000..33b74c3 --- /dev/null +++ b/gas/config/ho-sun3.h @@ -0,0 +1,7 @@ +/* $Id$ */ + +#include <ho-sunos.h> + +extern int sprintf(); + +/* end of ho-sun3.h */ diff --git a/gas/config/ho-sun386.h b/gas/config/ho-sun386.h new file mode 100644 index 0000000..00eacad --- /dev/null +++ b/gas/config/ho-sun386.h @@ -0,0 +1,7 @@ +/* $Id$ */ + +#include <ho-sunos.h> + +extern int sprintf(); + +/* end of ho-sun386.h */ diff --git a/gas/config/ho-sun4.h b/gas/config/ho-sun4.h new file mode 100644 index 0000000..6cfd6b4 --- /dev/null +++ b/gas/config/ho-sun4.h @@ -0,0 +1,5 @@ +/* $Id$ */ + +#include <ho-sunos.h> + +/* end of ho-sun4.h */ diff --git a/gas/config/ho-sunos.h b/gas/config/ho-sunos.h new file mode 100644 index 0000000..13d5c3d --- /dev/null +++ b/gas/config/ho-sunos.h @@ -0,0 +1,56 @@ +/* $Id$ */ + +#ifndef __STDC__ +#define NO_STDARG +#include <memory.h> +#endif /* not __STDC__ */ + +#include <ctype.h> +#include <string.h> + +/* externs for system libraries. */ + +extern char *strchr(); +extern char *malloc(); +extern char *realloc(); +extern char *strrchr(); +extern int _filbuf(); +extern int _flsbuf(); +extern int abort(); +extern int bcopy(); +extern int bzero(); +extern int bzero(); +extern int exit(); +extern int fclose(); +extern int fprintf(); +extern int fread(); +extern int free(); +extern int perror(); +extern int printf(); +extern int setvbuf(); +extern int sscanf(); +extern int strcmp(); +extern int strlen(); +extern int strncmp(); +extern int time(); +extern int ungetc(); +extern int vfprintf(); +extern int vprintf(); +extern long atol(); + +#ifndef tolower +extern int tolower(); +#endif /* tolower */ + +#ifndef toupper +extern int toupper(); +#endif /* toupper */ + +/* + * Local Variables: + * fill-column: 80 + * comment-column: 0 + * End: + */ + +/* end of ho-sun4.h */ diff --git a/gas/config/ho-sysv.h b/gas/config/ho-sysv.h new file mode 100644 index 0000000..af8dd6e --- /dev/null +++ b/gas/config/ho-sysv.h @@ -0,0 +1,31 @@ +/* ho-sysv.h System V specific header file. + Copyright (C) 1987, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* $Id$ */ + +#define HO_USG + +#define bcopy(from,to,n) memcpy((to),(from),(n)) +#define bzero(s,n) memset((s),0,(n)) +#define setbuffer(stream, buf, size) setvbuf((stream), (buf), _IOLBF, (size)) + +extern int free(); +extern char *malloc(); + +/* end of ho-sysv.h */ diff --git a/gas/configure.was b/gas/configure.was new file mode 100755 index 0000000..2485927 --- /dev/null +++ b/gas/configure.was @@ -0,0 +1,340 @@ +#!/bin/sh +# Configuration script for GNU GAS +# Copyright (C) 1988, 1990, 1991 Free Software Foundation, Inc. + +#This file is not yet part of GNU GAS. + +#GNU GAS is free software; you can redistribute it and/or modify +#it under the terms of the GNU General Public License as published by +#the Free Software Foundation; either version 1, or (at your option) +#any later version. + +#GNU GAS is distributed in the hope that it will be useful, +#but WITHOUT ANY WARRANTY; without even the implied warranty of +#MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +#GNU General Public License for more details. + +#You should have received a copy of the GNU General Public License +#along with GNU GAS; see the file COPYING. If not, write to +#the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. + +# $Id$ + +# +# Shell script to create proper links to machine-dependent files in +# preparation for compiling gas. +# +# Usage: configure [-srcdir=DIR] [-host=HOST] TARGET +# +# If configure succeeds, it leaves its status in config.status. +# If configure fails after disturbing the status quo, +# config.status is removed. +# + +progname=$0 + +remove=rm +hard_link=ln +symbolic_link='ln -s' + +host= +target= + +#for Test +#remove="echo rm" +#hard_link="echo ln" +#symbolic_link="echo ln -s" + +for arg in $*; +do + case $arg in + -srcdir=* | +srcdir=* | +srcdi=* | +srcd=* | +src=* | +sr=* | +s=*) + srcdir=`echo $arg | sed 's/[+-]s[a-z]*=//'` + ;; + -host=* | +host=* | +hos=* | +ho=* | +h=*) + host=`echo $arg | sed 's/[+-]h[a-z]*=//'` + ;; + *) +# Allow configure HOST TARGET + if [ x$host = x ] + then + host=$target + fi + target=$arg + ;; + esac +done + +# Complain if an arg is missing +if [ x$target = x ] +then + echo "Usage: $progname [+srcdir=DIR] [+host=HOST] TARGET" + echo -n "Where HOST and TARGET are something like " + echo "\`vax', \`sun3', \`encore', etc." + if [ -r config.status ] + then + cat config.status + fi + exit 1 +fi + +# Default other arg +if [ x$host = x ] +then + host=$target +fi + +# Find the source files, if location was not specified. +if [ x$srcdir = x ] +then + srcdirdefaulted=1 + srcdir=. + if [ ! -r as.c ] + then + srcdir=.. + fi +fi + +if [ ! -r ${srcdir}/as.c ] +then + if [ x$srcdirdefaulted = x ] + then + echo "$progname: Can't find assembler sources in \`${srcdir}'." 1>&2 + else + echo "$progname: Can't find assembler sources in \`.' or \`..'." 1>&2 + fi + exit 1 +fi + +# Decode the host machine, then the target machine. +# For the host machine, we save the ho variable as host_ho; +# then we decode the target machine and forget everything else +# that came from the host machine. +for machine in $host $target; do + tc= + obj= + + host_header= + obj_header= + obj_source= + te_header= + tc_header= + tc_source= + + make_var_file= + + case $machine in + generic) + ;; + i860) + tc=i860 + obj=aout + ;; + pmax | dec3100) + ho=pmax + ;; + sun386) + ho=sun386 + ;; + sun4 | sun4-aout | sun-4 | sun4-os4 | sun-4-os4) + ho=sun4 + tc=sparc + obj=aout + ;; + sun4-bout) + tc=sparc + obj=bout + ;; + sun4-bfd-sunos) + tc=sparc + obj=bfd-sunos + ;; + i960 | i960-coff) + tc=i960 + obj=coff + te=ic960 + ;; + i960-bout) + tc=i960 + obj=bout + ;; + i960-aout) + tc=i960 + obj=aout + ;; + sun3 | sun3-aout) + ho=sun3 + tc=m68k + obj=aout + te=sun3 + ;; + a29k | a29k-aout) + tc=a29k + obj=aout + ;; + a29k-coff) + tc=a29k + obj=coff + ;; + i386) + tc=i386 + obj=aout + ;; + ns32k) + tc=ns32k + obj=aout + ;; + vax) + tc=vax + obj=aout + ;; + rs6000) + ;; + esac + if [ x$pass1done = x ] + then + if [ x$ho = x ]; then ho=$host; fi + if [ x$ho_header = x ]; then ho_ho_header=ho-$ho.h + else ho_ho_header=$ho_header + fi + if [ x$make_var_file = x ] + then make_var_file=make-$ho; fi + ho_make_var_file=$make_var_file + pass1done=yes + else + host_make_var_file=$ho_make_var_file + ho_header=$ho_ho_header + fi +done + + +# Default the machine-specific variables that were not explicitly set. +if [ x$te = x ] +then te=generic; fi + +if [ x$te_header = x ] +then te_header=te-$te.h; fi + + +if [ x$tc = x ] +then tc=generic; fi + +if [ x$tc_header = x ] +then tc_header=tc-$tc.h; fi + +if [ x$tc_source = x ] +then tc_source=tc-$tc.c; fi + + +if [ x$obj = x ] +then obj=generic; fi + +if [ x$obj_header = x ] +then obj_header=obj-$obj.h; fi + +if [ x$obj_source = x ] +then obj_source=obj-$obj.c; fi + + +if [ x$atof_source = x ] +then atof_source=atof-ieee.c; fi + +# Set up the list of links to be made. +# $links is the list of link names, and $files is the list of names to link to. +files="$ho_header $te_header $tc_header $tc_source $obj_header $obj_source $atof_source" +links="host.h targ-env.h targ-cpu.h targ-cpu.c obj-format.h obj-format.c atof-targ.c" + +# Make the links. +while [ -n "$files" ] +do + # set file to car of files, files to cdr of files + set $files; file=$1; shift; files=$* + set $links; link=$1; shift; links=$* + + if [ ! -r ${srcdir}/config/$file ] + then + echo "$progname: cannot create a link \`$link'," 1>&2 + echo "since the file \`config/$file' does not exist." 1>&2 + exit 1 + fi + + $remove -f $link + rm -f config.status + # Make a symlink if possible, otherwise try a hard link + $symbolic_link ${srcdir}/config/$file $link 2>/dev/null || $hard_link ${srcdir}/config/$file $link + + if [ ! -r $link ] + then + echo "$progname: unable to link \`$link' to \`${srcdir}/config/$file'." 1>&2 + exit 1 + fi + echo "Linked \`$link' to \`${srcdir}/config/$file'." +done + +# Build a Makefile + +# Install a makefile, and make it set srcdir +# if necessary so that the sources are found. +# Also change its value of srcdir. +# Also create a .gdbinit file which runs the one in srcdir +# and tells GDB to look there for source files. +case $srcdir in +.) + ;; +*) + echo "VPATH = ${srcdir}" > x + cat x ${srcdir}/Makefile.in | sed "s@^srcdir = \.@srcdir = ${srcdir}@" > Makefile.in + rm x + echo "dir ." > .gdbinit + echo "dir ${srcdir}" >> .gdbinit + echo "source ${srcdir}/.gdbinit" >> .gdbinit + ;; +esac + +# Conditionalize the makefile for this machine. +if [ -f ${srcdir}/config/${host_make_var_file} ] +then + sed -e "/####/ r ${srcdir}/config/${host_make_var_file}" Makefile.in > Makefile.tem +else + cp Makefile.in Makefile.tem +fi + +# Remove all formfeeds, since some Makes get confused by them. +sed "s/ //" Makefile.tem > Makefile.tem1 + +# Delete the intermediate files +rm Makefile.tem +if [ x$srcdir != x. ] +then + rm Makefile.in +fi + + +# actual Makefile starts here. + +echo "host = $host" > Makefile +echo "target = $target" >> Makefile + +# Define macro CROSS_ASSEMBLE in compilation if this is a cross-assembler. +if [ x$host = x$target ] +then + sed "/^ALL=gas/s//ALL=bootstrap/" < Makefile.tem1 >> Makefile +else + echo "CROSS=-DCROSS_ASSEMBLE" >> Makefile + cat Makefile.tem1 >> Makefile +fi + +rm Makefile.tem1 + +echo "Edited the makefile" + +if [ x$host = x$target ] +then + echo "Links are now set up for use with a $target." \ + | tee config.status +else + echo "Links are now set up for host $host and target $target." \ + | tee config.status +fi + +exit 0 diff --git a/gas/doc/a29k.m4 b/gas/doc/a29k.m4 new file mode 100644 index 0000000..cf3ba386 --- /dev/null +++ b/gas/doc/a29k.m4 @@ -0,0 +1,5 @@ +_divert__(-1) +_define__(<_AMD29K__>,<1>) +_define__(<_HOST__>,<AMD 29K>) +_define__(<_MACH_DEP__>,<AMD29K Dependent> +_divert__<>
\ No newline at end of file diff --git a/gas/doc/as.texinfo b/gas/doc/as.texinfo index ee3c3d2..e9f45cd 100644 --- a/gas/doc/as.texinfo +++ b/gas/doc/as.texinfo @@ -1,15 +1,86 @@ -\input texinfo @c -*-texinfo-*- -@tex -\special{twoside} -@end tex -@setfilename as -@settitle as +\input texinfo +@c @tex +@c \special{twoside} +@c @end tex +_if__(_ALL_ARCH__) +@setfilename as.info +_fi__(_ALL_ARCH__) +_if__(_AMD29K__ && !_ALL_ARCH__) +@setfilename as-29k.info +_fi__(_AMD29K__ && !_ALL_ARCH__) +_if__(_I960__ && !_ALL_ARCH__) +@setfilename as-960.info +_fi__(_I960__ && !_ALL_ARCH__) +_if__(_M680X0__ && !_ALL_ARCH__) +@setfilename as-m680x0.info +_fi__(_M680X0__ && !_ALL_ARCH__) +@c +@c NOTE: this manual is marked up for preprocessing with a collection +@c of m4 macros called "pretex.m4". If you see <_if__> and <_fi__> +@c scattered around the source, you have the full source before +@c preprocessing; if you don't, you have the source configured for +@c _HOST__ architectures (and you can of course get the full source, +@c with all configurations, from wherever you got this). +_if__(0) + +THIS IS THE FULL SOURCE. The full source needs to be run through m4 +before either tex- or info- formatting: for example, + m4 pretex.m4 none.m4 m680x0.m4 as.texinfo >as-680x0.texinfo +will produce (assuming your path finds either GNU or SysV m4; Berkeley +won't do) a file suitable for formatting. See the text in "pretex.m4" +for a fuller explanation (and the macro definitions). + +_fi__(0) +@c +@synindex ky cp +@ifinfo +This file documents the GNU Assembler "_AS__". + +Copyright (C) 1991 Free Software Foundation, Inc. + +Permission is granted to make and distribute verbatim copies of +this manual provided the copyright notice and this permission notice +are preserved on all copies. + +@ignore +Permission is granted to process this file through Tex and print the +results, provided the printed document carries copying permission +notice identical to this one except for the removal of this paragraph +(this paragraph not being relevant to the printed manual). + +@end ignore +Permission is granted to copy and distribute modified versions of this +manual under the conditions for verbatim copying, provided also that the +section entitled ``GNU General Public License'' is included exactly as +in the original, and provided that the entire resulting derived work is +distributed under the terms of a permission notice identical to this +one. + +Permission is granted to copy and distribute translations of this manual +into another language, under the above conditions for modified versions, +except that the section entitled ``GNU General Public License'' may be +included in a translation approved by the author instead of in the +original English. +@end ifinfo +@iftex +@finalout +@end iftex +@smallbook +@setchapternewpage odd +_if__(_ALL_ARCH__) +@settitle Using _AS__ +_fi__(_ALL_ARCH__) +_if__(!_ALL_ARCH__) +@settitle Using _AS__ (_HOST__) +_fi__(!_ALL_ARCH__) @titlepage -@center @titlefont{as} +@title{Using _AS__} +@subtitle{The GNU Assembler} +_if__(!_ALL_ARCH__) +@subtitle{for the _HOST__ family} +_fi__(!_ALL_ARCH__) @sp 1 -@center The GNU Assembler -@sp 2 -@center Dean Elsner, Jay Fenlason & friends +@subtitle March 1991 @sp 13 The Free Software Foundation Inc. thanks The Nice Computer Company of Australia for loaning Dean Elsner to write the @@ -18,462 +89,551 @@ The proprietors, management and staff of TNCCA thank FSF for distracting the boss while they got some work done. @sp 3 +@author{Dean Elsner, Jay Fenlason & friends} +@author{revised by Roland Pesch for Cygnus Support} +@c pesch@cygnus.com +@page +@tex +\def\$#1${{#1}} % Kluge: collect RCS revision info without $...$ +\xdef\manvers{\$Revision$} % For use in headers, footers too +{\parskip=0pt +\hfill Cygnus Support\par +\hfill \manvers\par +\hfill \TeX{}info \texinfoversion\par +} +%"boxit" macro for figures: +%Modified from Knuth's ``boxit'' macro from TeXbook (answer to exercise 21.3) +\gdef\boxit#1#2{\vbox{\hrule\hbox{\vrule\kern3pt + \vbox{\parindent=0pt\parskip=0pt\hsize=#1\kern3pt\strut\hfil +#2\hfil\strut\kern3pt}\kern3pt\vrule}\hrule}}%box with visible outline +\gdef\ibox#1#2{\hbox to #1{#2\hfil}\kern8pt}% invisible box +@end tex -Copyright @copyright{} 1986,1987 Free Software Foundation, Inc. +@vskip 0pt plus 1filll +Copyright @copyright{} 1991 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. -@ignore -Permission is granted to process this file through Tex and print the -results, provided the printed document carries copying permission -notice identical to this one except for the removal of this paragraph -(this paragraph not being relevant to the printed manual). - -@end ignore Permission is granted to copy and distribute modified versions of this -manual under the conditions for verbatim copying, provided that the entire -resulting derived work is distributed under the terms of a permission -notice identical to this one. +manual under the conditions for verbatim copying, provided also that the +section entitled ``GNU General Public License'' is included exactly as +in the original, and provided that the entire resulting derived work is +distributed under the terms of a permission notice identical to this +one. Permission is granted to copy and distribute translations of this manual -into another language, under the same conditions as for modified versions. - +into another language, under the above conditions for modified versions, +except that the section entitled ``GNU General Public License'' may be +included in a translation approved by the author instead of in the +original English. @end titlepage -@node top, Syntax, top, top -@chapter Overview, Usage -@menu -* Syntax:: The (machine independent) syntax that assembly language - files must follow. The machine dependent syntax - can be found in the machine dependent section of - the manual for the machine that you are using. -* Segments:: How to use segments and subsegments, and how the - assembler and linker will relocate things. -* Symbols:: How to set up and manipulate symbols. -* Expressions:: And how the assembler deals with them. -* PseudoOps:: The assorted machine directives that tell the - assembler exactly what to do with its input. -* MachineDependent:: Information specific to each machine. -* Maintenance:: Keeping the assembler running. -* Retargeting:: Teaching the assembler about new machines. -@end menu - -This document describes the GNU assembler @code{as}. This document -does @emph{not} describe what an assembler does, or how it works. -This document also does @emph{not} describe the opcodes, registers -or addressing modes that @code{as} uses on any paticular computer -that @code{as} runs on. Consult a good book on assemblers or the -machine's architecture if you need that information. - -This document describes the directives that @code{as} understands, -and their syntax. This document also describes some of the -machine-dependent features of various flavors of the assembler. +@page +@node Top,,, +@ifinfo +This file is a user guide to the GNU assembler @code{_AS__}. +_if__(!_ALL_ARCH__) +This version of the file describes @code{_AS__} configured to generate +code for _HOST__ architectures. +_fi__(!_ALL_ARCH__) +@end ifinfo +@node Overview,,, +@chapter Overview +@iftex +This manual is a user guide to the GNU assembler @code{_AS__}. +_if__(!_ALL_ARCH__) +This version of the manual describes @code{_AS__} configured to generate +code for _HOST__ architectures. +_fi__(!_ALL_ARCH__) +@end iftex + +@node Invoking,,, +@section Invoking @code{_AS__} + +Here is a brief summary of how to invoke @code{_AS__}. For details, +@pxref{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__ [ -D ] [ -f ] [ -I @var{path} ] [ -k ] [ -L ] + [ -o @var{objfile} ] [ -R ] [ -v ] [ -w ] +_if__(_AMD29K__) +@c am29k has no machine-dependent assembler options +_fi__(_AMD29K__) +_if__(_I960__) +@c see md_parse_option in i960.c + [ -ACA | -ACA_A | -ACB | -ACC | -AKA | -AKB | -AKC | -AMC ] + [ -b ] [ -norelax ] +_fi__(_I960__) +_if__(_M680X0__) + [ -l ] [ -mc68000 | -mc68010 | -mc68020 ] +_fi__(_M680X0__) + [ -- | @var{files} @dots{} ] +@end smallexample + +@table @code + +@item -D +This option is accepted only for script compatibility with calls to +other assemblers; it has no effect on @code{_AS__}. + +@item -f +``fast''---skip preprocessing (assume source is compiler output) + +@item -I @var{path} +Add @var{path} to the search list for @code{.include} directives + +@item -k +_if__(_AMD29K__ || _I960__) +This option is accepted but has no effect on the _HOST__ family. +_fi__(_AMD29K__ || _I960__) +_if__(!(_AMD29K__||_I960__)) +Issue warnings when difference tables altered for long displacements +_fi__(!(_AMD29K__||_I960__)) + +@item -L +Keep (in symbol table) local symbols, starting with @samp{L} + +@item -o @var{objfile} +Name the object-file output from @code{_AS__} + +@item -R +Fold data segment into text segment + +@item -W +Suppress warning messages + +_if__(_I960__) +@item -ACA | -ACA_A | -ACB | -ACC | -AKA | -AKB | -AKC | -AMC +Specify which variant of the 960 architecture is the target. + +@item -b +Add code to collect statistics about branches taken. + +@item -norelax +Do not alter compare-and-branch instructions for long displaements; +error if necessary. +_fi__(_I960__) + +_if__(_M680X0__) +@item -l +Shorten references to undefined symbols, to one word instead of two + +@item -mc68000 | -mc68010 | -mc68020 +Specify what processor in the 68000 family is the target (default 68020) +_fi__(_M680X0__) + +@item -- | @var{files} @dots{} +Source files to assemble, or standard input +@end table + +@node Manual, GNU Assembler, Invoking, Overview +@section Structure of this Manual +This document is intended to describe what you need to know to use +@code{_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__}. + +_if__(!_ALL_ARCH__) +We also cover special features in the _HOST__ +configuration of @code{_AS__}, including assembler directives. +_fi__(!_ALL_ARCH__) +_if__(_ALL_ARCH__) +This document also describes some of the machine-dependent features of +various flavors of the assembler. +_fi__(_ALL_ARCH__) +_if__(_INTERNALS__) This document 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__) +@refill +On the other hand, this manual is @emph{not} intended as an introduction +to programming in assembly language---let alone programming in general! +In a similar vein, we make no attempt to introduce the machine +architecture; we do @emph{not} describe the instruction set, standard +mnemonics, registers or addressing modes that are standard to a +particular architecture. You may want to consult the manufacturer's +machine architecture manual for this information. + +@c I think this is premature---pesch@cygnus.com, 17jan1991 +@ignore Throughout this document, we assume that you are running @dfn{GNU}, the portable operating system from the @dfn{Free Software Foundation, Inc.}. This restricts our attention to certain kinds of -computer (in paticular, the kinds of computers that GNU can run on); +computer (in particular, the kinds of computers that GNU can run on); once this assumption is granted examples and definitions need less qualification. -Readers should already comprehend: -@itemize @bullet -@item -Central processing unit -@item -registers -@item -memory address -@item -contents of memory address -@item -bit -@item -8-bit byte -@item -2's complement arithmetic -@end itemize - -@code{as} is part of a team of programs that turn a high-level +@code{_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. In paticular, -at the moment, @code{as} only works for the DEC Vax, the Motorola -680x0, the Intel 80386, the Sparc, and the National Semiconductor -32032/32532. - -@section Notation -GNU and @code{as} assume the computer that will run the programs it -assembles will obey these rules. - -A (memory) @dfn{address} is 32 bits. The lowest address is zero. - -The @dfn{contents} of any memory address is one @dfn{byte} of -exactly 8 bits. - -A @dfn{word} is 16 bits stored in two bytes of memory. The addresses -of the bytes differ by exactly 1. Notice that the interpretation of -the bits in a word and of how to address a word depends on which -particular computer you are assembling for. - -A @dfn{long word}, or @dfn{long}, is 32 bits composed of four bytes. -It is stored in 4 bytes of memory; these bytes have contiguous -addresses. Again the interpretation and addressing of those bits is -machine dependent. National Semiconductor 32x32 computers say -@i{double word} where we say @i{long}. - -Numeric quantities are usually @i{unsigned} or @i{2's complement}. -Bytes, words and longs may store numbers. @code{as} manipulates -integer expressions as 32-bit numbers in 2's complement format. -When asked to store an integer in a byte or word, the lowest order -bits are stored. The order of bytes in a word or long in memory is -determined by what kind of computer will run the assembled program. -We won't mention this important @i{caveat} again. - -The meaning of these terms has changed over time. Although @i{byte} -used to mean any length of contiguous bits, @i{byte} now pervasively -means exactly 8 contiguous bits. A @i{word} of 16 bits made sense -for 16-bit computers. Even on 32-bit computers, a @i{word} still -means 16 bits (to machine language programmers). To many other -programmers of GNU a @i{word} means 32 bits, so beware. Similarly -@i{long} means 32 bits: from ``long word''. National Semiconductor -32x32 machine language calls a 32-bit number a ``double word''. - -@example - - Names for integers of different sizes: some conventions - - -length as vax 32x32 680x0 GNU C -(bits) - - 8 byte byte byte byte char - 16 word word word word short (int) - 32 long long(-word) double-word long(-word) long (int) - 64 quad quad(-word) -128 octa octa-word - -@end example - -@section as, the GNU Assembler -@dfn{As} is an assembler; it is one of the team of programs that -`compile' your programs into the binary numbers that a computer uses -to `run' your program. Often @code{as} reads a @i{source} program -written by a compiler and writes an @dfn{object} program for the -linker (sometimes referred to as a @dfn{loader}) @code{ld} to read. - -The source program consists of @dfn{statements} and comments. Each -statement might @dfn{assemble} to one (and only one) machine -language instruction or to one very simple datum. - -Mostly you don't have to think about the assembler because the -compiler invokes it as needed; in that sense the assembler is just -another part of the compiler. If you write your own assembly -language program, then you must run the assembler yourself to get an -object file suitable for linking. You can read below how to do this. - -@code{as} is only intended to assemble the output of the C compiler -@code{cc} for use by the linker @code{ld}. @code{as} tries to -assemble correctly everything that the standard assembler would -assemble, with a few exceptions (described in the machine-dependent -chapters.) Note that this doesn't mean @code{as} will use the same -syntax as the standard assembler. For example, we know of several -incompatable syntaxes for the 680x0. - -Each version of the assembler knows about just one kind of machine -language, but much is common between the versions, including object -file formats, (most) assembler directives (often called -@dfn{pseudo-ops)} and assembler syntax. - -Unlike older assemblers, @code{as} tries to assemble a source program -in one pass of the source file. This subtly changes the meaning of -the @kbd{.org} directive (@xref{Org}.). - -If you want to write assembly language programs, you must tell -@code{as} what numbers should be in a computer's memory, and which -addresses should contain them, so that the program may be executed -by the computer. Using symbols will prevent many bookkeeping -mistakes that can occur if you use raw numbers. - -@section Command Line Synopsis -@example -as [ options @dots{} ] [ file1 @dots{} ] -@end example +@code{_AS__} are used for different kinds of computer. +@end ignore -After the program name @code{as}, the command line may contain +@c There used to be a section "Terminology" here, which defined +@c "contents", "byte", "word", and "long". Defining "word" to any +@c particular size is confusing when the .word directive may generate 16 +@c bits on one machine and 32 bits on another; in general, for the user +@c version of this manual, none of these terms seem essential to define. +@c They were used very little even in the former draft of the manual; +@c this draft makes an effort to avoid them (except in names of +@c directives). + +@node GNU Assembler,,, +@section _AS__, the GNU Assembler +GNU @code{as} is really a family of assemblers. +_if__(!_ALL_ARCH__) +This manual describes @samp{_AS__}, a member of that family which is +configured for the _HOST__ architectures. +_fi__(!_ALL_ARCH__) +If you use (or have used) the GNU assembler on another architecture, you +should find a fairly similar environment. 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 + +@code{_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 +assembler would. +_if__(_VAX__) +Any exceptions are documented explicitly (@pxref{_MACH_DEP__}). +_fi__(_VAX__) +_if__(_ALL_ARCH__||_M680X0__) +This doesn't mean @code{_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__(_ALL_ARCH__||_M680X0__) + +Unlike older assemblers, @code{_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}). + +@node Object Formats,,, +@section Object File Formats +The GNU assembler can be configured to produce several alternative +object file formats. +_if__(!_ALL_ARCH__) +_if__(!_I960__) +@code{_AS__} is configured to produce @code{a.out} format object +files.@refill +_fi__(!_I960__) +_if__(_I960__) +@code{_AS__} can be configured to produce either @code{b.out} or COFF +format object files. +_fi__(_I960__) +_fi__(!_ALL_ARCH__) + +@node Command Line,,, +@section Command Line + +After the program name @code{_AS__}, the command line may contain options and file names. Options may be in any order, and may be before, after, or between file names. The order of file names is significant. -@subsection Options +@file{--} (two hyphens) by itself names the standard input file +explicitly, as one of the files for @code{_AS__} to assemble. 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 -option is a @samp{-} followed by one ore more letters; the case of -the letter is important. No option (letter) should be used twice on -the same command line. (Nobody has decided what two copies of the -same option should mean.) All options are optional. +@code{_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. Some options expect exactly one file name to follow them. The file name may either immediately follow the option's letter (compatible with older assemblers) or it may be the next command argument (GNU standard). These two command lines are equivalent: -@example -as -o my-object-file.o mumble -as -omy-object-file.o mumble -@end example - -Always, @file{--} (that's two hyphens, not one) by itself names the -standard input file. +@smallexample +_AS__ -o my-object-file.o mumble.s +_AS__ -omy-object-file.o mumble.s +@end smallexample -@section Input File(s) +@node Input Files, Object, Command Line, Overview +@section Input Files -We use the words @dfn{source program}, abbreviated @dfn{source}, to -describe the program input to one run of @code{as}. The program may +We use the phrase @dfn{source program}, abbreviated @dfn{source}, to +describe the program input to one run of @code{_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 text is a catenation of the text in each file. +@c I added "con" prefix to "catenation" just to prove I can overcome my +@c APL training... pesch@cygnus.com +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 -program. A source program text is made of one or more files. +Each time you run @code{_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{_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 @code{as} is given no file -names it attempts to read one input file from @code{as}'s standard -input. - -Use @file{--} if you need to explicitly name the standard input file -in your command line. +is taken to be an input file name. -It is OK to assemble an empty source. @code{as} will produce a -small, empty object file. +If @code{_AS__} is given 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 +to assemble. -If you try to assemble no files then @code{as} will try to read -standard input, which is normally your terminal. You may have to -type @key{ctl-D} to tell @code{as} there is no more program to -assemble. +Use @samp{--} if you need to explicitly name the standard input file +in your command line. -@subsection Input Filenames and Line-numbers -A line is text up to and including the next newline. The first line -of a file is numbered @b{1}, the next @b{2} and so on. +If the source is empty, @code{_AS__} will produce a small, empty object +file. -There are two ways of locating a line in the input file(s) and both +@node Filenames, , Input Files, Input Files +@subsection Filenames and Line-numbers +There are two ways of locating a line in the input file (or files) and both are used in reporting error messages. One way refers to a line number in a physical file; the other refers to a line number in a -logical file. +``logical'' file. @dfn{Physical files} are those files named in the command line given -to @code{as}. +to @code{_AS__}. -@dfn{Logical files} are ``pretend'' files which bear no relation to -physical files. Logical file names help error messages reflect the -proper source file. Often they are used when @code{as}' source is -itself synthesized from other files. +@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__} +source is itself synthesized from other files. @xref{App-File}. +@node Object, Errors, Input Files, Overview @section Output (Object) File -Every time you run @code{as} it produces an output file, which is +Every time you run @code{_AS__} it produces an output file, which is your assembly language program translated into numbers. This file -is the object file; named @code{a.out} unless you tell @code{as} to +is the object file, named @code{a.out} unless you tell @code{_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 +@file{a.out} is used for historical reasons: older assemblers were capable of assembling self-contained programs directly into a -runnable program. This may still work, but hasn't been tested. +runnable program. +@c This may still work, but hasn't been tested. -The object file is for input to the linker @code{ld}. It contains -assembled program code, information to help @code{ld} to integrate -the assembled program into a runnable file and (optionally) symbolic -information for the debugger. The precise format of object files is -described elsewhere. +The object file is meant for input to the linker @code{_LD__}. It contains +assembled program code, information to help @code{_LD__} integrate +the assembled program into a runnable file, and (optionally) symbolic +information for the debugger. @comment link above to some info file(s) like the description of a.out. @comment don't forget to describe GNU info as well as Unix lossage. +@node Errors, Options, Object, Overview @section Error and Warning Messages -@code{as} may write warnings and error messages to the standard -error file (usually your terminal). This should not happen when -@code{as} is run automatically by a compiler. Error messages are -useful for those (few) people who still write in assembly language. - -Warnings report an assumption made so that @code{as} could keep -assembling a flawed program. - -Errors report a grave problem that stops the assembly. +@code{_AS__} may write warnings and error messages to the standard error +file (usually your terminal). This should not happen when @code{_AS__} is +run automatically by a compiler. Warnings report an assumption made so +that @code{_AS__} could keep assembling a flawed program; errors report a +grave problem that stops the assembly. Warning messages have the format -@example -file_name:line_number:Warning Message Text -@end example -If a logical file name has been given (@xref{File}.) it is used for -the filename, otherwise the name of the current input file is used. -If a logical line number was given (@xref{Line}.) then it is used to -calculate the number printed, otherwise the actual line in the -current source file is printed. The message text is intended to be -self explanatory (In the grand Unix tradition). +@smallexample +file_name:@b{NNN}:Warning Message Text +@end smallexample +@noindent(where @b{NNN} is a line number). If a logical file name has +been given (@pxref{App-File}) it is used for the filename, otherwise the +name of the current input file is used. If a logical line number was +given +_if__(!_AMD29K__) +(@pxref{Line}) +_fi__(!_AMD29K__) +_if__(_AMD29K__) +(@pxref{Ln}) +_fi__(_AMD29K__) +then it is used to calculate the number printed, +otherwise the actual line in the current source file is printed. The +message text is intended to be self explanatory (in the grand Unix +tradition). @refill Error messages have the format -@example -file_name:line_number:FATAL:Error Message Text -@end example -The file name and line number are derived the same as for warning +@smallexample +file_name:@b{NNN}:FATAL:Error Message Text +@end smallexample +The file name and line number are derived as for warning messages. The actual message text may be rather less explanatory because many of them aren't supposed to happen. +@node Options, , Errors, Overview @section Options -@subsection -f Works Faster +This section describes command-line options available in @emph{all} +versions of the GNU assembler; @pxref{_MACH_DEP__}, for options specific +to the _HOST__. + +@subsection @code{-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__}. + +@subsection Work Faster: @code{-f} @samp{-f} should only be used when assembling programs written by a -(trusted) compiler. @samp{-f} causes the assembler to not bother -pre-processing the input file(s) before assembling them. Needless -to say, if the files actually need to be pre-processed (if the -contain comments, for example), @code{as} will not work correctly if +(trusted) compiler. @samp{-f} stops the assembler from pre-processing +the input file(s) before assembling them. +@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 @samp{-f} is used. - -@subsection -L Includes Local Labels -For historical reasons, labels beginning with @samp{L} (upper case -only) are called @dfn{local labels}. Normally you don't see such -labels because they are intended for the use of programs (like +@end quotation + +@subsection @code{.include} search path: @code{-I} @var{path} +Use this option to add a @var{path} to the list of directories +@code{_AS__} will search for files specified in @code{.include} directives +(@pxref{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__} searches any @samp{-I} directories +in the same order as they were specified (left to right) on the command +line. + +@subsection Difference Tables: @code{-k} +_if__(_AMD29K__ || _I960__) +On the _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__ +family does not have the addressing limitations that sometimes lead to this +alteration on other platforms. +_fi__(_AMD29K__ || _I960__) + +_if__(! (_AMD29K__ || _I960__) ) +@code{_AS__} sometimes alters the code emitted for directives of the form +@samp{.word @var{sym1}-@var{sym2}}; @pxref{Word}. +You can use the @samp{-k} option if you want a warning issued when this +is done. +_fi__(! (_AMD29K__ || _I960__) ) + +@subsection Include Local Labels: @code{-L} +Labels beginning with @samp{L} (upper case only) are called @dfn{local +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 debug with them. +Normally both @code{_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{_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}. +@code{_LD__} to preserve symbols whose names begin with @samp{L}. -@subsection -o Names the Object File -There is always one object file output when you run @code{as}. By +@subsection Name the Object File: @code{-o} +There is always one object file output when you run @code{_AS__}. By default it has the name @file{a.out}. 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{_AS__} will overwrite any existing file of the same name. -@subsection -R Folds Data Segment into Text Segment -@code{-R} tells @code{as} to write the object file as if all +@subsection Join Data and Text Segments: @code{-R} +@code{-R} tells @code{_AS__} to write the object file as if all data-segment data lives in the text segment. This is only done at the very last moment: your binary data are the same, but data segment parts are relocated differently. The data segment part of your object file is zero bytes long because all it bytes are appended to the text segment. (@xref{Segments}.) -When you use @code{-R} it would be nice to generate shorter address -displacements (possible because we don't have to cross segments) -between text and data segment. We don't do this simply for -compatibility with older versions of @code{as}. @code{-R} may work -this way in future. +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 segment). We refrain from doing this simply for compatibility with +older versions of @code{_AS__}. In future, @code{-R} may work this way. -@subsection -W Represses Warnings -@code{as} should never give a warning or error message when +@subsection Suppress Warnings: @code{-W} +@code{_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{_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, any warning is repressed. This option only -affects warning messages: it cannot change any detail of how -@code{as} assembles your file. Errors, which stop the assembly, are +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 still reported. -@section Special Features to support Compilers +@node Syntax, Segments, Overview, Top +@chapter Syntax +This chapter describes the machine-independent syntax allowed in a +source file. @code{_AS__} syntax is similar to what many other assemblers +use; it is inspired in BSD 4.2 +_if__(!_VAX__) +assembler. @refill +_fi__(!_VAX__) +_if__(_VAX__) +assembler, except that @code{_AS__} does not assemble Vax bit-fields. +_fi__(_VAX__) + +@node Pre-processing, Whitespace, Syntax, Syntax +@section Pre-processing + +The pre-processor: +@itemize @bullet +@item +adjusts and removes extra whitespace. It leaves one space or tab before +the keywords on a line, and turns any other whitespace on the line into +a single space. -In order to assemble compiler output into something that will work, -@code{as} will occasionlly do strange things to @samp{.word} -directives. In particular, when @code{gas} 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 -create a @dfn{secondary jump table}, immediately before the next -label. This @var{secondary jump table} will be preceeded by a -short-jump to the first byte after the table. The short-jump -prevents the flow-of-control from accidentally falling into the -table. Inside the table will be a long-jump to @code{sym2}. The -original @samp{.word} will contain @code{sym1} minus (the address of -the long-jump to sym2) If there were several @samp{.word sym1-sym2} -before the secondary jump table, all of them will be adjusted. If -ther was a @samp{.word sym3-sym4}, that also did not fit in sixteen -bits, a long-jump to @code{sym4} will be included in the secondary -jump table, and the @code{.word}(s), will be adjusted to contain -@code{sym3} minus (the address of the long-jump to sym4), etc. - -@emph{This feature may be disabled by compiling @code{as} with the -@samp{-DWORKING_DOT_WORD} option.} This feature is likely to confuse -assembly language programmers. +@item +removes all comments, replacing them with a single space, or an +appropriate number of newlines. -@node Syntax, Segments, top, top -@chapter Syntax -This chapter informally defines the machine-independent syntax -allowed in a source file. @code{as} has ordinary syntax; it tries -to be upward compatible from BSD 4.2 assembler except @code{as} does -not assemble Vax bit-fields. - -@section The Pre-processor -The preprocess phase handles several aspects of the syntax. The -pre-processor will be disabled by the @samp{-f} option, or if the -first line of the source file is @code{#NO_APP}. The option to -disable the pre-processor was designed to make compiler output -assemble as fast as possible. - -The pre-processor adjusts and removes extra whitespace. It leaves -one space or tab before the keywords on a line, and turns any other -whitespace on the line into a single space. - -The pre-processor removes all comments, replacing them with a single -space (for /* @dots{} */ comments), or an appropriate number of -newlines. - -The pre-processor converts character constants into the appropriate -numeric values. - -This means that excess whitespace, comments, and character constants +@item +converts character constants into the appropriate numeric values. +@end itemize + +Excess whitespace, comments, and character constants cannot be used in the portions of the input text that are not pre-processed. -If the first line of an input file is @code{#NO_APP} or the -@samp{-f} option is given, the input file will not be -pre-processed. Within such an input file, parts of the file can be -pre-processed by putting a line that says @code{#APP} before the -text that should be pre-processed, and putting a line that says -@code{#NO_APP} after them. This feature is mainly intend to support -asm statements in compilers whose output normally does not need to -be pre-processed. +If the first line of an input file is @code{#NO_APP} or the @samp{-f} +option is given, the input file will not be pre-processed. Within such +an input file, parts of the file can be pre-processed by putting a line +that says @code{#APP} before the text that should be pre-processed, and +putting a line that says @code{#NO_APP} after them. This feature is +mainly intend to support @code{asm} statements in compilers whose output +normally does not need to be pre-processed. +@node Whitespace, Comments, Pre-processing, Syntax @section Whitespace @dfn{Whitespace} is one or more blanks or tabs, in any order. Whitespace is used to separate symbols, and to make programs neater for people to read. Unless within character constants -(@xref{Characters}.), any whitespace means the same as exactly one +(@pxref{Characters}), any whitespace means the same as exactly one space. +@node Comments, Symbol Intro, Whitespace, Syntax @section Comments -There are two ways of rendering comments to @code{as}. In both +There are two ways of rendering comments to @code{_AS__}. In both cases the comment is equivalent to one space. Anything from @samp{/*} through the next @samp{*/} is a comment. +This means you may not nest these comments. -@example +@smallexample /* The only way to include a newline ('\n') in a comment is to use this sort of comment. */ + /* This sort of comment does not nest. */ -@end example +@end smallexample Anything from the @dfn{line comment} character to the next newline -considered a comment and is ignored. The line comment character is -@samp{#} on the Vax, and @samp{|} on the 680x0. -@xref{MachineDependent}. 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. +is considered a comment and is ignored. The line comment character is +_if__(_VAX__ || _I960__) +@samp{#} on the _HOST__; +_fi__(_VAX__ || _I960__) +_if__(_M680X0__) +@samp{|} on the 680x0; +_fi__(_M680X0__) +_if__(_AMD29K__) +@samp{;} for the AMD 29K family; +_fi__(_AMD29K__) +@pxref{_MACH_DEP__}. @refill + +_if__(_ALL_ARCH__) +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__(_ALL_ARCH__) To be compatible with past assemblers a special interpretation is given to lines that begin with @samp{#}. Following the @samp{#} an @@ -484,97 +644,110 @@ name. The rest of the line, if any, should be whitespace. If the first non-whitespace characters on the line are not numeric, the line is ignored. (Just like a comment.) -@example +@smallexample # This is an ordinary comment. # 42-6 "new_file_name" # New logical file name # This is logical line # 36. -@end example +@end smallexample This feature is deprecated, and may disappear from future versions -of @code{as}. +of @code{_AS__}. +@node Symbol Intro, Statements, Comments, Syntax @section Symbols A @dfn{symbol} is one or more characters chosen from the set of all letters (both upper and lower case), digits and the three characters -@samp{_.$}. No symbol may begin with a digit. Case is -significant. There is no length limit: all characters are -significant. Symbols are delimited by characters not in that set, -or by begin/end-of-file. (@xref{Symbols}.) +@samp{_.$}. No symbol may begin with a digit. Case is significant. +There is no length limit: all characters are significant. Symbols are +delimited by characters not in that set, or by the beginning of a file +(since the source program must end with a newline, the end of a file is +not a possible symbol delimiter). @xref{Symbols}. +@node Statements, Constants, Symbol Intro, Syntax @section Statements +_if__(!_AMD29K__) A @dfn{statement} ends at a newline character (@samp{\n}) or at a -semicolon (@samp{;}). The newline or semicolon is considered part -of the preceding statement. Newlines and semicolons within -character constants are an exception: they don't end statements. +semicolon (@samp{;}). The newline or semicolon is considered part of +the preceding statement. Newlines and semicolons within character +constants are an exception: they don't end statements. +_fi__(!_AMD29K__) +_if__(_AMD29K__) +A @dfn{statement} ends at a newline character (@samp{\n}) or an ``at'' +sign (@samp{@@}). The newline or at sign is considered part of the +preceding statement. Newlines and at signs within character constants +are an exception: they don't end statements. +_fi__(_AMD29K__) + It is an error to end any statement with end-of-file: the last -character of any input file should be a newline. +character of any input file should be a newline.@refill 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{_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. -An empty statement is OK, and may include whitespace. It is ignored. +An empty statement is allowed, and may include whitespace. It is ignored. -Statements begin with zero or more labels, followed by a @dfn{key -symbol} which determines what kind of statement it is. The key +@c "key symbol" is not used elsewhere in the document; seems pedantic to +@c @defn{} it in that case, as was done previously... pesch@cygnus.com, +@c 13feb91. +A statement begins with zero or more labels, optionally followed by a +key symbol which determines what kind of statement it is. The key symbol determines the syntax of the rest of the statement. If the -symbol begins with a dot (@t{.}) then the statement is an assembler -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. Different versions of @code{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. - -A label is usually a symbol immediately followed by a colon -(@code{:}). Whitespace before a label or after a colon is OK. You -may not have whitespace between a label's symbol and its colon. -Labels are explained below. -@xref{Labels}. - -@example +symbol begins with a dot @samp{.} then the statement is an assembler +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__(_ALL_ARCH__) +Different versions of @code{_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__(_ALL_ARCH__) + +A label is a symbol immediately followed by a colon (@code{:}). +Whitespace before a label or after a colon is permitted, but you may not +have whitespace between a label's symbol and its colon. @xref{Labels}. + +@smallexample label: .directive followed by something another$label: # This is an empty statement. instruction operand_1, operand_2, @dots{} -@end example +@end smallexample +@node Constants, , Statements, Syntax @section Constants A constant is a number, written so that its value is known by inspection, without knowing any context. Like this: -@example +@smallexample .byte 74, 0112, 092, 0x4A, 0X4a, 'J, '\J # All the same value. .ascii "Ring the bell\7" # A string constant. .octa 0x123456789abcdef0123456789ABCDEF0 # A bignum. .float 0f-314159265358979323846264338327\ 95028841971.693993751E-40 # - pi, a flonum. -@end example +@end smallexample -@node Characters, Strings, , Syntax +@node Characters, Numbers, Constants, Constants @subsection Character Constants -There are two kinds of character constants. @dfn{Characters} stand -for one character in one byte and their values may be used in +There are two kinds of character constants. A @dfn{character} stands +for one character in one byte and its value may be used in numeric expressions. String constants (properly called string -@i{literals}) are potentially many bytes and their values may not be +@emph{literals}) are potentially many bytes and their values may not be used in arithmetic expressions. -@node Strings, , Characters, Syntax +@node Strings, Chars, Characters, Characters @subsubsection Strings A @dfn{string} is written between double-quotes. It may contain -double-quotes or null characters. The way to get weird characters +double-quotes or null characters. The way to get special characters into a string is to @dfn{escape} these characters: precede them with -a backslash (@code{\}) character. For example @samp{\\} represents +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{_AS__} to interpret the second character literally as a backslash +(which prevents @code{_AS__} from recognizing the second @code{\} as an escape character). The complete list of escapes follows. @table @kbd -@item \EOF -A @kbd{\} followed by end-of-file erroneous. It is treated just -like an end-of-file without a preceding backslash. @c @item \a @c Mnemonic for ACKnowledge; for ASCII this is octal code 007. @item \b @@ -600,8 +773,8 @@ Mnemonic for horizontal Tab; for ASCII this is octal code 011. @c A hexadecimal character code. The numeric code is 3 hexadecimal digits. @item \ @var{digit} @var{digit} @var{digit} An octal character code. The numeric code is 3 octal digits. -For compatibility with other Unix systems, 8 and 9 are legal digits -with values 010 and 011 respectively. +For compatibility with other Unix systems, 8 and 9 are accepted as digits: +for example, @code{\008} has the value 010, and @code{\009} the value 011. @item \\ Represents one @samp{\} character. @c @item \' @@ -616,38 +789,50 @@ this character, because an unescaped @samp{"} would end the string. 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{_AS__} has no +other interpretation, so @code{_AS__} knows it is giving you the wrong code and warns you of the fact. @end table Which characters are escapable, and what those escapes represent, varies widely among assemblers. The current set is what we think -BSD 4.2 @code{as} recognizes, and is a subset of what most C +the BSD 4.2 assembler recognizes, and is a subset of what most C compilers recognize. If you are in doubt, don't use an escape sequence. +@node Chars, , Strings, Characters @subsubsection Characters A single character may be written as a single quote immediately followed by that character. The same escapes apply to characters as to strings. So if you want to write the character backslash, you must write @kbd{'\\} where the first @code{\} escapes the second -@code{\}. As you can see, the quote is an accent acute, not an -accent grave. A newline (or semicolon (@samp{;})) immediately -following an accent acute is taken as a literal character and does -not count as the end of a statement. The value of a character +@code{\}. As you can see, the quote is an acute accent, not a +grave accent. A newline +_if__(!_AMD29K__) +(or semicolon @samp{;}) +_fi__(!_AMD29K__) +_if__(_AMD29K__) +(or at sign @samp{@@}) +_fi__(_AMD29K__) +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: @kbd{'A} -means 65, @kbd{'B} means 66, and so on. +that character. @code{_AS__} assumes your character code is ASCII: +@kbd{'A} means 65, @kbd{'B} means 66, and so on. @refill +@node Numbers,,, @subsection Number Constants -@code{as} distinguishes 3 flavors of numbers according to how they -are stored in the target machine. @i{Integers} are numbers that -would fit into an @code{int} in the C language. @i{Bignums} are -integers, but they are stored in a more than 32 bits. @i{Flonums} +@code{_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} are floating point numbers, described below. +@node Integers,,, @subsubsection Integers +A binary integer is @samp{0b} or @samp{0B} followed by zero or more of +the binary digits @samp{01}. + An octal integer is @samp{0} followed by zero or more of the octal digits (@samp{01234567}). @@ -657,49 +842,59 @@ more digits (@samp{0123456789}). A hexadecimal integer is @samp{0x} or @samp{0X} followed by one or more hexadecimal digits chosen from @samp{0123456789abcdefABCDEF}. -Integers have the obvious values. To denote a negative integer, use -the unary operator @samp{-} discussed under expressions -(@xref{Unops}.). +Integers have the usual values. To denote a negative integer, use +the prefix operator @samp{-} discussed under expressions +(@pxref{Prefix Ops}). +@node Bignums,,, @subsubsection Bignums A @dfn{bignum} has the same syntax and semantics as an integer except that the number (or its negative) takes more than 32 bits to represent in binary. The distinction is made because in some places integers are permitted while bignums are not. +@node Flonums,,, @subsubsection Flonums -A @dfn{flonum} represents a floating point number. The translation -is complex: a decimal floating point number from the text is -converted by @code{as} to a generic binary floating point number of -more than sufficient precision. This generic floating point number -is converted to the particular computer's floating point format(s) -by a portion of @code{as} specialized to that computer. +A @dfn{flonum} represents a floating point number. The translation is +complex: a decimal floating point number from the text is converted by +@code{_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. 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. -@kbd{e} -is recommended. Case is not important. -(Any otherwise illegal letter will work here, -but that might be changed. Vax BSD 4.2 assembler -seems to allow any of @samp{defghDEFGH}.) +_if__(_AMD29K__) +One of the letters @samp{DFPRSX} (in upper or lower case), to tell +@code{_AS__} the rest of the number is a flonum. +_fi__(_AMD29K__) +_if__(_I960__) +One of the letters @samp{DFT} (in upper or lower case), to tell +@code{_AS__} the rest of the number is a flonum. +_fi__(_I960__) +_if__(!(_AMD29K__||_I960__)) +A letter, to tell @code{_AS__} the rest of the number is a flonum. @kbd{e} +is recommended. Case is not important. (Any otherwise illegal letter +will work here, but that might be changed. Vax BSD 4.2 assembler seems +to allow any of @samp{defghDEFGH}.) +_fi__(!(_AMD29K__||_I960__)) @item An optional sign: either @samp{+} or @samp{-}. @item -An optional integer part: zero or more decimal digits. +An optional @dfn{integer part}: zero or more decimal digits. @item -An optional fraction part: @samp{.} followed by zero +An optional @dfn{fraction part}: @samp{.} followed by zero or more decimal digits. @item An optional exponent, consisting of: @itemize @bullet @item -A letter; the exact significance varies according to -the computer that executes the program. @code{as} -accepts any letter for now. Case is not important. +An @samp{E} or @samp{e}. +@c I can't find a config where "EXP_CHARS" is other than 'eE', but in +@c principle this can perfectly well be different on different targets. @item Optional sign: either @samp{+} or @samp{-}. @item @@ -708,132 +903,185 @@ One or more decimal digits. @end itemize At least one of @var{integer part} or @var{fraction part} must be -present. The floating point number has the obvious value. - -The computer running @code{as} needs no floating point hardware. -@code{as} does all processing using integers. - -@node Segments, Symbols, Syntax, top -@chapter (Sub)Segments & Relocation -Roughly, a @dfn{segment} is a range of addresses, with no gaps, with -all data ``in'' those addresses being treated the same. For example -there may be a ``read only'' segment. - -The linker @code{ld} reads many object files (partial programs) and -combines their contents to form a runnable program. When @code{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. -That explanation is too simple, but it will suffice to explain how -@code{as} works. - -@code{ld} moves blocks of bytes of your program to their run-time +present. The floating point number has the usual base-10 value. + +@code{_AS__} does all processing using integers. Flonums are computed +independently of any floating point hardware in the computer running +@code{_AS__}. + +_if__(_I960__) +@c Bit fields are written as a general facility but are also controlled +@c by a conditional-compilation flag---which is as of now (21mar91) +@c turned on only by the i960 config of GAS. +@node Bit Fields,,, +@subsubsection Bit Fields +You can also define numeric constants as @dfn{bit fields}. +specify two numbers separated by a colon--- +@example +@var{mask}:@var{value} +@end example +@noindent +the first will act as a mask; @code{_AS__} will bitwise-and it with the +second value. + +The resulting number is then packed +_if__(_ALL_ARCH__) +(in host-dependent byte order) +_fi__(_ALL_ARCH__) +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, +more constants are generated, of the specified width, beginning with the +least significant digits.@refill + +The directives @code{.byte}, @code{.hword}, @code{.int}, @code{.long}, +@code{.short}, and @code{.word} accept bit-field arguments. +_fi__(_I960__) + +@node Segments, Symbols, Syntax, Top +@chapter Segments and Relocation + +@node Segs Background, _LD__ Segments, Segments, Segments +@section Background +Roughly, a segment is a range of addresses, with no gaps; all data +``in'' those addresses is treated the same for some particular purpose. +For example there may be a ``read only'' segment. + +The linker @code{_LD__} reads many object files (partial programs) and +combines their contents to form a runnable program. When @code{_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 segments. + +@code{_LD__} moves blocks of bytes of your program to their run-time addresses. These blocks slide to their run-time addresses as rigid -units; their length does not change and neither does the order of -bytes within them. Such a rigid unit is called a @i{segment}. -Assigning run-time addresses to segments is called -@dfn{relocation}. It includes the task of adjusting mentions of -object-file addresses so they refer to the proper run-time addresses. - -An object file written by @code{as} has three segments, any of which -may be empty. These are named @i{text}, @i{data} and @i{bss} -segments. Within the object file, the text segment starts at -address 0, the data segment follows, and the bss segment follows the -data segment. - -To let @code{ld} know which data will change when the segments are -relocated, and how to change that data, @code{as} also writes to the +units; their length does not change and neither does the order of bytes +within them. Such a rigid unit is called a @emph{segment}. Assigning +run-time addresses to segments is called @dfn{relocation}. It includes +the task of adjusting mentions of object-file addresses so they refer to +the proper run-time addresses. + +An object file written by @code{_AS__} has three segments, any of which may +be empty. These are named @dfn{text}, @dfn{data} and @dfn{bss} +segments. +_if__(_COFF__) + +@c Thanks, Rich! +@quotation +@emph{Warning:} @code{_AS__} can only assign output to one of these +three segments, even when configured for COFF output; the +@code{.section} directive is not supported. +@end quotation +_fi__(_COFF__) + +Within the object file, the text segment starts at address @code{0}, the +data segment follows, and the bss segment follows the data segment. + +To let @code{_LD__} know which data will change when the segments are +relocated, and how to change that data, @code{_AS__} also writes to the object file details of the relocation needed. To perform relocation -@code{ld} must know for each mention of an address in the object -file: +@code{_LD__} must know, each time an address in the object +file is mentioned: @itemize @bullet @item -At what address in the object file does this mention of -an address begin? +Where in the object file is the beginning of this reference to +an address? @item -How long (in bytes) is this mention? +How long (in bytes) is this reference? @item -Which segment does the address refer to? -What is the numeric value of (@var{address} @t{-} -@var{start-address of segment})? +Which segment does the address refer to? What is the numeric value of +@display +(@var{address}) @minus{} (@var{start-address of segment})? +@end display @item -Is the mention of an address ``Program counter relative''? +Is the reference to an address ``Program-Counter relative''? @end itemize -In fact, every address @code{as} ever thinks about is expressed as -(@var{segment} @t{+} @var{offset into segment}). Further, every -expression @code{as} computes is of this segmented nature. So -@dfn{absolute expression} means an expression with segment -``absolute'' (@xref{LdSegs}.). A @dfn{pass1 expression} means an -expression with segment ``pass1'' (@xref{MythSegs}.). In this -document ``(segment, offset)'' will be written as @{ segment-name -(offset into segment) @}. +In fact, every address @code{_AS__} ever uses is expressed as +@display +(@var{segment}) + (@var{offset into segment}) +@end display +@noindent +Further, every expression @code{_AS__} computes is of this segmented +nature. @dfn{Absolute expression} means an expression with segment +``absolute'' (@pxref{_LD__ Segments}). A @dfn{pass1 expression} means +an expression with segment ``pass1'' (@pxref{_AS__ Segments}). In this +manual we use the notation @{@var{segname} @var{N}@} to mean ``offset +@var{N} into segment @var{segname}''. Apart from text, data and bss segments you need to know about the -@dfn{absolute} segment. When @code{ld} mixes partial programs, -addresses in the absolute segment remain unchanged. That is, -address @{absolute 0@} is ``relocated'' to run-time address 0 by -@code{ld}. Although two partial programs' data segments will not -overlap addresses after linking, @b{by definition} their absolute -segments will overlap. Address @{absolute 239@} in one partial -program will always be the same address when the program is running -as address @{absolute 239@} in any other partial program. - -The idea of segments is extended to the @dfn{undefined} segment. -Any address whose segment is unknown at assembly time is by -definition rendered @{undefined (something, unknown yet)@}. Since -numbers are always defined, the only way to generate an undefined +@dfn{absolute} segment. When @code{_LD__} mixes partial programs, +addresses in the absolute segment remain unchanged. That is, address +@code{@{absolute 0@}} is ``relocated'' to run-time address 0 by @code{_LD__}. +Although two partial programs' data segments will not overlap addresses +after linking, @emph{by definition} their absolute segments will overlap. +Address @code{@{absolute@ 239@}} in one partial program will always be the same +address when the program is running as address @code{@{absolute@ 239@}} in any +other partial program. + +The idea of segments is extended to the @dfn{undefined} segment. Any +address whose segment is unknown at assembly time is by definition +rendered @{undefined @var{U}@}---where @var{U} will be filled in later. +Since numbers are always defined, the only way to generate an undefined address is to mention an undefined symbol. A reference to a named common block would be such a symbol: its value is unknown at assembly -time so it has segment @i{undefined}. +time so it has segment @emph{undefined}. -By analogy the word @i{segment} is to describe groups of segments in -the linked program. @code{ld} puts all partial program's text +By analogy the word @emph{segment} is used to describe groups of segments in +the linked program. @code{_LD__} puts all partial programs' text segments in contiguous addresses in the linked program. It is -customary to refer to the @i{text segment} of a program, meaning all +customary to refer to the @emph{text segment} of a program, meaning all the addresses of all partial program's text segments. Likewise for data and bss segments. -@section Segments -Some segments are manipulated by @code{ld}; others are invented for -use of @code{as} and have no meaning except during assembly. +Some segments are manipulated by @code{_LD__}; others are invented for +use of @code{_AS__} and have no meaning except during assembly. + +@node _LD__ Segments, _AS__ Segments, Segs Background, Segments +@section _LD__ Segments +@code{_LD__} deals with just five kinds of segments, summarized below. + +@table @strong -@node LdSegs, , , -@subsection ld segments -@code{ld} deals with just 5 kinds of segments, summarized below. -@table @b @item text segment @itemx data segment -These segments hold your program bytes. @code{as} and @code{ld} -treat them as separate but equal segments. Anything you can say of -one segment is true of the other. When the program is running -however it is customary for the text segment to be unalterable: it -will contain instructions, constants and the like. The data segment -of a running program is usually alterable: for example, C variables -would be stored in the data segment. +These segments hold your program. @code{_AS__} and @code{_LD__} treat them as +separate but equal segments. Anything you can say of one segment is +true of the other. When the program is running, however, it is +customary for the text segment to be unalterable. The +text segment is often shared among processes: it will contain +instructions, constants and the like. The data segment of a running +program is usually alterable: for example, C variables would be stored +in the data segment. + @item bss segment -This segment contains zeroed bytes when your program begins -running. It is used to hold unitialized variables or common -storage. The length of each partial program's bss segment is -important, but because it starts out containing zeroed bytes there -is no need to store explicit zero bytes in the object file. The Bss -segment was invented to eliminate those explicit zeros from object -files. +This segment contains zeroed bytes when your program begins running. It +is used to hold unitialized variables or common storage. The length of +each partial program's bss segment is important, but because it starts +out containing zeroed bytes there is no need to store explicit zero +bytes in the object file. The bss segment was invented to eliminate +those explicit zeros from object files. + @item absolute segment -Address 0 of this segment is always ``relocated'' to runtime address -0. This is useful if you want to refer to an address that @code{ld} -must not change when relocating. In this sense we speak of absolute -addresses being ``unrelocatable'': they don't change during -relocation. +Address 0 of this segment is always ``relocated'' to runtime address 0. +This is useful if you want to refer to an address that @code{_LD__} must +not change when relocating. In this sense we speak of absolute +addresses being ``unrelocatable'': they don't change during relocation. + @item undefined segment -This ``segment'' is a catch-all for address references to objects -not in the preceding segments. See the description of @file{a.out} -for details. +This ``segment'' is a catch-all for address references to objects not in +the preceding segments. +@c FIXME: ref to some other doc on obj-file formats could go here. + @end table -An idealized example of the 3 relocatable segments follows. Memory + +An idealized example of the three relocatable segments follows. Memory addresses are on the horizontal axis. -@example +@ifinfo +@smallexample +-----+----+--+ partial program # 1: |ttttt|dddd|00| +-----+----+--+ @@ -850,83 +1098,131 @@ linked program: | |TTT|ttttt| |dddd|DDD|00000| +--+---+-----+--+----+---+-----+~~ addresses: 0 @dots{} -@end example +@end smallexample +@end ifinfo +@tex + +{\it Partial program \#1: } + +\line{\ibox{2.5cm}{\tt text}\ibox{2cm}{\tt data}\ibox{1cm}{\tt bss}\hfil} +\line{\boxit{2.5cm}{\tt ttttt}\boxit{2cm}{\tt dddd}\boxit{1cm}{\tt 00}\hfil} + +{\it Partial program \#2:} + +\line{\ibox{1cm}{\tt text}\ibox{1.5cm}{\tt data}\ibox{1cm}{\tt bss}\hfil} +\line{\boxit{1cm}{\tt TTT}\boxit{1.5cm}{\tt DDDD}\boxit{1cm}{\tt 000}\hfil} + +{\it linked program: } + +\line{\ibox{.5cm}{}\ibox{1cm}{\tt text}\ibox{2.5cm}{}\ibox{.75cm}{}\ibox{2cm}{\tt data}\ibox{1.5cm}{}\ibox{2cm}{\tt bss}\hfil} +\line{\boxit{.5cm}{}\boxit{1cm}{\tt TTT}\boxit{2.5cm}{\tt +ttttt}\boxit{.75cm}{}\boxit{2cm}{\tt dddd}\boxit{1.5cm}{\tt +DDDD}\boxit{2cm}{\tt 00000}\ \dots\hfil} + +{\it addresses:} + +\line{0\dots\hfil} -@node MythSegs, , , -@subsection Mythical Segments -These segments are invented for the internal use of @code{as}. They +@end tex + +@node _AS__ Segments, Sub-Segments, _LD__ Segments, Segments +@section _AS__ Internal Segments +These segments are invented for the internal use of @code{_AS__}. They have no meaning at run-time. You don't need to know about these -segments except that they might be mentioned in @code{as}' warning +segments except that they might be mentioned in the @code{_AS__} warning messages. These segments are invented to permit the value of every expression in your assembly language program to be a segmented address. @table @b @item absent segment -An expression was expected and none was found. +An expression was expected and none was +found. + @item goof segment -An internal assembler logic error has been found. This means there -is a bug in the assembler. +An internal assembler logic error has been +found. This means there is a bug in the assembler. + @item grand segment -A @dfn{grand number} is a bignum or a flonum, but not an integer. -If a number can't be written as a C @code{int} constant, it is a -grand number. @code{as} has to remember that a flonum or a bignum -does not fit into 32 bits, and cannot be a primary (@xref{Primary}.) -in an expression: this is done by making a flonum or bignum be of -type ``grand''. This is purely for internal @code{as} convenience; -grand segment behaves similarly to absolute segment. +A @dfn{grand number} is a bignum or a flonum, but not an integer. If a +number can't be written as a C @code{int} constant, it is a grand +number. @code{_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 segment +grand. This is purely for internal @code{_AS__} convenience; grand +segment behaves similarly to absolute segment. + @item pass1 segment The expression was impossible to evaluate in the first pass. The -assembler will attempt a second pass (second reading of the source) -to evaluate the expression. Your expression mentioned an undefined -symbol in a way that defies the one-pass (segment + offset in -segment) assembly process. No compiler need emit such an expression. +assembler will attempt a second pass (second reading of the source) to +evaluate the expression. Your expression mentioned an undefined symbol +in a way that defies the one-pass (segment + offset in segment) assembly +process. No compiler need emit such an expression. + +@quotation +@emph{Warning:} the second pass is currently not implemented. @code{_AS__} +will abort with an error message if one is required. +@end quotation + @item difference segment As an assist to the C compiler, expressions of the forms -@itemize @bullet -@item -(undefined symbol) @t{-} (expression) -@item -(something) @t{-} (undefined symbol) -@item -(undefined symbol) @t{-} (undefined symbol) -@end itemize -are permitted to belong to the ``difference'' segment. @code{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 segment. -The intention is to permit statements like @samp{.word label - -base_of_table} to be assembled in one pass where both @code{label} -and @code{base_of_table} are undefined. This is useful for -compiling C and Algol switch statements, Pascal case statements, -FORTRAN computed goto statements and the like. +@display + (@var{undefined symbol}) @minus{} (@var{expression}) + @var{something} @minus{} (@var{undefined symbol}) + (@var{undefined symbol}) @minus{} (@var{undefined symbol}) +@end display +are permitted, and belong to the difference segment. @code{_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 segment. The +intention is to permit statements like +@samp{.word label - base_of_table} +to be assembled in one pass where both @code{label} and +@code{base_of_table} are undefined. This is useful for compiling C and +Algol switch statements, Pascal case statements, FORTRAN computed goto +statements and the like. @end table +@node Sub-Segments, bss, _AS__ Segments, Segments @section Sub-Segments -Assembled bytes fall into two segments: text and data. Because you -may have groups of text or data that you want to end up near to each -other in the object file, @code{as}, allows you to use +Assembled bytes fall into two segments: text and data. +Because you may have groups of text or data that you want to end up near +to each other in the object file, @code{_AS__} allows you to use @dfn{subsegments}. Within each segment, there can be numbered -subsegments with values from 0 to 8192. Objects assembled into the -same subsegment will be grouped with other objects in the same -subsegment when they are all put into the object file. For example, -a compiler might want to store constants in the text segment, but -might not want to have them intersperced with the program being -assembled. In this case, the compiler could issue a @code{text 0} -before each section of code being output, and a @code{text 1} before -each group of constants being output. - -Subsegments are optional. If you don't used subsegments, everything +subsegments with values from 0 to 8192. Objects assembled into the same +subsegment will be grouped with other objects in the same subsegment +when they are all put into the object file. For example, a compiler +might want to store constants in the text segment, but might not want to +have them interspersed with the program being assembled. In this case, +the compiler could issue a @code{text 0} before each section of code +being output, and a @code{text 1} before each group of constants being +output. + +Subsegments are optional. If you don't use subsegments, everything will be stored in subsegment number zero. +_if__(!(_AMD29K__||_I960__)) Each subsegment is zero-padded up to a multiple of four bytes. (Subsegments may be padded a different amount on different flavors -of @code{as}.) Subsegments appear in your object file in numeric -order, lowest numbered to highest. (All this to be compatible with -other people's assemblers.) The object file, @code{ld} @i{etc.} -have no concept of subsegments. They just see all your text -subsegments as a text segment, and all your data subsegments as a -data segment. +of @code{_AS__}.) +_fi__(!(_AMD29K__||_I960__)) +_if__(_I960__) +@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__) +_if__(_AMD29K__) +On the AMD 29K family, no particular padding is added to segment sizes; +_AS__ forces no alignment on this platform. +_fi__(_AMD29K__) +Subsegments appear in your object file in numeric order, lowest numbered +to highest. (All this to be compatible with other people's assemblers.) +The object file contains no representation of subsegments; @code{_LD__} and +other programs that manipulate object files will see no trace of them. +They just see all your text subsegments as a text segment, and all your +data subsegments as a data segment. To specify which subsegment you want subsequent statements assembled into, use a @samp{.text @var{expression}} or a @samp{.data @@ -935,7 +1231,7 @@ expression. (@xref{Expressions}.) If you just say @samp{.text} then @samp{.text 0} is assumed. Likewise @samp{.data} means @samp{.data 0}. Assembly begins in @code{text 0}. For instance: -@example +@smallexample .text 0 # The default subsegment is text 0 anyway. .ascii "This lives in the first text subsegment. *" .text 1 @@ -946,274 +1242,319 @@ For instance: .text 0 .ascii "This lives in the first text segment," .ascii "immediately following the asterisk (*)." -@end example - -Each segment has a @dfn{location counter} incremented by one for -every byte assembled into that segment. Because subsegments are -merely a convenience restricted to @code{as} there is no concept of -a subsegment location counter. There is no way to directly -manipulate a location counter. The location counter of the segment -that statements are being assembled into is said to be the +@end smallexample + +Each segment has a @dfn{location counter} incremented by one for every +byte assembled into that segment. Because subsegments are merely a +convenience restricted to @code{_AS__} there is no concept of a subsegment +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 +segment that statements are being assembled into is said to be the @dfn{active} location counter. -@section Bss Segment -The @code{bss} segment is used for local common variable storage. -You may allocate address space in the @code{bss} segment, but you may +@node bss, , Sub-Segments, Segments +@section bss Segment +The bss segment is used for local common variable storage. +You may allocate address space in the bss segment, but you may not dictate data to load into it before your program executes. When -your program starts running, all the contents of the @code{bss} +your program starts running, all the contents of the bss segment are zeroed bytes. -Addresses in the bss segment are allocated with a special statement; +Addresses in the bss segment are allocated with special directives; you may not assemble anything directly into the bss segment. Hence -there are no bss subsegments. +there are no bss subsegments. @xref{Comm}; @pxref{Lcomm}. -@node Symbols, Expressions, Segments, top +@node Symbols, Expressions, Segments, Top @chapter Symbols -Because the linker uses symbols to link, the debugger uses symbols -to debug and the programmer uses symbols to name things, symbols are -a central concept. Symbols do not appear in the object file in the -order they are declared. This may break some debuggers. +Symbols are a central concept: the programmer uses symbols to name +things, the linker uses symbols to link, and the debugger uses symbols +to debug. -@node Labels, , , Symbols +@quotation +@emph{Warning:} @code{_AS__} does not place symbols in the object file in +the same order they were declared. This may break some debuggers. +@end quotation + +@node Labels, Setting Symbols, Symbols, Symbols @section Labels A @dfn{label} is written as a symbol immediately followed by a colon -(@samp{:}). The symbol then represents the current value of the +@samp{:}. The symbol then represents the current value of the active location counter, and is, for example, a suitable instruction operand. You are warned if you use the same symbol to represent two different locations: the first definition overrides any other definitions. +@node Setting Symbols, Symbol Names, Labels, Symbols @section Giving Symbols Other Values -A symbol can be given an arbitrary value by writing a symbol followed -by an equals sign (@samp{=}) followed by an expression +A symbol can be given an arbitrary value by writing a symbol, followed +by an equals sign @samp{=}, followed by an expression (@pxref{Expressions}). This is equivalent to using the @code{.set} -directive. (@xref{Set}.) +directive. @xref{Set}. +@node Symbol Names, Dot, Setting Symbols, Symbols @section Symbol Names Symbol names begin with a letter or with one of @samp{$._}. That character may be followed by any string of digits, letters, underscores and dollar signs. Case of letters is significant: @code{foo} is a different symbol name than @code{Foo}. -Each symbol has exactly one name. Each name in an assembly program -refers to exactly one symbol. You may use that symbol name any -number of times in an assembly program. +_if__(_AMD29K__) +For the AMD 29K family, @samp{?} is also allowed in the +body of a symbol name, though not at its beginning. +_fi__(_AMD29K__) + +Each symbol has exactly one name. Each name in an assembly language +program refers to exactly one symbol. You may use that symbol name any +number of times in a program. +@node Local Symbols, , Symbol Names, Symbol Names @subsection Local Symbol Names Local symbols help compilers and programmers use names temporarily. -There are ten @dfn{local} symbol names, which are re-used throughout -the program. Their names are @samp{0} @samp{1} @dots{} @samp{9}. -To define a local symbol, write a label of the form -@var{digit}@t{:}. To refer to the most recent previous definition -of that symbol write @var{digit}@t{b}, using the same digit as when -you defined the label. To refer to the next definition of a local -label, write @var{digit}@t{f} where @var{digit} gives you a choice -of 10 forward references. The @samp{b} stands for ``backwards'' and -the @samp{f} stands for ``forwards''. - -Local symbols are not used by the current C compiler. +There are ten local symbol names, which are re-used throughout the +program. You may refer to them using the names @samp{0} @samp{1} +@dots{} @samp{9}. To define a local symbol, write a label of the form +@samp{@b{N}:} (where @b{N} represents any digit). To refer to the most +recent previous definition of that symbol write @samp{@b{N}b}, using the +same digit as when you defined the label. To refer to the next +definition of a local label, write @samp{@b{N}f}---where @b{N} gives you +a choice of 10 forward references. The @samp{b} stands for +``backwards'' and the @samp{f} stands for ``forwards''. + +Local symbols are not emitted by the current GNU C compiler. There is no restriction on how you can use these labels, but remember that at any point in the assembly you can refer to at most 10 prior local labels and to at most 10 forward local labels. -Local symbol names are only a notation device. They are immediately +Local symbol names are only a notation device. They are immediately transformed into more conventional symbol names before the assembler -thinks about them. The symbol names stored in the symbol table, -appearing in error messages and optionally emitted to the object -file have these parts: -@table @kbd +uses them. The symbol names stored in the symbol table, appearing in +error messages and optionally emitted to the object file have these +parts: + +@table @code @item L -All local labels begin with @samp{L}. Normally both @code{as} and -@code{ld} forget symbols that start with @samp{L}. These labels are +All local labels begin with @samp{L}. Normally both @code{_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 -object file. By instructing @code{ld} to also retain these symbols, +@samp{-L} option then @code{_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. -@item @i{a digit} + +@item @var{digit} If the label is written @samp{0:} then the digit is @samp{0}. If the label is written @samp{1:} then the digit is @samp{1}. And so on up through @samp{9:}. -@item @i{control}-A + +@item @ctrl{A} This unusual character is included so you don't accidentally invent a symbol of the same name. The character has ASCII value @samp{\001}. -@item @i{an ordinal number} -This is like a serial number to keep the labels distinct. The first + +@item @emph{ordinal number} +This is a serial number to keep the labels distinct. The first @samp{0:} gets the number @samp{1}; The 15th @samp{0:} gets the -number @samp{15}; @i{etc.}. Likewise for the other labels @samp{1:} +number @samp{15}; @emph{etc.}. Likewise for the other labels @samp{1:} through @samp{9:}. @end table -For instance, the -first @code{1:} is named @code{L1^A1}, the 44th @code{3:} is named @code{L3^A44}. +For instance, the first @code{1:} is named @code{L1@ctrl{A}1}, the 44th +@code{3:} is named @code{L3@ctrl{A}44}. + +@node Dot, Symbol Attributes, Symbol Names, Symbols @section The Special Dot Symbol -The special symbol @code{.} refers to the current address that -@code{as} is assembling into. Thus, the expression @samp{melvin: -.long .} will cause @var{melvin} to contain its own address. +The special symbol @samp{.} refers to the current address that +@code{_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 +_if__(!_AMD29K__) @samp{.space 4}. +_fi__(!_AMD29K__) +_if__(_AMD29K__) +@samp{.block 4}. +_fi__(_AMD29K__) +@node Symbol Attributes, , Dot, Symbols @section Symbol Attributes -Every symbol has the attributes discussed below. The detailed -definitions are in <a.out.h>. +Every symbol has, as well as its name, the attributes ``Value'' and +``Type''. Depending on output format, symbols also have auxiliary attributes. +_if__(_INTERNALS__) +The detailed definitions are in _0__<a.out.h>_1__. +_fi__(_INTERNALS__) -If you use a symbol without defining it, @code{as} assumes zero for +If you use a symbol without defining it, @code{_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. +@node Symbol Value, Symbol Type, Symbol Attributes, Symbol Attributes @subsection Value -The value of a symbol is (usually) 32 bits, the size of one C -@code{int}. For a symbol which labels a location in the -@code{text}, @code{data}, @code{bss} or @code{Absolute} segments the -value is the number of addresses from the start of that segment to -the label. Naturally for @code{text} @code{data} and @code{bss} -segments the value of a symbol changes as @code{ld} changes segment -base addresses during linking. @code{absolute} symbols' values do -not change during linking: that is why they are called absolute. - -The value of an undefined symbol is treated in a special way. If it -is 0 then the symbol is not defined in this assembler source -program, and @code{ld} will try to determine its value from other -programs it is linked with. You make this kind of symbol simply by -mentioning a symbol name without defining it. A non-zero value -represents a @code{.comm} common declaration. The value is how much -common storage to reserve, in bytes (@i{i.e.} addresses). The -symbol refers to the first address of the allocated storage. - +The value of a symbol is (usually) 32 bits, the size of one GNU C +@code{int}. For a symbol which labels a location in the text, data, bss +or absolute segments the value is the number of addresses from the start +of that segment to the label. Naturally for text, data and bss segments +the value of a symbol changes as @code{_LD__} changes segment base +addresses during linking. Absolute symbols' values do not change during +linking: that is why they are called absolute. + +The value of an undefined symbol is treated in a special way. If it is +0 then the symbol is not defined in this assembler source program, and +@code{_LD__} will try to determine its value from other programs it is +linked with. You make this kind of symbol simply by mentioning a symbol +name without defining it. A non-zero value represents a @code{.comm} +common declaration. The value is how much common storage to reserve, in +bytes (addresses). The symbol refers to the first address of the +allocated storage. + +@node Symbol Type, Symbol Desc, Symbol Value, Symbol Attributes @subsection Type -The type attribute of a symbol is 8 bits encoded in a devious way. -We kept this coding standard for compatibility with older operating -systems. - -@example - - 7 6 5 4 3 2 1 0 bit numbers - +-----+-----+-----+-----+-----+-----+-----+-----+ - | | | | - | N_STAB bits | N_TYPE bits |N_EXT| - | | | bit | - +-----+-----+-----+-----+-----+-----+-----+-----+ - - n_type byte -@end example - -@subsubsection N_EXT bit -This bit is set if @code{ld} might need to use the symbol's value -and type bits. If this bit is re-set then @code{ld} can ignore the -symbol while linking. It is set in two cases. If the symbol is -undefined, then @code{ld} is expected to find the symbol's value -elsewhere in another program module. Otherwise the symbol has the -value given, but this symbol name and value are revealed to any other -programs linked in the same executable program. This second use of -the @code{N_EXT} bit is most often done by a @code{.globl} statement. - -@subsubsection N_TYPE bits -These establish the symbol's ``type'', which is mainly a relocation -concept. Common values are detailed in the manual describing the -executable file format. - -@subsubsection N_STAB bits -Common values for these bits are described in the manual on the -executable file format. - -@subsection Desc(riptor) +The type attribute of a symbol contains relocation (segment) +information, any flag settings indicating that a symbol is external, and +(optionally), other information for linkers and debuggers. The exact +format depends on the object-code output format in use. + +_if__(_AOUT__||_BOUT__) +@node a.out Symbols,,, +@subsection Symbol Attributes: @code{a.out}, @code{b.out} +These symbol attributes appear only when @code{_AS__} is configured for +one of the Berkeley-descended object output formats. + +@node Symbol Desc, Symbol Other, Symbol Type, Symbol Attributes +@subsubsection Descriptor This is an arbitrary 16-bit value. You may establish a symbol's -descriptor value by using a @code{.desc} statement (@xref{Desc}.). -A descriptor value means nothing to @code{as}. - -@subsection Other -This is an arbitrary 8-bit value. It means nothing to @code{as}. - -@node Expressions, PseudoOps, Symbols, top +descriptor value by using a @code{.desc} statement (@pxref{Desc}). +A descriptor value means nothing to @code{_AS__}. + +@node Symbol Other, , Symbol Desc, Symbol Attributes +@subsubsection Other +This is an arbitrary 8-bit value. It means nothing to @code{_AS__}. +_fi__(_AOUT__||_BOUT__) + +_if__(_COFF__) +@node COFF Symbols,,, +@subsection Symbol Attributes for COFF +The COFF format supports a multitude of auxiliary symbol attributes; +like the primary symbol attributes, they are set between @code{.def} and +@code{.endef} directives. + +@subsubsection Primary Attributes +The symbol name is set with @code{.def}; the value and type, +respectively, with @code{.val} and @code{.type}. + +@subsubsection Auxiliary Attributes +The @code{_AS__} directives @code{.dim}, @code{.line}, @code{.scl}, +@code{.size}, and @code{.tag} can generate auxiliary symbol table +information for COFF. +_fi__(_COFF__) + +@node Expressions, Pseudo Ops, Symbols, Top @chapter Expressions An @dfn{expression} specifies an address or numeric value. Whitespace may precede and/or follow an expression. +@node Empty Exprs, Integer Exprs, Expressions, Expressions @section Empty Expressions -An empty expression has no operands: it is just whitespace or null. +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{_AS__} will assume a value of (absolute) 0. This is compatible with other assemblers. +@node Integer Exprs, , Empty Exprs, Expressions @section Integer Expressions -An @dfn{integer expression} is one or more @i{primaries} delimited -by @i{operators}. - -@node Primary, Unops, , Expressions -@subsection Primaries -@dfn{Primaries} are symbols, numbers or subexpressions. Other -languages might call primaries ``arithmetic operands'' but we don't -want them confused with ``instruction operands'' of the machine -language so we give them a different name. - -Symbols are evaluated to yield @{@var{segment} @var{value}@} where -@var{segment} is one of @b{text}, @b{data}, @b{bss}, @b{absolute}, -or @b{undefined}. @var{value} is a signed 2's complement 32 bit +An @dfn{integer expression} is one or more @emph{arguments} delimited +by @emph{operators}. + +@node Arguments, Operators, Integer Exprs, Integer Exprs +@subsection Arguments + +@dfn{Arguments} are symbols, numbers or subexpressions. In other +contexts arguments are sometimes called ``arithmetic operands''. In +this manual, to avoid confusing them with the ``instruction operands'' of +the machine language, we use the term ``argument'' to refer to parts of +expressions only, reserving the word ``operand'' to refer only to machine +instruction operands. + +Symbols are evaluated to yield @{@var{segment} @var{NNN}@} where +@var{segment} is one of text, data, bss, absolute, +or undefined. @var{NNN} is a signed, 2's complement 32 bit integer. 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{_AS__} pretends these 32 bits are an integer. You may write integer-manipulating instructions that act on exotic constants, compatible with other assemblers. -Subexpressions are a left parenthesis (@t{(}) followed by an integer -expression followed by a right parenthesis (@t{)}), or a unary -operator followed by an primary. +Subexpressions are a left parenthesis @samp{(} followed by an integer +expression, followed by a right parenthesis @samp{)}; or a prefix +operator followed by an argument. +@node Operators, Prefix Ops, Arguments, Integer Exprs @subsection Operators -@dfn{Operators} are arithmetic marks, like @t{+} or @t{%}. Unary -operators are followed by an primary. Binary operators appear -between primaries. Operators may be preceded and/or followed by +@dfn{Operators} are arithmetic functions, like @code{+} or @code{%}. Prefix +operators are followed by an argument. Infix operators appear +between their arguments. Operators may be preceded and/or followed by whitespace. -@subsection Unary Operators -@node Unops, , Primary, Expressions -@code{as} has the following @dfn{unary operators}. They each take -one primary, which must be absolute. -@table @t +@node Prefix Ops, Infix Ops, Operators, Integer Exprs +@subsection Prefix Operators +@code{_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 +@c it align, on the printed page, with the similar table in the next +@c section (which is inside an enumerate). +@tex +\global\advance\leftskip by \itemindent +@end tex + +@table @code @item - -Hyphen. @dfn{Negation}. Two's complement negation. +@dfn{Negation}. Two's complement negation. @item ~ -Tilde. @dfn{Complementation}. Bitwise not. +@dfn{Complementation}. Bitwise not. @end table -@subsection Binary Operators -@dfn{Binary operators} are infix. Operators are prioritized, but -equal priority operators are performed left to right. Apart from -@samp{+} or @samp{-}, both primaries must be absolute, and the -result is absolute, else one primary can be either undefined or -pass1 and the result is pass1. +@tex +\global\advance\leftskip by -\itemindent +@end tex + +@node Infix Ops, , Prefix Ops, Integer Exprs +@subsection Infix Operators + +@dfn{Infix operators} take two arguments, one on either side. Operators +have precedence, but operations with equal precedence are performed left +to right. Apart from @code{+} or @code{-}, both arguments must be +absolute, and the result is absolute. + @enumerate + @item -Highest Priority +Highest Precedence @table @code @item * @dfn{Multiplication}. @item / @dfn{Division}. Truncation is the same as the C operator @samp{/} -of the compiler that compiled @code{as}. @item % @dfn{Remainder}. -@item < -@itemx << -@dfn{Shift Left}. Same as the C operator @samp{<<} of -the compiler that compiled @code{as}. -@item > -@itemx >> -@dfn{Shift Right}. Same as the C operator @samp{>>} of -the compiler that compiled @code{as}. +@item _0__<_1__ +@itemx _0__<<_1__ +@dfn{Shift Left}. Same as the C operator @samp{_0__<<_1__} +@item _0__>_1__ +@itemx _0__>>_1__ +@dfn{Shift Right}. Same as the C operator @samp{_0__>>_1__} @end table + @item -Intermediate priority -@table @t +Intermediate precedence +@table @code @item | @dfn{Bitwise Inclusive Or}. @item & @@ -1223,145 +1564,241 @@ Intermediate priority @item ! @dfn{Bitwise Or Not}. @end table + @item -Lowest Priority -@table @t +Lowest Precedence +@table @code @item + -@dfn{Addition}. If either primary is absolute, the result -has the segment of the other primary. -If either primary is pass1 or undefined, result is pass1. -Otherwise @t{+} is illegal. +@dfn{Addition}. If either argument is absolute, the result +has the segment of the other argument. +If either argument is pass1 or undefined, the result is pass1. +Otherwise @code{+} is illegal. @item - -@dfn{Subtraction}. If the right primary is absolute, the -result has the segment of the left primary. -If either primary is pass1 the result is pass1. -If either primary is undefined the result is difference segment. -If both primaries are in the same segment, the result is absolute; provided +@dfn{Subtraction}. If the right argument is absolute, the +result has the segment of the left argument. +If either argument is pass1 the result is pass1. +If either argument is undefined the result is difference segment. +If both arguments are in the same segment, the result is absolute---provided that segment is one of text, data or bss. -Otherwise @t{-} is illegal. +Otherwise subtraction is illegal. @end table @end enumerate -The sense of the rules is that you can't add or subtract quantities -from two different segments. If both primaries are in one of these -segments, they must be in the same segment: @b{text}, @b{data} or -@b{bss}, and the operator must be @samp{-}. +The sense of the rule for addition is that it's only meaningful to add +the @emph{offsets} in an address; you can only have a defined segment in +one of the two arguments. -@node PseudoOps, MachineDependent, Expressions, top +Similarly, you can't subtract quantities from two different segments. + +@node Pseudo Ops, _MACH_DEP__, Expressions, Top @chapter Assembler Directives -@menu -* Abort:: The Abort directive causes as to abort -* Align:: Pad the location counter to a power of 2 -* Ascii:: Fill memory with bytes of ASCII characters -* Asciz:: Fill memory with bytes of ASCII characters followed - by a null. -* Byte:: Fill memory with 8-bit integers -* Comm:: Reserve public space in the BSS segment -* Data:: Change to the data segment -* Desc:: Set the n_desc of a symbol -* Double:: Fill memory with double-precision floating-point numbers -* File:: Set the logical file name -* Fill:: Fill memory with repeated values -* Float:: Fill memory with single-precision floating-point numbers -* Global:: Make a symbol visible to the linker -* Int:: Fill memory with 32-bit integers -* Lcomm:: Reserve private space in the BSS segment -* Line:: Set the logical line number -* Long:: Fill memory with 32-bit integers -* Lsym:: Create a local symbol -* Octa:: Fill memory with 128-bit integers -* Org:: Change the location counter -* Quad:: Fill memory with 64-bit integers -* Set:: Set the value of a symbol -* Short:: Fill memory with 16-bit integers -* Space:: Fill memory with a repeated value -* Stab:: Store debugging information -* Text:: Change to the text segment -* Word:: Fill memory with 16-bit integers -@end menu - -All assembler directives begin with a symbol that begins with a -period (@samp{.}). The rest of the symbol is letters: their case -does not matter. - -@node Abort, Align, PseudoOps, PseudoOps -@section .abort + +All assembler directives have names that begin with a period (@samp{.}). +The rest of the name is letters: their case does not matter. + +This chapter discusses directives present regardless of the target +machine configuration for the GNU assembler; @pxref{_MACH_DEP__} for +additional directives. + +@node Abort,,, +@section @code{.abort} This directive stops the assembly immediately. It is for compatibility with other assemblers. The original idea was that the -assembler program would be piped into the assembler. If the source -of program wanted to quit, then this directive tells @code{as} to +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 quit also. One day @code{.abort} will not be supported. -@node Align, Ascii, Abort, PseudoOps -@section .align @var{absolute-expression} , @var{absolute-expression} -Pad the location counter (in the current subsegment) to a word, -longword or whatever boundary. The first expression is the number -of low-order zero bits the location counter will have after +_if__(_COFF__) +@node coff-ABORT,,, +@section @code{.ABORT} +When producing COFF output, @code{_AS__} accepts this directive as a +synonym for @samp{.abort}. +_fi__(_COFF__) +_if__(_BOUT__) +_if__(!_COFF__) +@node bout-ABORT,,, +@section @code{.ABORT} +_fi__(!_COFF__) + +When producing @code{b.out} output, @code{_AS__} accepts this directive, +but ignores it. +_fi__(_BOUT__) + +@node Align,,, +@section @code{.align @var{abs-expr} , @var{abs-expr}} +Pad the location counter (in the current subsegment) to a particular +storage boundary. The first expression (which must be absolute) is the +number of low-order zero bits the location counter will have after advancement. For example @samp{.align 3} will advance the location -counter until it a multiple of 8. If the location counter is -already a multiple of 8, no change is needed. - -The second expression gives the value to be stored in the padding -bytes. It (and the comma) may be omitted. If it is omitted, the -padding bytes are zeroed. - -@node Ascii, Asciz, Align, PseudoOps -@section .ascii @var{strings} -This expects zero or more string literals (@xref{Strings}.) +counter until it a multiple of 8. If the location counter is already a +multiple of 8, no change is needed. + +The second expression (also absolute) gives the value to be stored in +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}} +@code{.app-file} +_if__(!_AMD29K__) +(which may also be spelled @samp{.file}) +_fi__(!_AMD29K__) +tells @code{_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__} +programs.@refill + +@node Ascii,,, +@section @code{.ascii "@var{string}"}@dots{} +@code{.ascii} expects zero or more string literals (@pxref{Strings}) separated by commas. It assembles each string (with no automatic trailing zero byte) into consecutive addresses. -@node Asciz, Byte, Ascii, PseudoOps -@section .asciz @var{strings} -This is just like .ascii, but each string is followed by a zero byte. -The `z' in `.asciz' stands for `zero'. +@node Asciz, Byte, Ascii, Pseudo Ops +@section @code{.asciz "@var{string}"}@dots{} +@code{.asciz} is just like @code{.ascii}, but each string is followed by +a zero byte. The ``z'' in @samp{.asciz} stands for ``zero''. -@node Byte, Comm, Asciz, PseudoOps -@section .byte @var{expressions} +@node Byte, Comm, Asciz, Pseudo Ops +@section @code{.byte @var{expressions}} -This expects zero or more expressions, separated by commas. +@code{.byte} expects zero or more expressions, separated by commas. Each expression is assembled into the next byte. -@node Comm, Data, Byte, PseudoOps -@section .comm @var{symbol} , @var{length} -This declares a named common area in the bss segment. Normally -@code{ld} reserves memory addresses for it during linking, so no -partial program defines the location of the symbol. Tell @code{ld} -that it must be at least @var{length} bytes long. @code{ld} will -allocate space that is at least as long as the longest @code{.comm} -request in any of the partial programs linked. @var{length} is an -absolute expression. - -@node Data, Desc, Comm, PseudoOps -@section .data @var{subsegment} -This tells @code{as} to assemble the following statements onto the +@node Comm, Data, Byte, Pseudo Ops +@section @code{.comm @var{symbol} , @var{length} } +@code{.comm} declares a named common area in the bss segment. Normally +@code{_LD__} reserves memory addresses for it during linking, so no partial +program defines the location of the symbol. Use @code{.comm} to tell +@code{_LD__} that it must be at least @var{length} bytes long. @code{_LD__} +will allocate space for each @code{.comm} symbol that is at least as +long as the longest @code{.comm} request in any of the partial programs +linked. @var{length} is an absolute expression. + +@node Data, Desc, Comm, Pseudo Ops +@section @code{.data @var{subsegment}} +@code{.data} tells @code{_AS__} to assemble the following statements onto the end of the data subsegment numbered @var{subsegment} (which is an absolute expression). If @var{subsegment} is omitted, it defaults to zero. -@node Desc, Double, Data, PseudoOps -@section .desc @var{symbol}, @var{absolute-expression} -This sets @code{n_desc} of the symbol to the low 16 bits of -@var{absolute-expression}. - -@node Double, File, Desc, PseudoOps -@section .double @var{flonums} -This expects zero or more flonums, separated by commas. It assembles -floating point numbers. The exact kind of floating point numbers -emitted depends on what computer @code{as} is assembling for. See -the machine-specific part of the manual for the machine the -assembler is running on for more information. - -@node File, Fill, Double, PseudoOps -@section .file @var{string} -This tells @code{as} that we are about to start a new logical -file. @var{String} is the new file name. An empty file name -is OK, but you must still give the quotes: @code{""}. This -statement may go away in future: it is only recognized to -be compatible with old @code{as} programs. - -@node Fill, Float, File, PseudoOps -@section .fill @var{repeat} , @var{size} , @var{value} +_if__(_COFF__) +@node Def,,, +@section @code{.def @var{name}} +Begin defining debugging information for a symbol @var{name}; the +definition extends until the @code{.endef} directive is encountered. +_if__(_BOUT__) + +This directive is only observed when @code{_AS__} is configured for COFF +format output; when producing @code{b.out}, @samp{.def} is recognized, +but ignored. +_fi__(_BOUT__) +_fi__(_COFF__) + +_if__(_AOUT__||_BOUT__) +@node Desc, Double, Data, Pseudo Ops +@section @code{.desc @var{symbol}, @var{abs-expression}} +This directive sets the descriptor of the symbol (@pxref{Symbol Attributes}) +to the low 16 bits of an absolute expression. + +_if__(_COFF__) +The @samp{.desc} directive is not available when @code{_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 +it, but produce no output, when configured for COFF. +_fi__(_COFF__) +_fi__(_AOUT__||_BOUT__) + +_if__(_COFF__) +@node Dim,,, +@section @code{.dim} +This directive is generated by compilers to include auxiliary debugging +information in the symbol table. It is only permitted inside +@code{.def}/@code{.endef} pairs. +_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 +ignores it. +_fi__(_BOUT__) +_fi__(_COFF__) + +@node Double, Else, Desc, Pseudo Ops +@section @code{.double @var{flonums}} +@code{.double} expects zero or more flonums, separated by commas. It +assembles floating point numbers. +_if__(_ALL_ARCH__) +The exact kind of floating point numbers emitted depends on how +@code{_AS__} is configured. @xref{_MACH_DEP__}. +_fi__(_ALL_ARCH__) +_if__(_AMD29K__ || _I960__) +On the _HOST__ family @samp{.double} emits 64-bit floating-point numbers +in IEEE format. +_fi__(_AMD29K__ || _I960__) + +@node Else,,, +@section @code{.else} +@code{.else} is part of the @code{_AS__} support for conditional assembly; +@pxref{If}. It marks the beginning of a section of code to be assembled +if the condition for the preceding @code{.if} was false. + +_if__(0) +@node End,,, +@section @code{.end} +This doesn't do anything---but isn't an s_ignore, so I suspect it's +meant to do something eventually (which is why it isn't documented here +as "for compatibility with blah"). +_fi__(0) + +_if__(_COFF__) +@node Endef,,, +@section @code{.endef} +This directive flags the end of a symbol definition begun with +@code{.def}. +_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 +directive but ignores it. +_fi__(_BOUT__) +_fi__(_COFF__) + +@node Endif, Equ, End, Pseudo Ops +@section @code{.endif} +@code{.endif} is part of the @code{_AS__} support for conditional assembly; +it marks the end of a block of code that is only assembled +conditionally. @xref{If}. + +@node Equ, Extern, Endif, Pseudo Ops +@section @code{.equ @var{symbol}, @var{expression}} + +This directive sets the value of @var{symbol} to @var{expression}. +It is synonymous with @samp{.set}; @pxref{Set}. + +@node Extern,,, +@section @code{.extern} +@code{.extern} is accepted in the source program---for compatibility +with other assemblers---but it is ignored. @code{_AS__} treats +all undefined symbols as external. + +_if__(!_AMD29K__) +@node File,,, +@section @code{.app-file @var{string}} +@code{.file} (which may also be spelled @samp{.app-file}) tells +@code{_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. +_fi__(!_AMD29K__) + + +@node Fill,,, +@section @code{.fill @var{repeat} , @var{size} , @var{value}} @var{result}, @var{size} and @var{value} are absolute expressions. This emits @var{repeat} copies of @var{size} bytes. @var{Repeat} may be zero or more. @var{Size} may be zero or more, but if it is @@ -1369,221 +1806,535 @@ more than 8, then it is deemed to have the value 8, compatible with 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{_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. -@var{Size} and @var{value} are optional. +@var{size} and @var{value} are optional. If the second comma and @var{value} are absent, @var{value} is assumed zero. If the first comma and following tokens are absent, @var{size} is assumed to be 1. -@node Float, Global, Fill, PseudoOps -@section .float @var{flonums} -This directive assembles zero or more flonums, separated by commas. -The exact kind of floating point numbers emitted depends on what -computer @code{as} is assembling for. See the machine-specific part -of the manual for the machine the assembler is running on for more -information. - -@node Global, Int, Float, PseudoOps -@section .global @var{symbol} -This makes the symbol visible to @code{ld}. If you define +@node Float, Global, Fill, Pseudo Ops +@section @code{.float @var{flonums}} +This directive assembles zero or more flonums, separated by commas. It +has the same effect as @code{.single}. +_if__(_ALL_ARCH__) +The exact kind of floating point numbers emitted depends on how +@code{_AS__} is configured. +@xref{_MACH_DEP__}. +_fi__(_ALL_ARCH__) +_if__(_AMD29K__ || _I960__) +On the _HOST__ family, @code{.float} emits 32-bit floating point numbers +in IEEE format. +_fi__(_AMD29K__ || _I960__) + +@node Global, Ident, Float, Pseudo Ops +@section @code{.global @var{symbol}}, @code{.globl @var{symbol}} +@code{.global} makes the symbol visible to @code{_LD__}. If you define @var{symbol} in your partial program, its value is made available to other partial programs that are linked with it. Otherwise, @var{symbol} will take its attributes from a symbol of the same name from another partial program it is linked with. -This is done by setting the @code{N_EXT} bit -of that symbol's @code{n_type} to 1. +_if__(!_I960__) +@c FIXME BFD implications; this is different in COFF. +This is done by setting the @code{N_EXT} bit of that symbol's type byte +to 1. @xref{Symbol Attributes}. +_fi__(!_I960__) + +Both spellings (@samp{.globl} and @samp{.global}) are accepted, for +compatibility with other assemblers. + +@node hword, line, file, Machine Directives +@section @code{.hword @var{expressions}} +This expects zero or more @var{expressions}, and emits +a 16 bit number for each. + +_if__(_ALL_ARCH__) +This directive is a synonym for @samp{.short}; depending on the target +architecture, it may also be a synonym for @samp{.word}. +_fi__(_ALL_ARCH__) +_if__( (_AMD29K__ || _I960__) && !_ALL_ARCH__ ) +This directive is a synonym for @samp{.short}. +_fi__( (_AMD29K__ || _I960__) && !_ALL_ARCH__ ) + +_if__(_AOUT__||_BOUT__||_COFF__) +@node Ident, If, Global, Pseudo Ops +@section @code{.ident} +This directive is used by some assemblers to place tags in object files. +@code{_AS__} simply accepts the directive for source-file +compatibility with such assemblers, but does not actually emit anything +for it. +_fi__(_AOUT__||_BOUT__||_COFF__) + +@node If, Include, Ident, Pseudo Ops +@section @code{.if @var{absolute expression}} +@code{.if} marks the beginning of a section of code which is only +considered part of the source program being assembled if the argument +(which must be an @var{absolute expression}) is non-zero. The end of +the conditional section of code must be marked by @code{.endif} +(@pxref{Endif}); optionally, you may include code for the +alternative condition, flagged by @code{.else} (@pxref{Else}. + +The following variants of @code{.if} are also supported: +@table @code +@item ifdef @var{symbol} +Assembles the following section of code if the specified @var{symbol} +has been defined. + +_if__(0) +@item ifeqs +Not yet implemented. +_fi__(0) + +@item ifndef @var{symbol} +@itemx ifnotdef @var{symbol} +Assembles the following section of code if the specified @var{symbol} +has not been defined. Both spelling variants are equivalent. + +_if__(0) +@item ifnes +Not yet implemented. +_fi__(0) +@end table -@node Int, Lcomm, Global, PseudoOps -@section .int @var{expressions} +@node Include, Int, If, Pseudo Ops +@section @code{.include "@var{file}"} +This directive provides a way to include supporting files at specified +points in your source program. The code from @var{file} is assembled as +if it followed the point of the @code{.include}; when the end of the +included file is reached, assembly of the original file continues. You +can control the search paths used with the @samp{-I} command-line option +(@pxref{Options}). Quotation marks are required around @var{file}. + +@node Int, Lcomm, Include, Pseudo Ops +@section @code{.int @var{expressions}} Expect zero or more @var{expressions}, of any segment, separated by commas. For each expression, emit a 32-bit number that will, at run time, be the value of that expression. The byte order of the expression depends on what kind of computer will run the program. -@node Lcomm, Line, Int, PseudoOps -@section .lcomm @var{symbol} , @var{length} +@node Lcomm, Line, Int, Pseudo Ops +@section @code{.lcomm @var{symbol} , @var{length}} Reserve @var{length} (an absolute expression) bytes for a local -common and denoted by @var{symbol}, whose segment and value are +common denoted by @var{symbol}. The segment and value of @var{symbol} are those of the new local common. The addresses are allocated in the -@code{bss} segment, so at run-time the bytes will start off zeroed. -@var{Symbol} is not declared global (@xref{Global}.), so is normally -not visible to @code{ld}. - -@node Line, Long, Lcomm, PseudoOps -@section .line @var{logical line number} -This tells @code{as} to change the logical line number. -@var{logical line number} is an absolute expression. The next line -will have that logical line number. So any other statements on the -current line (after a @code{;}) will be reported as on logical line -number @var{logical line number} - 1. One day this directive will -be unsupported: it is used only for compatibility with existing -assembler programs. - -@node Long, Lsym, Line, PseudoOps -@section .long @var{expressions} -This is the same as @samp{.int}, @pxref{Int}. - -@node Lsym, Octa, Long, PseudoOps -@section .lsym @var{symbol}, @var{expression} -This creates a new symbol named @var{symbol}, but do not put it in +bss segment, so at run-time the bytes will start off zeroed. +@var{Symbol} is not declared global (@pxref{Global}), so is normally +not visible to @code{_LD__}. + +_if__(_AOUT__||_BOUT__||_COFF__) +_if__(!_AMD29K__) +@node Line,,, +@section @code{.line @var{line-number}} +_fi__(!_AMD29K__) +_if__(_AMD29K__) +@node Ln,,, +@section @code{.ln @var{line-number}} +_fi__(_AMD29K__) +_fi__(_AOUT__||_BOUT__||_COFF__) +_if__(_AOUT__||_BOUT__) +Tell @code{_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 +_if__(_AMD29K__) +@samp{@@}) +_fi__(_AMD29K__) +_if__(!_AMD29K__) +@code{;}) +_fi__(!_AMD29K__) +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 +_fi__(_AOUT__||_BOUT__) +_if__(_COFF__) + +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 +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. + +Inside a @code{.def}, @samp{.line} is, instead, one of the directives +used by compilers to generate auxiliary symbol information for +debugging. +_fi__(_COFF__) + +_if__(_AOUT__&&!_AMD29K__) +@node Ln,,, +@section @code{.ln @var{line-number}} +@samp{.ln} is a synonym for @samp{.line}. +_fi__(_AOUT__&&!_AMD29K__) + +_if__(_COFF__&&!_AOUT__) +@node Ln,,, +@section @code{.ln @var{line-number}} +Tell @code{_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 +@code{b.out}; its effect is only associated with COFF output format. +_fi__(_BOUT__) +_fi__(_COFF__&&!_AOUT__) + +@node List,,, +@section @code{.list} and related directives +@code{_AS__} ignores the directives @code{.list}, @code{.nolist}, +@code{.eject}, @code{.lflags}, @code{.title}, @code{.sbttl}; however, +they're accepted for compatibility with assemblers that use them. + +@node Long, Lsym, List, Pseudo Ops +@section @code{.long @var{expressions}} +@code{.long} is the same as @samp{.int}, @pxref{Int}. + +@node Lsym, Octa, Long, Pseudo Ops +@section @code{.lsym @var{symbol}, @var{expression}} +@code{.lsym} creates a new symbol named @var{symbol}, but does not put it in the hash table, ensuring it cannot be referenced by name during the rest of the assembly. This sets the attributes of the symbol to be -the same as the expression value. @code{n_other} = @code{n_desc} = -0. @code{n_type} = (whatever segment the expression has); the -@code{N_EXT} bit of @code{n_type} is zero. @code{n_value} = -(expression's value). - -@node Octa, Org, Lsym, PseudoOps -@section .octa @var{bignums} -This expects zero or more bignums, separated by commas. For each -bignum, it emits an 16-byte (@b{octa}-word) integer. - -@node Org, Quad, Octa, PseudoOps -@section .org @var{new-lc} , @var{fill} -This will advance the location counter of the current segment to +the same as the expression value: +@smallexample +@var{other} = @var{descriptor} = 0 +@var{type} = @r{(segment of @var{expression})} +@var{value} = @var{expression} +@end smallexample +@noindent +The new symbol is not flagged as external. + +@c FIXME: double size emitted for "octa" on i960, others? Or warn? +@node Octa, Org, Lsym, Pseudo Ops +@section @code{.octa @var{bignums}} +This directive expects zero or more bignums, separated by commas. For each +bignum, it emits a 16-byte integer. + +The term ``octa'' comes from contexts in which a ``word'' is two bytes; +hence @emph{octa}-word for 16 bytes. + +@node Org, Quad, Octa, Pseudo Ops +@section @code{.org @var{new-lc} , @var{fill}} + +@code{.org} will advance the location counter of the current segment to @var{new-lc}. @var{new-lc} is either an absolute expression or an -expression with the same segment as the current subsegment. That -is, you can't use @code{.org} to cross segments. Because @code{as} -tries to assemble programs in one pass @var{new-lc} must be defined. -If you really detest this restriction we eagerly await a chance to -share your improved assembler. To be compatible with former -assemblers, if the segment of @var{new-lc} is absolute then we -pretend the segment of @var{new-lc} is the same as the current -subsegment. +expression with the same segment as the current subsegment. That is, +you can't use @code{.org} to cross segments: if @var{new-lc} has the +wrong segment, the @code{.org} directive is ignored. To be compatible +with former assemblers, if the segment of @var{new-lc} is absolute, +@code{_AS__} will issue a warning, then pretend the segment of @var{new-lc} +is the same as the current subsegment. + +@code{.org} may only increase the location counter, or leave it +unchanged; you cannot use @code{.org} to move the location counter +backwards. + +@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 segment. pesch@cygnus.com 18feb91 +Because @code{_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. Beware that the origin is relative to the start of the segment, not to the start of the subsegment. This is compatible with other people's assemblers. -If the location counter (of the current subsegment) is advanced, the +When the location counter (of the current subsegment) is advanced, the intervening bytes are filled with @var{fill} which should be an absolute expression. If the comma and @var{fill} are omitted, @var{fill} defaults to zero. -@node Quad, Set, Org, PseudoOps -@section .quad @var{bignums} -This expects zero or more bignums, separated by commas. For each -bignum, it emits an 8-byte (@b{quad}-word) integer. If the bignum -won't fit in a quad-word, it prints a warning message; and just -takes the lowest order 8 bytes of the bignum. - -@node Set, Short, Quad, PseudoOps -@section .set @var{symbol}, @var{expression} - -This sets the value of @var{symbol} to expression. This will change -@code{n_value} and @code{n_type} to conform to the @var{expression}. -if @code{n_ext} is set, it remains set. - -It is OK to @code{.set} a symbol many times in the same assembly. +@node Quad, Set, Org, Pseudo Ops +@section @code{.quad @var{bignums}} +@code{.quad} expects zero or more bignums, separated by commas. For +each bignum, it emits +_if__(!_I960__) +an 8-byte integer. If the bignum won't fit in 8 +bytes, it prints a warning message; and just takes the lowest order 8 +bytes of the bignum.@refill + +The term ``quad'' comes from contexts in which a ``word'' is two bytes; +hence @emph{quad}-word for 8 bytes. +_fi__(!_I960__) +_if__(_I960__) +a 16-byte integer. If the bignum won't fit in 16 bytes, it prints a +warning message; and just takes the lowest order 16 bytes of the +bignum.@refill +_fi__(_I960__) + +_if__(_COFF__) +@node Scl,,, +@section @code{.scl @var{class}} +Set the storage-class value for a symbol. This directive may only be +used inside a @code{.def}/@code{.endef} pair. Storage class may flag +whether a symbol is static or external, or it may record further +symbolic debugging information. +_if__(_BOUT__) + +The @samp{.scl} directive is primarily associated with COFF output; when +configured to generate @code{b.out} output format, @code{_AS__} will +accept this directive but ignore it. +_fi__(_BOUT__) +_fi__(_COFF__) + + +@node Set,,, +@section @code{.set @var{symbol}, @var{expression}} + +This directive sets the value of @var{symbol} to @var{expression}. This +will change @var{symbol}'s value and type to conform to +@var{expression}. If @var{symbol} was flagged as external, it remains +flagged. (@xref{Symbol Attributes}.) + +You may @code{.set} a symbol many times in the same assembly. If the expression's segment 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{_AS__} will abort with an error message if one is required. If you @code{.set} a global symbol, the value stored in the object file is the last value stored into it. -@node Short, Space, Set, PseudoOps -@section .short @var{expressions} -Except on the Sparc this is the same as @samp{.word}. @xref{Word}. -On the sparc, this expects zero or more @var{expressions}, and emits +@node Short, Single, Set, Pseudo Ops +@section @code{.short @var{expressions}} +_if__(! (_SPARC__ || _AMD29K__ || _I960__) ) +@code{.short} is the same as @samp{.word}. @xref{Word}. +_fi__(! (_SPARC__ || _AMD29K__ || _I960__) ) +_if__(_SPARC__ || _AMD29K__ || _I960__) +This expects zero or more @var{expressions}, and emits a 16 bit number for each. - -@node Space, Stab, Short, PseudoOps -@section .space @var{size} , @var{fill} -This emits @var{size} bytes, each of value @var{fill}. Both +_fi__(_SPARC__ || _AMD29K__ || _I960__) + +@node Single,,, +@section @code{.single @var{flonums}} +This directive assembles zero or more flonums, separated by commas. It +has the same effect as @code{.float}. +_if__(_ALL_ARCH__) +The exact kind of floating point numbers emitted depends on how +@code{_AS__} is configured. @xref{_MACH_DEP__}. +_fi__(_ALL_ARCH__) +_if__(_AMD29K__ || _I960__) +On the _HOST__ family, @code{.single} emits 32-bit floating point +numbers in IEEE format. +_fi__(_AMD29K__ || _I960__) + +_if__(_COFF__) +@node Size,,, +@section @code{.size} +This directive is generated by compilers to include auxiliary debugging +information in the symbol table. It is only permitted inside +@code{.def}/@code{.endef} pairs. +_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 +ignores it. +_fi__(_BOUT__) +_fi__(_COFF__) + +@node Space,,, +_if__(!_AMD29K__) +@section @code{.space @var{size} , @var{fill}} +This directive emits @var{size} bytes, each of value @var{fill}. Both @var{size} and @var{fill} are absolute expressions. If the comma and @var{fill} are omitted, @var{fill} is assumed to be zero. - -@node Stab, Text, Space, PseudoOps -@section .stabd, .stabn, .stabs -There are three directives that begin @code{.stab@dots{}}. -All emit symbols, for use by symbolic debuggers. -The symbols are not entered in @code{as}' hash table: they +_fi__(!_AMD29K__) + +_if__(_AMD29K__) +@section @code{.space} +This directive is ignored; it is accepted for compatibility with other +AMD 29K assemblers. + +@quotation +@emph{Warning:} In other versions of the GNU assembler, the directive +@code{.space} has the effect of @code{.block} @xref{Machine Directives}. +@end quotation +_fi__(_AMD29K__) + +_if__(_AOUT__||_BOUT__||_COFF__) +@node Stab, Text, Space, Pseudo Ops +@section @code{.stabd, .stabn, .stabs} +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 cannot be referenced elsewhere in the source file. Up to five fields are required: @table @var @item string This is the symbol's name. It may contain any character except @samp{\000}, so is more general than ordinary symbol names. Some debuggers used to -code arbitrarily complex structures into symbol names using this technique. +code arbitrarily complex structures into symbol names using this field. @item type -An absolute expression. The symbol's @code{n_type} is set to the low 8 +An absolute expression. The symbol's type is set to the low 8 bits of this expression. -Any bit pattern is permitted, but @code{ld} and debuggers will choke on +Any bit pattern is permitted, but @code{_LD__} and debuggers will choke on silly bit patterns. @item other An absolute expression. -The symbol's @code{n_other} is set to the low 8 bits of this expression. +The symbol's ``other'' attribute is set to the low 8 bits of this expression. @item desc An absolute expression. -The symbol's @code{n_desc} is set to the low 16 bits of this expression. +The symbol's descriptor is set to the low 16 bits of this expression. @item value -An absolute expression which becomes the symbol's @code{n_value}. +An absolute expression which becomes the symbol's value. @end table -If a warning is detected while reading the @code{.stab@dots{}} -statement the symbol has probably already been created and you will -get a half-formed symbol in your object file. This is compatible -with earlier assemblers (!) +If a warning is detected while reading a @code{.stabd}, @code{.stabn}, +or @code{.stabs} statement, the symbol has probably already been created +and you will get a half-formed symbol in your object file. This is +compatible with earlier assemblers! -.stabd @var{type} , @var{other} , @var{desc} +@table @code +@item .stabd @var{type} , @var{other} , @var{desc} The ``name'' of the symbol generated is not even an empty string. It is a null pointer, for compatibility. Older assemblers used a null pointer so they didn't waste space in object files with empty strings. -The symbol's @code{n_value} is set to the location counter, +The symbol's value is set to the location counter, relocatably. When your program is linked, the value of this symbol will be where the location counter was when the @code{.stabd} was assembled. -.stabn @var{type} , @var{other} , @var{desc} , @var{value} +@item .stabn @var{type} , @var{other} , @var{desc} , @var{value} The name of the symbol is set to the empty string @code{""}. -.stabs @var{string} , @var{type} , @var{other} , @var{desc} , @var{value} +@item .stabs @var{string} , @var{type} , @var{other} , @var{desc} , @var{value} -@node Text, Word, Stab, PseudoOps -@section .text @var{subsegment} -Tells @code{as} to assemble the following statements onto the end of +All five fields are specified. +@end table +_fi__(_AOUT__||_BOUT__||_COFF__) + +_if__(_COFF__) +@node Tag,,, +@section @code{.tag @var{structname}} +This directive is generated by compilers to include auxiliary debugging +information in the symbol table. It is only permitted inside +@code{.def}/@code{.endef} pairs. Tags are used to link structure +definitions in the symbol table with instances of those structures. +_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 +ignores it. +_fi__(_BOUT__) +_fi__(_COFF__) + +@node Text,,, +@section @code{.text @var{subsegment}} +Tells @code{_AS__} to assemble the following statements onto the end of the text subsegment numbered @var{subsegment}, which is an absolute expression. If @var{subsegment} is omitted, subsegment number zero is used. -@node Word, , Text, PseudoOps -@section .word @var{expressions} -On the Sparc, this produces 32-bit numbers instead of 16-bit ones. -This expect zero or more @var{expressions}, of any segment, -separated by commas. For each expression, emit a 16-bit number that -will, at run time, be the value of that expression. The byte order -of the expression depends on what kind of computer will run the -program. +_if__(_COFF__) +@node Type,,, +@section @code{.type @var{int}} +This directive, permitted only within @code{.def}/@code{.endef} pairs, +records the integer @var{int} as the type attribute of a symbol table entry. +_if__(_BOUT__) + +@samp{.type} is associated only with COFF format output; when +@code{_AS__} is configured for @code{b.out} output, it accepts this +directive but ignores it. +_fi__(_BOUT__) +_fi__(_COFF__) + +_if__(_COFF__) +@node Val,,, +@section @code{.val @var{addr}} +This directive, permitted only within @code{.def}/@code{.endef} pairs, +records the address @var{addr} as the value attribute of a symbol table +entry. +_if__(_BOUT__) + +@samp{.val} is used only for COFF output; when @code{_AS__} is +configured for @code{b.out}, it accepts this directive but ignores it. +_fi__(_BOUT__) +_fi__(_COFF__) + +@node Word,,, +@section @code{.word @var{expressions}} +This directive expects zero or more @var{expressions}, of any segment, +separated by commas. +_if__(_SPARC__ || _AMD29K__ || _I960__) +For each expression, @code{_AS__} emits a 32-bit number. +_fi__(_SPARC__ || _AMD29K__ || _I960__) +_if__(! (_SPARC__ || _AMD29K__ || _I960__) ) +For each expression, @code{_AS__} emits a 16-bit number. +_fi__(! (_SPARC__ || _AMD29K__ || _I960__) ) + +_if__(_ALL_ARCH__) +The byte order of the expression depends on what kind of computer will +run the program. +_fi__(_ALL_ARCH__) + +@c on these boxes the "special treatment to support compilers" doesn't +@c happen---32-bit addressability, period; no long/short jumps. +_if__(! (_AMD29K__ || _I960__) ) +@subsection Special Treatment to support Compilers +In order to assemble compiler output into something that will work, +@code{_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 +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 +create a @dfn{secondary jump table}, immediately before the next label. +This @var{secondary jump table} will be preceded by a short-jump to the +first byte after the secondary table. This short-jump prevents the flow +of control from accidentally falling into the new table. Inside the +table will be a long-jump to @code{sym2}. The original @samp{.word} +will contain @code{sym1} minus the address of the long-jump to +@code{sym2}. + +If there were several occurrences of @samp{.word sym1-sym2} before the +secondary jump table, all of them will be adjusted. If there was a +@samp{.word sym3-sym4}, that also did not fit in sixteen bits, a +long-jump to @code{sym4} will be included in the secondary jump table, +and the @code{.word} directives will be adjusted to contain @code{sym3} +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 +@samp{-DWORKING_DOT_WORD} option.} This feature is likely to confuse +assembly language programmers. +_fi__(_INTERNALS__) +_fi__(! (_AMD29K__ || _I960__) ) + +@node Deprecated, _MACH_DEP__, Word, Pseudo Ops @section Deprecated Directives One day these directives won't work. They are included for compatibility with older assemblers. @table @t @item .abort -@item .file +@item .app-file @item .line @end table -@node MachineDependent, Maintenance, PseudoOps, top +@node _MACH_DEP__,,, +_if__(_ALL_ARCH__) @chapter Machine Dependent Features -@section Vax -@subsection Options +_fi__(_ALL_ARCH__) +_if__(_VAX__) +@group +_CHAPSEC__(0+_ALL_ARCH__) VAX Dependent Features +_CHAPSEC__(1+_ALL_ARCH__) Options -The Vax version of @code{as} accepts any of the following options, +The Vax version of @code{_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. +@end group @table @asis @item @kbd{-D} (Debug) @@ -1600,7 +2351,7 @@ argument that follows @kbd{-d} (GNU standard). @item @kbd{-V} (Virtualize Interpass Temporary File) 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{_AS__} always does this, so this option is redundant. @item @kbd{-J} (JUMPify Longer Branches) @@ -1615,23 +2366,23 @@ this option to emit short and long branches. @item @kbd{-t} (Temporary File Directory) 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{_AS__} does not use a temporary disk file, so this option makes no difference. @kbd{-t} needs exactly one filename. @end table 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{_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{_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} -symbol so that the object file will be compatable with Vax-11 +symbol so that the object file will be compatible with Vax-11 "C". -@subsection Floating Point +_CHAPSEC__(1+_ALL_ARCH__) Floating Point Conversion of flonums to floating point is correct, and compatible with previous assemblers. Rounding is towards zero if the remainder is exactly half the least significant bit. @@ -1639,14 +2390,14 @@ towards zero if the remainder is exactly half the least significant bit. @code{D}, @code{F}, @code{G} and @code{H} floating point formats are understood. -Immediate floating literals (@i{e.g.} @samp{S`$6.9}) +Immediate floating literals (@emph{e.g.} @samp{S`$6.9}) are rendered correctly. Again, rounding is towards zero in the boundary case. The @code{.float} directive produces @code{f} format numbers. The @code{.double} directive produces @code{d} format numbers. -@subsection Machine Directives +_CHAPSEC__(1+_ALL_ARCH__) Machine Directives The Vax version of the assembler supports four directives for generating Vax floating point constants. They are described in the table below. @@ -1670,14 +2421,14 @@ assembles Vax @code{h} format 128-bit floating point constants. @end table -@subsection Opcodes +_CHAPSEC__(1+_ALL_ARCH__) Opcodes All DEC mnemonics are supported. Beware that @code{case@dots{}} instructions have exactly 3 operands. The dispatch table that follows the @code{case@dots{}} instruction should be made with @code{.word} statements. This is compatible with all unix assemblers we know of. -@subsection Branch Improvement +_CHAPSEC__(1+_ALL_ARCH__) Branch Improvement Certain pseudo opcodes are permitted. They are for branch instructions. They expand to the shortest branch instruction that will reach the target. Generally these mnemonics are made by @@ -1756,7 +2507,7 @@ Unconditional branch. @end table @end table -@subsection operands +_CHAPSEC__(1+_ALL_ARCH__) operands The immediate character is @samp{$} for Unix compatibility, not @samp{#} as DEC writes it. @@ -1772,9 +2523,9 @@ Register names understood are @code{r0 r1 r2 @dots{} r15 ap fp sp pc}. Any case of letters will do. For instance -@example +@smallexample tstb *w`$4(r5) -@end example +@end smallexample Any expression is permitted in an operand. Operands are comma separated. @@ -1783,52 +2534,409 @@ separated. @c in operands, but I forget what it is. It is @c a syntax clash because () is used as an address mode @c and to encapsulate sub-expressions. -@subsection Not Supported -Vax bit fields can not be assembled with @code{as}. Someone +_CHAPSEC__(1+_ALL_ARCH__) Not Supported +Vax bit fields can not be assembled with @code{_AS__}. Someone can add the required code if they really need it. +_fi__(_VAX__) +_if__(_AMD29K__) +@group +_CHAPSEC__(0+_ALL_ARCH__) AMD 29K Dependent Features +@node AMD29K Options, AMD29K Syntax, _MACH_DEP__, _MACH_DEP__ +_CHAPSEC__(1+_ALL_ARCH__) Options +@code{_AS__} has no additional command-line options for the AMD +29K family. +@end group + +@node AMD29K Syntax, AMD29K Floating Point, AMD29K Options, _MACH_DEP__ +@group +_CHAPSEC__(1+_ALL_ARCH__) Syntax +_CHAPSEC__(2+_ALL_ARCH__) Special Characters +@samp{;} is the line comment character. + +@samp{@@} can be used instead of a newline to separate statements. + +The character @samp{?} is permitted in identifiers (but may not begin +an identifier). +@end group + +_CHAPSEC__(2+_ALL_ARCH__) Register Names +General-purpose registers are represented by predefined symbols of the +form @samp{GR@var{nnn}} (for global registers) or @samp{LR@var{nnn}} +(for local registers), where @var{nnn} represents a number between +@code{0} and @code{127}, written with no leading zeros. The leading +letters may be in either upper or lower case; for example, @samp{gr13} +and @samp{LR7} are both valid register names. + +You may also refer to general-purpose registers by specifying the +register number as the result of an expression (prefixed with @samp{%%} +to flag the expression as a register number): +@smallexample +%%@var{expression} +@end smallexample +@noindent---where @var{expression} must be an absolute expression +evaluating to a number between @code{0} and @code{255}. The range +[0, 127] refers to global registers, and the range [128, 255] to local +registers. + +In addition, @code{_AS__} understands the following protected +special-purpose register names for the AMD 29K family: + +@smallexample + vab chd pc0 + ops chc pc1 + cps rbp pc2 + cfg tmc mmu + cha tmr lru +@end smallexample + +These unprotected special-purpose register names are also recognized: +@smallexample + ipc alu fpe + ipa bp inte + ipb fc fps + q cr exop +@end smallexample + +@node AMD29K Floating Point, AMD29K Directives, AMD29K Syntax, _MACH_DEP__ +_CHAPSEC__(1+_ALL_ARCH__) Floating Point +The AMD 29K family uses IEEE floating-point numbers. + +@group +@node AMD29K Directives, AMD29K Opcodes, AMD29K Floating Point, _MACH_DEP__ +_CHAPSEC__(1+_ALL_ARCH__) Machine Directives + +@node block, cputype, AMD29K Directives, AMD29K Directives +_CHAPSEC__(2+_ALL_ARCH__) @code{.block @var{size} , @var{fill}} +This directive emits @var{size} bytes, each of value @var{fill}. Both +@var{size} and @var{fill} are absolute expressions. If the comma +and @var{fill} are omitted, @var{fill} is assumed to be zero. -@section 680x0 -@subsection Options -The 680x0 version of @code{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 -assembling for. +In other versions of the GNU assembler, this directive is called +@samp{.space}. +@end group + +@node cputype, file, block, Machine Directives +_CHAPSEC__(2+_ALL_ARCH__) @code{.cputype} +This directive is ignored; it is accepted for compatibility with other +AMD 29K assemblers. + +@node file, hword, cputype, Machine Directives +_CHAPSEC__(2+_ALL_ARCH__) @code{.file} +This directive is ignored; it is accepted for compatibility with other +AMD 29K assemblers. + +@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. +@end quotation + +@node line, reg, hword, Machine Directives +_CHAPSEC__(2+_ALL_ARCH__) @code{.line} +This directive is ignored; it is accepted for compatibility with other +AMD 29K assemblers. + +@node reg, sect, line, Machine Directives +_CHAPSEC__(2+_ALL_ARCH__) @code{.reg @var{symbol}, @var{expression}} +@code{.reg} has the same effect as @code{.lsym}; @pxref{Lsym}. + +@node sect, use, reg, Machine Directives +_CHAPSEC__(2+_ALL_ARCH__) @code{.sect} +This directive is ignored; it is accepted for compatibility with other +AMD 29K assemblers. + +@node use, , sect, Machine Directives +_CHAPSEC__(2+_ALL_ARCH__) @code{.use @var{segment name}} +Establishes the segment and subsegment for the following code; +@var{segment name} may be one of @code{.text}, @code{.data}, +@code{.data1}, or @code{.lit}. With one of the first three @var{segment +name} options, @samp{.use} is equivalent to the machine directive +@var{segment name}; the remaining case, @samp{.use .lit}, is the same as +@samp{.data 200}. + + +@node AMD29K Opcodes, , AMD29K Directives, _MACH_DEP__ +@section Opcodes +@code{_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 +User's Manual}, Advanced Micro Devices, Inc. + +_fi__(_AMD29K__) +_if__(_I960__) +_CHAPSEC__(0+_ALL_ARCH__) Intel 80960 Dependent Features +@node Options-i960,,, +_CHAPSEC__(1+_ALL_ARCH__) Command-line Options +@table @code -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 being, -@code{as} can only allocate space for the linker to fill in later. -Since @code{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 possible, and you know -that the relevant symbols will be less than 17 bits away. - -The 680x0 version of @code{as} is usually 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 @samp{-m68000}, @samp{-mc68000}, @samp{-m68010}, -@samp{-mc68010}, @samp{-m68020}, and @samp{-mc68020} to tell it what -processor it should be assembling for. Unfortunately, these options -are almost entirely unused and untried. They make work, but nobody -has tested them much. +@item -ACA | -ACA_A | -ACB | -ACC | -AKA | -AKB | -AKC | -AMC +Select the 80960 architecture. Instructions or features not supported +by the selected architecture cause fatal errors. + +@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 +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 +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 +architecture explicitly. + + +@item -b +Add code to collect information about conditional branches taken, for +later optimization using branch prediction bits. (The conditional branch +instructions have branch prediction bits in the CA, CB, and CC +architectures.) If @var{BR} represents a conditional branch instruction, +the following represents the code generated by the assembler when +@samp{-b} is specified: + +@smallexample + call @var{increment routine} + .word 0 # pre-counter +Label: @var{BR} + call @var{increment routine} + .word 0 # post-counter +@end smallexample + +The counter following a branch records the number of times that branch +was @emph{not} taken; the differenc between the two counters is the +number of times the branch @emph{was} taken. + +A table of all such @code{Label}s is also generated, so that the +external postprocessor @samp{gbr960} (supplied by Intel) can locate all +the counters. This table is always labelled @samp{__BRANCH_TABLE__}; +this is a local symbol to permit collecting statistics for many separate +object files. The table is word aligned, and begins with a two-word +header. The first word, initialized to 0, is used in maintaining linked +lists of branch tables. The second word is a count of the number of +entries in the table, which follow immediately: each is a word, pointing +to one of the labels illustrated above. + +@ifinfo +@example + +------------+------------+------------+ ... +------------+ + | | | | | | + | *NEXT | COUNT: N | *BRLAB 1 | | *BRLAB N | + | | | | | | + +------------+------------+------------+ ... +------------+ -@subsection Syntax + __BRANCH_TABLE__ layout +@end example +@end ifinfo +@tex +\vskip 1pc +\line{\leftskip=0pt\hskip\tableindent +\boxit{2cm}{\tt *NEXT}\boxit{2cm}{\tt COUNT: \it N}\boxit{2cm}{\tt +*BRLAB 1}\ibox{1cm}{\quad\dots}\boxit{2cm}{\tt *BRLAB \it N}\hfil} +\centerline{\it {\tt \_\_BRANCH\_TABLE\_\_} layout} +@end tex -The 680x0 version of @code{as} uses syntax similar to the Sun -assembler. Size modifieres are appended directly to the end of the -opcode without an intervening period. Thus, @samp{move.l} is -written @samp{movl}, etc. +The first word of the header is used to locate multiple branch tables, +since each object file may contain one. Normally the links are +maintained with a call to an initialization routine, placed at the +beginning of each function in the file. The GNU C compiler will +generate these calls automatically when you give it a @samp{-b} option. +For further details, see the documentation of @samp{gbr960}. + +@item -norelax +Normally, Compare-and-Branch instructions with targets that require +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 +is larger than 13 bits. + +This option does not affect the Compare-and-Jump instructions; the code +emitted for them is @emph{always} adjusted when necessary (depending on +displacement size), regardless of whether you use @samp{-norelax}. +@end table + +@node Floating Point-i960,,, +_CHAPSEC__(1+_ALL_ARCH__) Floating Point +@code{_AS__} generates IEEE floating-point numbers for the directives +@samp{.float}, @samp{.double}, @samp{extended}, and @samp{.single}. + +@group +@node Directives-i960,,, +_CHAPSEC__(1+_ALL_ARCH__) Machine Directives + +@node bss-i960,,, +_CHAPSEC__(2+_ALL_ARCH__) @code{.bss @var{symbol}, @var{length}, @var{align}} +Reserve @var{length} bytes in the bss segment for a local @var{symbol}, +aligned to the power of two specified by @var{align}. @var{length} and +@var{align} must be positive absolute expressions. This directive +differs from @samp{.lcomm} only in that it permits you to specify +an alignment. @xref{Lcomm}. +@end group + +@node extended-i960,,, +_CHAPSEC__(2+_ALL_ARCH__) @code{.extended @var{flonums}} +@code{.extended} expects zero or more flonums, separated by commas; for +each flonum, @samp{.extended} emits an IEEE extended-format (80-bit) +floating-point number. + +@node leafproc-i960,,, +_CHAPSEC__(2+_ALL_ARCH__) @code{.leafproc @var{call-lab}, @var{bal-lab}} +You can use the @samp{.leafproc} directive in conjunction with the +optimized @code{callj} instruction to enable faster calls of leaf +procedures. If a procedure is known to call no other procedures, you +may define an entry point that skips procedure prolog code (and that does +not depend on system-supplied saved context), and declare it as the +@var{bal-lab} using @samp{.leafproc}. If the procedure also has an +entry point that goes through the normal prolog, you can specify that +entry point as @var{call-lab}. + +A @samp{.leafproc} declaration is meant for use in conjunction with the +optimized call instruction @samp{callj}; the directive records the data +needed later to choose between converting the @samp{callj} into a +@code{bal} or a @code{call}. + +@var{call-lab} is optional; if only one argument is present, or if the +two arguments are identical, the single argument is assumed to be the +@code{bal} entry point. + +@node sysproc-i960,,, +_CHAPSEC__(2+_ALL_ARCH__) @code{.sysproc @var{name}, @var{index}} +The @samp{.sysproc} directive defines a name for a system procedure. +After you define it using @samp{.sysproc}, you can use @var{name} to +refer to the system procedure identified by @var{index} when calling +procedures with the optimized call instruction @samp{callj}. + +Both arguments are required; @var{index} must be between 0 and 31 +(inclusive). + +@node Opcodes for i960,,, +_CHAPSEC__(1+_ALL_ARCH__) i960 Opcodes +All Intel 960 machine instructions are supported; @pxref{Options-i960} +for a discussion of selecting the instruction subset for a particular +960 architecture.@refill + +Some opcodes are processed beyond simply emitting a single corresponding +instruction: @samp{callj}, and Compare-and-Branch or Compare-and-Jump +instructions with target displacements larger than 13 bits. + +@node callj-i960 +_CHAPSEC__(2+_ALL_ARCH__) @code{callj} +You can write @code{callj} to have the assembler or the linker determine +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 +@code{callj}; if not, it will simply emit the @code{callj}, leaving it +for the linker to resolve. + +@node Compare-and-branch-i960 +_CHAPSEC__(2+_ALL_ARCH__) Compare-and-Branch + +The 960 architectures provide combined Compare-and-Branch instructions +that permit you to store the branch target in the lower 13 bits of the +instruction word itself. However, if you specify a branch target far +enough away that its address won't fit in 13 bits, the assembler can +either issue an error, or convert your Compare-and-Branch instruction +into separate instructions to do the compare and the branch. + +Whether @code{_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. + +These are the Compare-and-Branch instructions, their ``Jump'' variants, +and the instruction pairs they may expand into: + +@ifinfo +@example + Compare and + Branch Jump Expanded to + ------ ------ ------------ + bbc chkbit; bno + bbs chkbit; bo + cmpibe cmpije cmpi; be + cmpibg cmpijg cmpi; bg + cmpibge cmpijge cmpi; bge + cmpibl cmpijl cmpi; bl + cmpible cmpijle cmpi; ble + cmpibno cmpijno cmpi; bno + cmpibne cmpijne cmpi; bne + cmpibo cmpijo cmpi; bo + cmpobe cmpoje cmpo; be + cmpobg cmpojg cmpo; bg + cmpobge cmpojge cmpo; bge + cmpobl cmpojl cmpo; bl + cmpoble cmpojle cmpo; ble + cmpobne cmpojne cmpo; bne +@end example +@end ifinfo +@tex +\hskip\tableindent +\halign{\hfil {\tt #}\quad&\hfil {\tt #}\qquad&{\tt #}\hfil\cr +\omit{\hfil\it Compare and\hfil}\span\omit&\cr +{\it Branch}&{\it Jump}&{\it Expanded to}\cr + bbc& & chkbit; bno\cr + bbs& & chkbit; bo\cr + cmpibe& cmpije& cmpi; be\cr + cmpibg& cmpijg& cmpi; bg\cr + cmpibge& cmpijge& cmpi; bge\cr + cmpibl& cmpijl& cmpi; bl\cr + cmpible& cmpijle& cmpi; ble\cr + cmpibno& cmpijno& cmpi; bno\cr + cmpibne& cmpijne& cmpi; bne\cr + cmpibo& cmpijo& cmpi; bo\cr + cmpobe& cmpoje& cmpo; be\cr + cmpobg& cmpojg& cmpo; bg\cr + cmpobge& cmpojge& cmpo; bge\cr + cmpobl& cmpojl& cmpo; bl\cr + cmpoble& cmpojle& cmpo; ble\cr + cmpobne& cmpojne& cmpo; bne\cr} +@end tex -@c This is no longer true -@c Explicit size modifiers for branch instructions are ignored; @code{as} -@c automatically picks the smallest size that will reach the -destination. +_fi__(_I960__) +_if__(_M680X0__) +@group +_CHAPSEC__(0+_ALL_ARCH__) M680x0 Dependent Features +_CHAPSEC__(1+_ALL_ARCH__) M680x0 Options +The Motorola 680x0 version of @code{_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 +assembling for. +@end group -If @code{as} is compiled with SUN_ASM_SYNTAX defined, it will also -allow Sun-style local labels of the form @samp{1$} through @samp{$9}. +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 +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 +possible, and you know that the relevant symbols will be less than 17 +bits away. + +The 680x0 version of @code{_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 +@samp{-m68000}, @samp{-mc68000}, @samp{-m68010}, @samp{-mc68010}, +@samp{-m68020}, and @samp{-mc68020} to tell it what processor is the +target. + +_CHAPSEC__(1+_ALL_ARCH__) Syntax + +The 680x0 version of @code{_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 +Sun-style local labels of the form @samp{1$} through @samp{$9}. +_fi__(_INTERNALS__) In the following table @dfn{apc} stands for any of the address registers (@samp{a0} through @samp{a7}), nothing, (@samp{}), the @@ -1874,16 +2982,21 @@ or @samp{@var{apc}@@(@var{register}:@var{size}:@var{scale})@@(@var{digits})} @samp{@var{apc}@@(@var{digits})@@(@var{digits})} @item Absolute -@samp{@var{symbol}}, or @samp{@var{digits}}, or either of the above followed +@samp{@var{symbol}}, or @samp{@var{digits}} +@ignore +@c pesch@cygnus.com: gnu, rich concur the following needs careful +@c research before documenting. + , or either of the above followed by @samp{:b}, @samp{:w}, or @samp{:l}. +@end ignore @end table -@subsection Floating Point +_CHAPSEC__(1+_ALL_ARCH__) Floating Point The floating point code is not too well tested, and may have subtle bugs in it. Packed decimal (P) format floating literals are not supported. -Feel free to add the code yourself. +Feel free to add the code! The floating point formats generated by directives are these. @table @code @@ -1897,9 +3010,9 @@ There is no directive to produce regions of memory holding extended precision numbers, however they can be used as immediate operands to floating-point instructions. Adding a directive to create extended precision numbers would not be -hard. Nobody has felt any burning need to do it. +hard, but it has not yet seemed necessary. -@subsection Machine Directives +_CHAPSEC__(1+_ALL_ARCH__) Machine Directives In order to be compatible with the Sun assembler the 680x0 assembler understands the following directives. @table @code @@ -1914,25 +3027,121 @@ This directive is identical to a @code{.align 1} directive. This directive is identical to a @code{.space} directive. @end table -@subsection Opcodes +_CHAPSEC__(1+_ALL_ARCH__) Opcodes +@c pesch@cygnus.com: I don't see any point in the following +@c paragraph. Bugs are bugs; how does saying this +@c help anyone? +@ignore Danger: Several bugs have been found in the opcode table (and fixed). More bugs may exist. Be careful when using obscure instructions. +@end ignore + +_CHAPSEC__(2+_ALL_ARCH__) Branch Improvement + +Certain pseudo opcodes are permitted for branch instructions. +They expand to the shortest branch instruction that will reach the +target. Generally these mnemonics are made by substituting @samp{j} for +@samp{b} at the start of a Motorola mnemonic. + +The following table summarizes the pseudo-operations. A @code{*} flags +cases that are more fully described after the table: -The assembler automatically chooses the proper size for branch -instructions. However, most attempts to force a short displacement -will be honored. Branches that are forced to use a short -displacement will not be adjusted if the target is out of range. -Let The User Beware. +@smallexample + Displacement + +--------------------------------------------------------- + | 68020 68000/10 +Pseudo-Op |BYTE WORD LONG LONG non-PC relative + +--------------------------------------------------------- + jbsr |bsrs bsr bsrl jsr jsr + jra |bras bra bral jmp jmp +* jXX |bXXs bXX bXXl bNXs;jmpl bNXs;jmp +* dbXX |dbXX dbXX dbXX; bra; jmpl +* fjXX |fbXXw fbXXw fbXXl fbNXw;jmp +XX: condition +NX: negative of condition XX + +@end smallexample +@center{@code{*}---see full description below} + +@table @code +@item jbsr +@itemx jra +These are the simplest jump pseudo-operations; they always map to one +particular machine instruction, depending on the displacement to the +branch target. + +@item j@var{XX} +Here, @samp{j@var{XX}} stands for an entire family of pseudo-operations, +where @var{XX} is a conditional branch or condition-code test. The full +list of pseudo-ops in this family is: +@smallexample + jhi jls jcc jcs jne jeq jvc + jvs jpl jmi jge jlt jgt jle +@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 +@var{NX}, the opposite condition to @var{XX}: +@smallexample + j@var{XX} foo +@end smallexample +gives +@smallexample + b@var{NX}s oof + jmp foo + oof: +@end smallexample + +@item db@var{XX} +The full family of pseudo-operations covered here is +@smallexample + dbhi dbls dbcc dbcs dbne dbeq dbvc + dbvs dbpl dbmi dbge dblt dbgt dble + dbf dbra dbt +@end smallexample + +Other than for word and byte displacements, when the source reads +@samp{db@var{XX} foo}, @code{_AS__} will emit +@smallexample + db@var{XX} oo1 + bra oo2 + oo1:jmpl foo + oo2: +@end smallexample + +@item fj@var{XX} +This family includes +@smallexample + fjne fjeq fjge fjlt fjgt fjle fjf + fjt fjgl fjgle fjnge fjngl fjngle fjngt + fjnle fjnlt fjoge fjogl fjogt fjole fjolt + fjor fjseq fjsf fjsne fjst fjueq fjuge + fjugt fjule fjult fjun +@end smallexample + +For branch targets that are not PC relative, @code{_AS__} emits +@smallexample + fb@var{NX} oof + jmp foo + oof: +@end smallexample +when it encounters @samp{fj@var{XX} foo}. + +@end table + +_CHAPSEC__(2+_ALL_ARCH__) Special Characters The immediate character is @samp{#} for Sun compatibility. The line-comment character is @samp{|}. If a @samp{#} appears at the 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__) +@c pesch@cygnus.com: conditionalize on something other than 0 when filled in. +_if__(0) @section 32x32 -@subsection Options -The 32x32 version of @code{as} accepts a @kbd{-m32032} option to +@section Options +The 32x32 version of @code{_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 @@ -1940,17 +3149,20 @@ is compiled. @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{_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 IEEE floating point numbers, but @code{as} will only +The 32x32 uses IEEE floating point numbers, but @code{_AS__} will only create single or double precision values. I don't know if the 32x32 understands extended precision numbers. @subsection Machine Directives The 32x32 has no machine dependent directives. - +_fi__(0) +_if__(_SPARC__) +@c fixme (sparc): Fill in "syntax" section! +_CHAPSEC__(0+_ALL_ARCH__) SPARC Dependent Features @section Sparc @subsection Options The sparc has no machine dependent options. @@ -1963,7 +3175,7 @@ will have to write this section. The Sparc uses ieee floating-point numbers. @subsection Machine Directives -The Sparc version of @code{as} supports the following additional +The Sparc version of @code{_AS__} supports the following additional machine directives: @table @code @@ -2000,14 +3212,15 @@ On the Sparc, the .word directive produces 32 bit values, instead of the 16 bit values it produces on every other machine. @end table - -@section Intel 80386 -@subsection Options +_fi__(_SPARC__) +_if__(_I80386__) +_CHAPSEC__(0+_ALL_ARCH__) 80386 Dependent Features +_CHAPSEC__(1+_ALL_ARCH__) Options The 80386 has no machine dependent options. -@subsection AT&T Syntax versus Intel Syntax -In order to maintain compatibility with the output of @code{GCC}, -@code{as} supports AT&T System V/386 assembler syntax. This is quite +_CHAPSEC__(1+_ALL_ARCH__) AT&T Syntax versus Intel Syntax +In order to maintain compatibility with the output of @code{_GCC__}, +@code{_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: @@ -2039,7 +3252,7 @@ Immediate form long jumps and calls are @samp{lcall/ljmp $@var{segment}, $@var{offset}} in AT&T syntax; the Intel syntax is @samp{call/jmp far @var{segment}:@var{offset}}. Also, the far return -instruction +instruction is @samp{lret $@var{stack-adjust}} in AT&T syntax; Intel syntax is @samp{ret far @var{stack-adjust}}. @@ -2048,11 +3261,11 @@ The AT&T assembler does not provide support for multiple segment programs. Unix style systems expect all programs to be single segments. @end itemize -@subsection Opcode Naming +_CHAPSEC__(1+_ALL_ARCH__) Opcode Naming 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{_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 @@ -2086,13 +3299,13 @@ The Intel syntax conversion instructions @samp{cdq} --- sign-extend dword in @samp{%eax} to quad in @samp{%edx:%eax}, @end itemize 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{_AS__} accepts either naming for these instructions. Far call/jump instructions are @samp{lcall} and @samp{ljmp} in AT&T syntax, but are @samp{call far} and @samp{jump far} in Intel -convention. +convention. -@subsection Register Naming +_CHAPSEC__(1+_ALL_ARCH__) Register Naming Register operands are always prefixes with @samp{%}. The 80386 registers consist of @itemize @bullet @@ -2133,7 +3346,7 @@ the 8 floating point register stack @samp{%st} or equivalently @samp{%st(4)}, @samp{%st(5)}, @samp{%st(6)}, and @samp{%st(7)}. @end itemize -@subsection Opcode Prefixes +_CHAPSEC__(1+_ALL_ARCH__) Opcode Prefixes Opcode prefixes are used to modify the following opcode. They are used to repeat string instructions, to provide segment overrides, to perform bus lock operations, and to give operand and address size (16-bit @@ -2142,10 +3355,10 @@ normally be 32-bit operands with a ``operand size'' opcode prefix). Opcode prefixes are usually given as single-line instructions with no operands, and must directly precede the instruction they act upon. For example, the @samp{scas} (scan string) instruction is repeated with: -@example +@smallexample repne scas -@end example +@end smallexample Here is a list of opcode prefixes: @itemize @bullet @@ -2175,15 +3388,15 @@ The @samp{rep}, @samp{repe}, and @samp{repne} prefixes are added to string instructions to make them repeat @samp{%ecx} times. @end itemize -@subsection Memory References +_CHAPSEC__(1+_ALL_ARCH__) Memory References An Intel syntax indirect memory reference of the form -@example +@smallexample @var{segment}:[@var{base} + @var{index}*@var{scale} + @var{disp}] -@end example +@end smallexample is translated into the AT&T syntax -@example +@smallexample @var{segment}:@var{disp}(@var{base}, @var{index}, @var{scale}) -@end example +@end smallexample where @var{base} and @var{index} are the optional 32-bit base and index registers, @var{disp} is the optional displacement, and @var{scale}, taking the values 1, 2, 4, and 8, multiplies @var{index} @@ -2193,7 +3406,7 @@ optional segment register for the memory operand, and may override the default segment register (see a 80386 manual for segment register defaults). Note that segment overrides in AT&T syntax @emph{must} have be preceded by a @samp{%}. If you specify a segment override which -coincides with the default segment register, @code{as} will @emph{not} +coincides with the default segment register, @code{_AS__} will @emph{not} output any segment register override prefixes to assemble the given instruction. Thus, segment overrides can be specified to emphasize which segment register is used for a given memory operand. @@ -2219,18 +3432,18 @@ Note that @var{base} and @var{index} are both missing, but there is only @item AT&T: @samp{%gs:foo}; Intel @samp{gs:foo} This selects the contents of the variable @samp{foo} with segment register @var{segment} being @samp{%gs}. - + @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 -always choose PC relative addressing for jump/call labels. +prefixed with @samp{*}. If no @samp{*} is specified, @code{_AS__} will +always choose PC relative addressing for jump/call labels. Any instruction that has a memory operand @emph{must} specify its size (byte, word, or long) with an opcode suffix (@samp{b}, @samp{w}, or @samp{l}, respectively). -@subsection Handling of Jump Instructions +_CHAPSEC__(1+_ALL_ARCH__) Handling of Jump Instructions Jump instructions are always optimized to use the smallest possible displacements. This is accomplished by using byte (8-bit) displacement jumps whenever the target is sufficiently close. If a byte displacement @@ -2242,17 +3455,17 @@ with the @samp{addr16} opcode prefix), since the 80386 insists upon masking Note that the @samp{jcxz}, @samp{jecxz}, @samp{loop}, @samp{loopz}, @samp{loope}, @samp{loopnz} and @samp{loopne} instructions only come in byte displacements, so that it is possible that use of these -instructions (@code{GCC} does not use them) will cause the assembler to +instructions (@code{_GCC__} does not use them) will cause the assembler to print an error message (and generate incorrect code). The AT&T 80386 assembler tries to get around this problem by expanding @samp{jcxz foo} to -@example +@smallexample jcxz cx_zero jmp cx_nonzero cx_zero: jmp foo cx_nonzero: -@end example +@end smallexample -@subsection Floating Point +_CHAPSEC__(1+_ALL_ARCH__) Floating Point All 80387 floating point types except packed BCD are supported. (BCD support may be added without much difficulty). These data types are 16-, 32-, and 64- bit integers, and single (32-bit), @@ -2284,21 +3497,21 @@ so that @samp{fst %st, %st(1)} is equivalent to @samp{fstl %st, %st(1)}. 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} supresses +80286/80287 and 8086/8087 combinations). Therefore, @code{_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{}} instructions are made equivalent to @samp{f@dots{}} instructions. If @samp{fwait} is desired it must be explicitly coded. -@subsection Notes +_CHAPSEC__(1+_ALL_ARCH__) Notes There is some trickery concerning the @samp{mul} and @samp{imul} instructions that deserves mention. The 16-, 32-, and 64-bit expanding multiplies (base opcode @samp{0xf6}; extension 4 for @samp{mul} and 5 for @samp{imul}) can be output only in the one operand form. Thus, @samp{imul %ebx, %eax} does @emph{not} select the expanding multiply; the expanding multiply would clobber the @samp{%edx} register, and this -would confuse @code{GCC} output. Use @samp{imul %ebx} to get the +would confuse @code{_GCC__} output. Use @samp{imul %ebx} to get the 64-bit product in @samp{%edx:%eax}. We have added a two operand form of @samp{imul} when the first operand @@ -2306,8 +3519,13 @@ is an immediate mode expression and the second operand is a register. This is just a shorthand, so that, multiplying @samp{%eax} by 69, for example, can be done with @samp{imul $69, %eax} rather than @samp{imul $69, %eax, %eax}. - -@node Maintenance, Retargeting, MachineDependent, top +_fi__(_I80386__) +_if__(0) +@c pesch@cygnus.com: we ignore the following chapters, since internals are +@c changing rapidly. These may need to be moved to another +@c book anyhow, if we adopt the model of user/modifier +@c books. +@node Maintenance, Retargeting, _MACH_DEP__, Top @chapter Maintaining the Assembler [[this chapter is still being built]] @@ -2315,13 +3533,13 @@ $69, %eax, %eax}. 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{_AS__} should emit ``correct'' code. This leaves some latitude in choosing addressing modes, order of @code{relocation_info} structures in the object -file, @i{etc}. +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{_AS__} will be assembling compiler emissions. @item Upward compatibility for existing assembler code. @@ -2356,7 +3574,7 @@ large buffers. RMS suggested a one-pass algorithm which seems to work well. By not parsing text during a second pass considerable time is saved on -large programs (@i{e.g.} the sort of C program @code{yacc} would +large programs (@emph{e.g.} the sort of C program @code{yacc} would emit). It happened that the data structures needed to emit relocation @@ -2367,7 +3585,7 @@ Many of the functions began life as re-usable modules, loosely connected. RMS changed this to gain speed. For example, input parsing routines which used to work on pre-sanitized strings now must parse raw data. Hence they have to import knowledge of the -assemblers' comment conventions @i{etc}. +assemblers' comment conventions @emph{etc}. @section Deprecated Feature(?)s We have stopped supporting some features: @@ -2396,22 +3614,22 @@ interpret binary gobbledygook from a compiler's tables than to 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{_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{_AS__}. (Modify @code{app.c} to flush useless spaces: only keep space/tabs at begin of line or between 2 symbols.) @item Put pointers in this documentation to @file{a.out} documentation. @item Split the assembler into parts so it can gobble direct binary -from @i{e.g.} @code{cc}. It is silly for@code{cc} to compose text -just so @code{as} can parse it back to 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. @item Rewrite hash functions: I want a more modular, faster library. @item @@ -2424,7 +3642,7 @@ Document flonums. Implement flonum short literals. @item Change all talk of expression operands to expression quantities, -or perhaps to expression primaries. +or perhaps to expression arguments. @item Implement pass 2. @item @@ -2440,7 +3658,7 @@ relaxable addresses, which is common). @end itemize @section Sources -@c The following files in the @file{as} directory +@c The following files in the @file{_AS__} directory @c are symbolic links to other files, of @c the same name, in a different directory. @c @itemize @bullet @@ -2462,7 +3680,7 @@ relaxable addresses, which is common). @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{_AS__} directory. @table @file @item app.c @@ -2476,14 +3694,14 @@ pointer just after the last @code{char} appended. (JF: All these 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{_AS__}. @item expr.c This is a branch office of @file{read.c}. This understands -expressions, primaries. Inside @code{as}, primaries are called -(expression) @i{operands}. This is confusing, because we also talk -(elsewhere) about instruction @i{operands}. Also, expression -operands are called @i{quantities} explicitly to avoid confusion +expressions, arguments. Inside @code{_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 with instruction operands. What a mess. @item frags.c @@ -2491,7 +3709,7 @@ This implements the @b{frag} concept. Without frags, finding the right size for branch instructions would be a lot harder. @item hash.c -This contains the symbol table, opcode table @i{etc.} hashing +This contains the symbol table, opcode table @emph{etc.} hashing functions. @item hex_value.c @@ -2502,7 +3720,7 @@ something similar. @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{_AS__} is intended to run under GNU and Unix only, this might be worth flushing. Anyway, almost all C compilers support stdio. @@ -2516,10 +3734,10 @@ warning message reporting. See @file{append.c} above. @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{_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{_AS__}. This also deals with passing input lines to the machine dependent part of the assembler. @@ -2577,7 +3795,7 @@ be identical to the one used by GDB (which uses it for disassembly.) @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{_AS__}. @item i386-opcode.h This is the opcode-table for the i386 version of the assembler. @@ -2634,7 +3852,7 @@ Vax specific file for describing Vax operands and other Vax-ish things. Vax opcode table. @item vax.c -Vax specific parts of @code{as}. Also includes the former files +Vax specific parts of @code{_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 @@ -2660,8 +3878,8 @@ inside the object file. Perhaps we should use the one in @file{/usr/include}? @item as.h -This defines all the globally useful things, and pulls in <stdio.h> -and <assert.h>. +This defines all the globally useful things, and pulls in _0__<stdio.h>_1__ +and _0__<assert.h>_1__. @item bignum.h This defines macros useful for dealing with bignums. @@ -2694,7 +3912,7 @@ Since nobody is running under real GNU yet, we include this file. Macros and function headers for reading in source files. @item struct-symbol.h -Structure definition and macros for dealing with the gas +Structure definition and macros for dealing with the _AS__ internal form of a symbol. @item subsegs.h @@ -2712,40 +3930,40 @@ Structure for doing segment fixups. @comment (Note: The test directory seems to have disappeared somewhere @comment along the line. If you want it, you'll probably have to find a @comment REALLY OLD dump tape~dots{}) -@comment +@comment @comment The ~file{test/} directory is used for regression testing. -@comment After you modify ~code{as}, you can get a quick go/nogo -@comment confidence test by running the new ~code{as} over the source +@comment After you modify ~@code{_AS__}, you can get a quick go/nogo +@comment confidence test by running the new ~@code{_AS__} over the source @comment files in this directory. You use a shell script ~file{test/do}. -@comment +@comment @comment The tests in this suite are evolving. They are not comprehensive. @comment They have, however, caught hundreds of bugs early in the debugging -@comment cycle of ~code{as}. Most test statements in this suite were naturally -@comment selected: they were used to demonstrate actual ~code{as} bugs rather +@comment cycle of ~@code{_AS__}. Most test statements in this suite were naturally +@comment selected: they were used to demonstrate actual ~@code{_AS__} bugs rather @comment than being written ~i{a prioi}. -@comment +@comment @comment Another testing suggestion: over 30 bugs have been found simply by -@comment running examples from this manual through ~code{as}. +@comment running examples from this manual through ~@code{_AS__}. @comment Some examples in this manual are selected -@comment to distinguish boundary conditions; they are good for testing ~code{as}. -@comment +@comment to distinguish boundary conditions; they are good for testing ~@code{_AS__}. +@comment @comment ~subsubsection Regression Testing @comment Each regression test involves assembling a file and comparing the -@comment actual output of ~code{as} to ``known good'' output files. Both +@comment actual output of ~@code{_AS__} to ``known good'' output files. Both @comment the object file and the error/warning message file (stderr) are -@comment inspected. Optionally ~code{as}' exit status may be checked. +@comment inspected. Optionally the ~@code{_AS__} exit status may be checked. @comment Discrepencies are reported. Each discrepency means either that -@comment you broke some part of ~code{as} or that the ``known good'' files +@comment you broke some part of ~@code{_AS__} or that the ``known good'' files @comment are now out of date and should be changed to reflect the new @comment definition of ``good''. -@comment +@comment @comment Each regression test lives in its own directory, in a tree @comment rooted in the directory ~file{test/}. Each such directory @comment has a name ending in ~file{.ret}, where `ret' stands for @comment REgression Test. The ~file{.ret} ending allows ~code{find @comment (1)} to find all regression tests in the tree, without @comment needing to list them explicitly. -@comment +@comment @comment Any ~file{.ret} directory must contain a file called @comment ~file{input} which is the source file to assemble. During @comment testing an object file ~file{output} is created, as well as @@ -2756,17 +3974,17 @@ Structure for doing segment fixups. @comment deleted. Likewise ~file{stdouterr} is removed if it exactly @comment matches a file ~file{stdouterr.good}. If file @comment ~file{status.good} is present, containing a decimal number -@comment before a newline, the exit status of ~code{as} is compared +@comment before a newline, the exit status of ~@code{_AS__} is compared @comment to this number. If the status numbers are not equal, a file @comment ~file{status} is written to the directory, containing the @comment actual status as a decimal number followed by newline. -@comment +@comment @comment Should any of the ~file{*.good} files fail to match their corresponding @comment actual files, this is noted by a 1-line message on the screen during -@comment the regression test, and you can use ~code{find (1)} to find any +@comment the regression test, and you can use ~@code{find (1)} to find any @comment files named ~file{status}, ~file {output} or ~file{stdouterr}. -@comment -@node Retargeting, , Maintenance, top +@comment +@node Retargeting, License, Maintenance, Top @chapter Teaching the Assembler about a New Machine This chapter describes the steps required in order to make the @@ -2782,16 +4000,16 @@ you can compile your new version of the assembler. This should be straighforward; simply add lines similar to the ones there for the four current versions of the assembler. -If you want to be compatable with GDB, (and the current +If you want to be compatible with GDB, (and the current machine-dependent versions of the assembler), you should create a file called @file{@var{machine}-opcode.h} which should contain all the information about the names of the machine 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{_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{_AS__} is emitting the correct bytes. Since @code{_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}. @@ -2818,7 +4036,7 @@ start a comment anywhere in a line. Comments are stripped off automatically by the machine independent part of the assembler. Note that the @samp{/*} will always start a comment, and that only @samp{*/} will end a comment started by -@samp{*/}. +@samp{*/}. @item char line_comment_chars[]; This character array holds the values of the chars that start a @@ -2855,7 +4073,7 @@ any of your other routines. @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{_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 @@ -3055,7 +4273,7 @@ This function stores a relocation fixup to be acted on later. @var{size} is the size of the relocation, and is usually 1 (a single byte), 2 (sixteen bits), or 4 (a longword). The value @var{add_symbol} @minus{} @var{sub_symbol} + @var{offset}, is added to the byte(s) -at @var{frag->literal[where]}. If @var{pcrel} is non-zero, the address of the +at _0__@var{frag->literal[where]}_1__. If @var{pcrel} is non-zero, the address of the location is subtracted from the result. A relocation entry is also added to the @file{a.out} file. @var{add_symbol}, @var{sub_symbol}, and/or @var{offset} may be NULL.@refill @@ -3098,8 +4316,8 @@ line number, then uses @code{fprintf} to print the @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{_AS__} encounters +conditions that are bad enough that @code{_AS__} should not produce an object file, but should continue reading input and printing warning and bad error messages. @@ -3138,10 +4356,10 @@ modes. (e.g. branch instructions) This means the size of many 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{_AS__} stores the output bytes as @dfn{frags}. Here is the definition of a frag (from @file{as.h}) -@example +@smallexample struct frag @{ long int fr_fix; @@ -3155,7 +4373,7 @@ struct frag struct frag *fr_next; char fr_literal[]; @} -@end example +@end smallexample @table @var @item fr_fix @@ -3209,19 +4427,315 @@ actual object bytes. A frag consists of a fixed size piece of object data, (which may be zero bytes long), followed by a piece of object data whose size may not have been determined yet. Other information includes the type of the frag (which -controls how it is relaxed), +controls how it is relaxed), @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{_AS__}. @end table +_fi__(0) + +@node License, , Retargeting, Top +@unnumbered GNU GENERAL PUBLIC LICENSE +@center Version 1, February 1989 + +@display +Copyright @copyright{} 1989 Free Software Foundation, Inc. +675 Mass Ave, Cambridge, MA 02139, USA + +Everyone is permitted to copy and distribute verbatim copies +of this license document, but changing it is not allowed. +@end display + +@unnumberedsec Preamble + + The license agreements of most software companies try to keep users +at the mercy of those companies. By contrast, our General Public +License is intended to guarantee your freedom to share and change free +software---to make sure the software is free for all its users. The +General Public License applies to the Free Software Foundation's +software and to any other program whose authors commit to using it. +You can use it for your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Specifically, the General Public License is designed to make +sure that you have the freedom to give away or sell copies of free +software, that you receive source code or can get it if you want it, +that you can change the software or use pieces of it in new free +programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of a such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must tell them their rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + The precise terms and conditions for copying, distribution and +modification follow. + +@iftex +@unnumberedsec TERMS AND CONDITIONS +@end iftex +@ifinfo +@center TERMS AND CONDITIONS +@end ifinfo + +@enumerate +@item +This License Agreement applies to any program or other work which +contains a notice placed by the copyright holder saying it may be +distributed under the terms of this General Public License. The +``Program'', below, refers to any such program or work, and a ``work based +on the Program'' means either the Program or any work containing the +Program or a portion of it, either verbatim or with modifications. Each +licensee is addressed as ``you''. + +@item +You may copy and distribute verbatim copies of the Program's source +code as you receive it, in any medium, provided that you conspicuously and +appropriately publish on each copy an appropriate copyright notice and +disclaimer of warranty; keep intact all the notices that refer to this +General Public License and to the absence of any warranty; and give any +other recipients of the Program a copy of this General Public License +along with the Program. You may charge a fee for the physical act of +transferring a copy. + +@item +You may modify your copy or copies of the Program or any portion of +it, and copy and distribute such modifications under the terms of Paragraph +1 above, provided that you also do the following: + +@itemize @bullet +@item +cause the modified files to carry prominent notices stating that +you changed the files and the date of any change; and + +@item +cause the whole of any work that you distribute or publish, that +in whole or in part contains the Program or any part thereof, either +with or without modifications, to be licensed at no charge to all +third parties under the terms of this General Public License (except +that you may choose to grant warranty protection to some or all +third parties, at your option). + +@item +If the modified program normally reads commands interactively when +run, you must cause it, when started running for such interactive use +in the simplest and most usual way, to print or display an +announcement including an appropriate copyright notice and a notice +that there is no warranty (or else, saying that you provide a +warranty) and that users may redistribute the program under these +conditions, and telling the user how to view a copy of this General +Public License. + +@item +You may charge a fee for the physical act of transferring a +copy, and you may at your option offer warranty protection in +exchange for a fee. +@end itemize + +Mere aggregation of another independent work with the Program (or its +derivative) on a volume of a storage or distribution medium does not bring +the other work under the scope of these terms. + +@item +You may copy and distribute the Program (or a portion or derivative of +it, under Paragraph 2) in object code or executable form under the terms of +Paragraphs 1 and 2 above provided that you also do one of the following: + +@itemize @bullet +@item +accompany it with the complete corresponding machine-readable +source code, which must be distributed under the terms of +Paragraphs 1 and 2 above; or, + +@item +accompany it with a written offer, valid for at least three +years, to give any third party free (except for a nominal charge +for the cost of distribution) a complete machine-readable copy of the +corresponding source code, to be distributed under the terms of +Paragraphs 1 and 2 above; or, + +@item +accompany it with the information you received as to where the +corresponding source code may be obtained. (This alternative is +allowed only for noncommercial distribution and only if you +received the program in object code or executable form alone.) +@end itemize + +Source code for a work means the preferred form of the work for making +modifications to it. For an executable file, complete source code means +all the source code for all modules it contains; but, as a special +exception, it need not include source code for modules which are standard +libraries that accompany the operating system on which the executable +file runs, or for standard header files or definitions files that +accompany that operating system. + +@item +You may not copy, modify, sublicense, distribute or transfer the +Program except as expressly provided under this General Public License. +Any attempt otherwise to copy, modify, sublicense, distribute or transfer +the Program is void, and will automatically terminate your rights to use +the Program under this License. However, parties who have received +copies, or rights to use copies, from you under this General Public +License will not have their licenses terminated so long as such parties +remain in full compliance. + +@item +By copying, distributing or modifying the Program (or any work based +on the Program) you indicate your acceptance of this license to do so, +and all its terms and conditions. + +@item +Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the original +licensor to copy, distribute or modify the Program subject to these +terms and conditions. You may not impose any further restrictions on the +recipients' exercise of the rights granted herein. + +@item +The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of the license which applies to it and ``any +later version'', you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +the license, you may choose any version ever published by the Free Software +Foundation. + +@item +If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + +@iftex +@heading NO WARRANTY +@end iftex +@ifinfo +@center NO WARRANTY +@end ifinfo + +@item +BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM ``AS IS'' WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + +@item +IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL +ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES +ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT +LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES +SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE +WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN +ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. +@end enumerate -@c Is this really a good idea? @iftex -@center [end of manual] +@heading END OF TERMS AND CONDITIONS @end iftex +@ifinfo +@center END OF TERMS AND CONDITIONS +@end ifinfo + +@page +@unnumberedsec Applying These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to humanity, the best way to achieve this is to make it +free software which everyone can redistribute and change under these +terms. + + To do so, attach the following notices to the program. It is safest to +attach them to the start of each source file to most effectively convey +the exclusion of warranty; and each file should have at least the +``copyright'' line and a pointer to where the full notice is found. + +@smallexample +@var{one line to give the program's name and a brief idea of what it does.} +Copyright (C) 19@var{yy} @var{name of author} + +This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +This program is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with this program; if not, write to the Free Software +Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. +@end smallexample + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + +@smallexample +Gnomovision version 69, Copyright (C) 19@var{yy} @var{name of author} +Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. +This is free software, and you are welcome to redistribute it +under certain conditions; type `show c' for details. +@end smallexample + +The hypothetical commands `show w' and `show c' should show the +appropriate parts of the General Public License. Of course, the +commands you use may be called something other than `show w' and `show +c'; they could even be mouse-clicks or menu items---whatever suits your +program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a ``copyright disclaimer'' for the program, if +necessary. Here is a sample; alter the names: + +@smallexample +Yoyodyne, Inc., hereby disclaims all copyright interest in the +program `Gnomovision' (a program to direct compilers to make passes +at assemblers) written by James Hacker. + +@var{signature of Ty Coon}, 1 April 1989 +Ty Coon, President of Vice +@end smallexample + +That's all there is to it! + + @summarycontents @contents @bye diff --git a/gas/doc/i80386.m4 b/gas/doc/i80386.m4 new file mode 100644 index 0000000..d8293d1 --- /dev/null +++ b/gas/doc/i80386.m4 @@ -0,0 +1,5 @@ +_divert__(-1) +_define__(<_I80386__>,<1>) +_define__(<_HOST__>,<Intel 80386>) +_define__(<_MACH_DEP__>,<80386 Dependent> +_divert__<>
\ No newline at end of file diff --git a/gas/doc/i960.m4 b/gas/doc/i960.m4 new file mode 100644 index 0000000..e98155d --- /dev/null +++ b/gas/doc/i960.m4 @@ -0,0 +1,12 @@ +_divert__(-1) +_define__(<_I960__>,<1>) +_define__(<_AOUT__>,<0>) +_define__(<_BOUT__>,<1>) +_define__(<_COFF__>,<1>) +_define__(<_AS__>,<gas960>) +_define__(<_GCC__>,<gcc960>) +_define__(<_LD__>,<gld960>) +_define__(<_GDB__>,<gdb960>) +_define__(<_HOST__>,<Intel 960>) +_define__(<_MACH_DEP__>,<i960 Dependent>) +_divert__<>
\ No newline at end of file diff --git a/gas/doc/m680x0.m4 b/gas/doc/m680x0.m4 new file mode 100644 index 0000000..e5f83b6 --- /dev/null +++ b/gas/doc/m680x0.m4 @@ -0,0 +1,5 @@ +_divert__(-1) +_define__(<_M680X0__>,<1>) +_define__(<_HOST__>,<Motorola 680x0>) +_define__(<_MACH_DEP__>,<M680x0 Dependent>) +_divert__<>
\ No newline at end of file diff --git a/gas/doc/none.m4 b/gas/doc/none.m4 new file mode 100644 index 0000000..327ef3e --- /dev/null +++ b/gas/doc/none.m4 @@ -0,0 +1,36 @@ +_divert__(-1) + +Switches: + +_define__(<_ALL_ARCH__>,<0>) +_define__(<_INTERNALS__>,<0>) + +_define__(<_AOUT__>,<1>) +_define__(<_BOUT__>,<0>) +_define__(<_COFF__>,<0>) +_define__(<_ELF__>,<0>) + +_define__(<_AMD29K__>,<0>) +_define__(<_I80386__>,<0>) +_define__(<_I960__>,<0>) +_define__(<_M680X0__>,<0>) +_define__(<_SPARC__>,<0>) +_define__(<_VAX__>,<0>) + +Text: + +Default names for assembler, compiler, linker, debugger; + individual configs may override +_define__(<_AS__>,<as>) +_define__(<_GCC__>,<gcc>) +_define__(<_LD__>,<ld>) +_define__(<_GDB__>,<gdb>) + +Text for host; individual configs *should* override, but this may +catch some flubs +_define__(<_HOST__>,<machine specific>) + +"Machine Dependent" nodename +_define__(<_MACH_DEP__>,<Machine Dependent>) + +_divert__<>
\ No newline at end of file diff --git a/gas/doc/pretex.m4 b/gas/doc/pretex.m4 new file mode 100644 index 0000000..3fe9e05 --- /dev/null +++ b/gas/doc/pretex.m4 @@ -0,0 +1,252 @@ +divert(-1) -*-Text-*- + +I. INTRODUCTION + +This collection of M4 macros is meant to help in pre-processing texinfo +files to allow configuring them by hosts; for example, the reader of an +as manual who only has access to a 386 may not really want to see crud about +VAXen. + +A preprocessor is used, rather than extending texinfo, because this +way we can hack the conditionals in only one place; otherwise we would +have to write TeX macros, update makeinfo, and update the Emacs +info-formatting functions. + +II. COMPATIBILITY + +These macros should work with GNU m4 and System V m4; they do not work +with Sun or Berkeley M4. + +III. USAGE + +A. M4 INVOCATION +Assume this file is called "pretex.m4". Then, to preprocess a +document "mybook.texinfo" you might do something like the following: + + m4 pretex.m4 none.m4 PARTIC.m4 mybook.texinfo >mybook-PARTIC.texinfo + +---where your path is set to find GNU or SysV "m4", and the other m4 +files mentioned are as follows: + + none.m4: A file that defines, as 0, all the options you might + want to turn on using the conditionals defined below. + Unlike the C preprocessor, m4 does not default + undefined macros to 0. For example, here is a "none.m4" + I have been using: + _divert__(-1) + + _define__(<_ALL_ARCH__>,<0>) + _define__(<_INTERNALS__>,<0>) + + _define__(<_AMD29K__>,<0>) + _define__(<_I80386__>,<0>) + _define__(<_I960__>,<0>) + _define__(<_M680X0__>,<0>) + _define__(<_SPARC__>,<0>) + _define__(<_VAX__>,<0>) + + _divert__<> + + PARTIC.m4: A file that turns on whichever options you actually + want the manual configured for, in this particular + instance. Its contents are similar to one or more of + the lines in "none.m4", but of course the second + argument to _define__ is <1> rather than <0>. + + This is also a convenient place to define any macros + that you want to expand to different text for + different configurations---for example, the name of + the program being described. + +Naturally, these are just suggested conventions; you could put your macro +definitions in any files or combinations of files you like. + +These macros use the characters < and > as m4 quotes; if you need +these characters in your text, you will also want to use the macros +_0__ and _1__ from this package---see the description of "Quote +Handling" in the "Implementation" section below. + +B. WHAT GOES IN THE PRE-TEXINFO SOURCE + +For the most part, the text of your book. In addition, you can +include text that is included only conditionally, using the macros +_if__ and _fi__ defined below. They BOTH take an argument! This is +primarily meant for readability (so a human can more easily see what +conditional end matches what conditional beginning), but the argument +is actually used in the _fi__ as well as the _if__ implementation. +You should always give a _fi__ the same argument as its matching +_if__. Other arguments may appear to work for a while, but are almost +certain to produce the wrong output for some configurations. + +For example, here is an excerpt from the very beginning of the +documentation for GNU as, to name the info file appropriately for +different configurations: + _if__(_ALL_ARCH__) + @setfilename as.info + _fi__(_ALL_ARCH__) + _if__(_M680X0__ && !_ALL_ARCH__) + @setfilename as-m680x0.info + _fi__(_M680X0__ && !_ALL_ARCH__) + _if__(_AMD29K__ && !_ALL_ARCH__) + @setfilename as-29k.info + _fi__(_AMD29K__ && !_ALL_ARCH__) + +Note that you can use Boolean expressions in the arguments; the +expression language is that of the builtin m4 macro "eval", described +in the m4 manual. + +IV. IMPLEMENTATION + +A.PRIMITIVE RENAMING +First, we redefine m4's built-ins to avoid conflict with plain text. +The naming convention used is that our macros all begin with a single +underbar and end with two underbars. The asymmetry is meant to avoid +conflict with some other conventions (which we may want to document) that +are intended to avoid conflict, like ANSI C predefined macros. + +define(`_undefine__',defn(`undefine')) +define(`_define__',defn(`define')) +define(`_defn__',defn(`defn')) +define(`_ppf__',`_define__(`_$1__',_defn__(`$1'))_undefine__(`$1')') +_ppf__(`builtin') +_ppf__(`changecom') +_ppf__(`changequote') +_ppf__(`decr') +_ppf__(`define') +_ppf__(`defn') +_ppf__(`divert') +_ppf__(`dnl') +_ppf__(`dumpdef') +_ppf__(`errprint') +_ppf__(`eval') +_ppf__(`ifdef') +_ppf__(`ifelse') +_ppf__(`include') +_ppf__(`incr') +_ppf__(`index') +_ppf__(`len') +_ppf__(`m4exit') +_ppf__(`m4wrap') +_ppf__(`maketemp') +_ppf__(`popdef') +_ppf__(`pushdef') +_ppf__(`shift') +_ppf__(`sinclude') +_ppf__(`substr') +_ppf__(`syscmd') +_ppf__(`sysval') +_ppf__(`traceoff') +_ppf__(`traceon') +_ppf__(`translit') +_ppf__(`undefine') +_ppf__(`undivert') + +B. QUOTE HANDLING. + +The characters used as quotes by M4, by default, are unfortunately +quite likely to occur in ordinary text. To avoid surprises, we will +use the characters <> ---which are just as suggestive (more so to +Francophones, perhaps) but a little less common in text (save for +those poor Francophones. You win some, you lose some). Still, we +expect also to have to set < and > occasionally in text; to do that, +we define a macro to turn off quote handling (_0__) and a macro to +turn it back on (_1__), according to our convention. + + BEWARE: This seems to make < and > unusable as relational operations + in calls to the builtin "eval". So far I've gotten + along without; but a better choice may be possible. + +Note that we postponed this for a while, for convenience in discussing +the issue and in the primitive renaming---not to mention in defining +_0__ and _1__ themselves! However, the quote redefinitions MUST +precede the _if__ / _fi__ definitions, because M4 will expand the text +as given---if we use the wrong quotes here, we will get the wrong +quotes when we use the conditionals. + +_define__(_0__,`_changequote__(,)')_define__(_1__,`_changequote__(<,>)') +_1__ + +C. CONDITIONALS + +We define two macros, _if__ and _fi__. BOTH take arguments! This is +meant both to help the human reader match up a _fi__ with its +corresponding _if__ and to aid in the implementation. You may use the +full expression syntax supported by M4 (see docn of `eval' builtin in +the m4 manual). + +The conditional macros are carefully defined to avoid introducing +extra whitespace (i.e., blank lines or blank characters). One side +effect exists--- + + BEWARE: text following an `_if__' on the same line is + DISCARDED even if the condition is true; text + following a `_fi__' on the same line is also + always discarded. + +The recommended convention is to always place _if__ and _fi__ on a +line by themselves. This will also aid the human reader. TeX won't +care about the line breaks; as for info, you may want to insert calls +to `@refill' at the end of paragraphs containing conditionalized text, +where you don't want line breaks separating unconditional from +conditional text. info formatting will then give you nice looking +paragraphs in the info file. + +Nesting: conditionals are designed to nest, in the following way: +*nothing* is output between an outer pair of false conditionals, even +if there are true conditionals inside. A false conditional "defeats" +all conditionals within it. The counter _IF_FS__ is used to +implement this; kindly avoid redefining it directly. + +_define__(<_IF_FS__>,<0>) +_define__( + <_pushf__>, + <_define__(<_IF_FS__>, + _incr__(_IF_FS__))>) +_define__( + <_popf__>, + <_ifelse__(0,_IF_FS__, + <<>_dnl__<>>, + <_define__(<_IF_FS__>,_decr__(_IF_FS__))>)>) + +_define__( + <_if__>, + <_ifelse__(1,_eval__( ($1) ), + <<>_dnl__<>>, + <_pushf__<>_divert__(-1)>)>) +_define__( + <_fi__>, + <_ifelse__(1,_eval__( ($1) ), + <<>_dnl__<>>, + <_popf__<>_ifelse__(0,_IF_FS__, + <_divert__<>_dnl__<>>,<>)>)>) + +D. CHAPTER/SECTION MACRO +In a parametrized manual, the heading level may need to be calculated; +for example, a manual that has a chapter on machine dependencies +should be conditionally structured as follows: + - IF the manual is configured for a SINGLE machine type, use +the chapter heading for that machine type, and run headings down +from there (top level for a particular machine is chapter, then within +that we have section, subsection etc); + - ELSE, if MANY machine types are described in the chapter, +use a generic chapter heading such as "@chapter Machine Dependencies", +use "section" for the top level description of EACH machine, and run +headings down from there (top level for a particular machine is +section, then within that we have subsection, subsubsection etc). + +The macro <_CHAPSEC__> is for this purpose: its argument is evaluated (so +you can construct expressions to express choices such as above), then +expands as follows: + 0: @chapter + 1: @section + 2: @subsection + 3: @subsubsection + ...and so on. + +_define__(<_CHAPSEC__>,<@_cs__(_eval__($1))>) +_define__(<_cs__>,<_ifelse__( + 0, $1, <chapter>, + 1, $1, <section>, + <sub<>_cs__(_eval__($1 - 1))>)>) + +_divert__<>_dnl__<> diff --git a/gas/doc/sparc.m4 b/gas/doc/sparc.m4 new file mode 100644 index 0000000..8cc6a3e --- /dev/null +++ b/gas/doc/sparc.m4 @@ -0,0 +1,5 @@ +_divert__(-1) +_define__(<_SPARC__>,<1>) +_define__(<_HOST__>,<SPARC>) +_define__(<_MACH_DEP__>,<SPARC Dependent>) +_divert__<>
\ No newline at end of file diff --git a/gas/doc/vax.m4 b/gas/doc/vax.m4 new file mode 100644 index 0000000..59cb2ab --- /dev/null +++ b/gas/doc/vax.m4 @@ -0,0 +1,5 @@ +_divert__(-1) +_define__(<_VAX__>,<1>) +_define__(<_HOST__>,<VAX>) +_define__(<_MACH_DEP__>,<VAX Dependent>) +_divert__<>
\ No newline at end of file diff --git a/gas/flonum-const.c b/gas/flonum-const.c new file mode 100755 index 0000000..25e7baf --- /dev/null +++ b/gas/flonum-const.c @@ -0,0 +1,159 @@ +/* flonum_const.c - Useful Flonum constants + Copyright (C) 1987, 1990, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* static const char rcsid[] = "$Id$"; */ + +#include "flonum.h" +/* JF: I added the last entry to this table, and I'm not + sure if its right or not. Could go either way. I wish + I really understood this stuff. */ + + +const int table_size_of_flonum_powers_of_ten = 11; + +static const LITTLENUM_TYPE zero[] = { 1 }; + +/***********************************************************************\ +* * +* Warning: the low order bits may be WRONG here. * +* I took this from a suspect bc(1) script. * +* "minus_X"[] is supposed to be 10^(2^-X) expressed in base 2^16. * +* The radix point is just AFTER the highest element of the [] * +* * +* Because bc rounds DOWN for printing (I think), the lowest * +* significance littlenums should probably have 1 added to them. * +* * +\***********************************************************************/ + +/* JF: If this equals 6553/(2^16)+39321/(2^32)+... it approaches .1 */ +static const LITTLENUM_TYPE minus_1 [] = { + 39321, 39321, 39321, 39321, 39321, 39321, 39321, 39321, 39321, 39321, + 39321, 39321, 39321, 39321, 39321, 39321, 39321, 39321, 39321, 6553 }; +static const LITTLENUM_TYPE plus_1 [] = { 10 }; + +/* JF: If this equals 655/(2^16) + 23592/(2^32) + ... it approaches .01 */ +static const LITTLENUM_TYPE minus_2 [] = { + 10485, 36700, 62914, 23592, 49807, 10485, 36700, 62914, 23592, 49807, + 10485, 36700, 62914, 23592, 49807, 10485, 36700, 62914, 23592, 655 }; +static const LITTLENUM_TYPE plus_2 [] = { 100 }; + +/* This approaches .0001 */ +static const LITTLENUM_TYPE minus_3 [] = { + 52533, 20027, 37329, 65116, 64067, 60397, 14784, 18979, 33659, 19503, + 2726, 9542, 629, 2202, 40475, 10590, 4299, 47815, 36280, 6 }; +static const LITTLENUM_TYPE plus_3 [] = { 10000 }; + +/* JF: this approaches 1e-8 */ +static const LITTLENUM_TYPE minus_4 [] = { + 22516, 49501, 54293, 19424, 60699, 6716, 24348, 22618, 23904, 21327, + 3919, 44703, 19149, 28803, 48959, 6259, 50273, 62237, 42 }; +/* This equals 1525 * 2^16 + 57600 */ +static const LITTLENUM_TYPE plus_4 [] = { 57600, 1525 }; + +/* This approaches 1e-16 */ +static const LITTLENUM_TYPE minus_5 [] = { + 22199, 45957, 17005, 26266, 10526, 16260, 55017, 35680, 40443, 19789, + 17356, 30195, 55905, 28426, 63010, 44197, 1844 }; +static const LITTLENUM_TYPE plus_5 [] = { 28609, 34546, 35 }; + +static const LITTLENUM_TYPE minus_6 [] = { + 30926, 26518, 13110, 43018, 54982, 48258, 24658, 15209, 63366, 11929, + 20069, 43857, 60487, 51 }; +static const LITTLENUM_TYPE plus_6 [] = { 61313, 34220, 16731, 11629, 1262 }; + +static const LITTLENUM_TYPE minus_7 [] = { + 29819, 14733, 21490, 40602, 31315, 65186, 2695 }; +static const LITTLENUM_TYPE plus_7 [] = { + 7937, 49002, 60772, 28216, 38893, 55975, 63988, 59711, 20227, 24 }; + +static const LITTLENUM_TYPE minus_8 [] = { + 45849, 19069, 18068, 36324, 37948, 48745, 10873, 64360, 15961, 20566, + 24178, 15922, 59427, 110 }; +static const LITTLENUM_TYPE plus_8 [] = { + 15873, 11925, 39177, 991, 14589, 19735, 25347, 65086, 53853, 938, + 37209, 47086, 33626, 23253, 32586, 42547, 9731, 59679, 590 }; + +static const LITTLENUM_TYPE minus_9 [] = { + 63601, 55221, 43562, 33661, 29067, 28203, 65417, 64352, 22462, 41110, + 12570, 28635, 23199, 50572, 28471, 27074, 46375, 64028, 13106, 63700, + 32698, 17493, 32420, 34382, 22750, 20681, 12300 }; +static const LITTLENUM_TYPE plus_9 [] = { + 63564, 61556, 29377, 54467, 18621, 28141, 36415, 61241, 47119, 30026, + 19740, 46002, 13541, 61413, 30480, 38664, 32205, 50593, 51112, 48904, + 48263, 43814, 286, 30826, 52813, 62575, 61390, 24540, 21495, 5 }; + +static const LITTLENUM_TYPE minus_10 [] = { + 50313, 34681, 1464, 25889, 19575, 41125, 17635, 4598, 49708, 13427, + 17287, 56115, 53783, 38255, 32415, 17778, 31596, 7557, 20951, 18477, + 40353, 1178, 44405, 11837, 11571, 50963, 15649, 11698, 40675, 2308, }; +static const LITTLENUM_TYPE plus_10[] = { +18520, 53764, 54535, 61910, 61962, 59843, 46270, 58053, 12473, 63785, + 2449, 43230, 50044, 47595, 10403, 35766, 32607, 1124, 24966, 35044, +25524, 23631, 18826, 14518, 58448, 14562, 49618, 5588, 25396, 28 }; + +static const LITTLENUM_TYPE minus_11 [] = { + 6223, 59909, 62437, 59960, 14652, 45336, 48800, 7647, 51962, 37982, + 60436, 58176, 26767, 8440, 9831, 48556, 20994, 14148, 6757, 17221, + 60624, 46129, 53210, 44085, 54016, 24259, 11232, 21229, 21313, 81, }; +static const LITTLENUM_TYPE plus_11 [] = { + 36159, 2055, 33615, 61362, 23581, 62454, 9748, 15275, 39284, 58636, + 16269, 42793, 47240, 45774, 50861, 48400, 9413, 40281, 4030, 9572, + 7984, 33038, 59522, 19450, 40593, 24486, 54320, 6661, 55766, 805, }; + +/* Shut up complaints about differing pointer types. They only differ + in the const attribute, but there isn't any easy way to do this + */ +#define X (LITTLENUM_TYPE *) + +const FLONUM_TYPE flonum_negative_powers_of_ten [] = { + {X zero, X zero, X zero, 0, '+'}, + {X minus_1, X minus_1 +19, X minus_1 + 19, -20, '+'}, + {X minus_2, X minus_2 +19, X minus_2 + 19, -20, '+'}, + {X minus_3, X minus_3 +19, X minus_3 + 19, -20, '+'}, + {X minus_4, X minus_4 +18, X minus_4 + 18, -20, '+'}, + {X minus_5, X minus_5 +16, X minus_5 + 16, -20, '+'}, + {X minus_6, X minus_6 +13, X minus_6 + 13, -20, '+'}, + {X minus_7, X minus_7 + 6, X minus_7 + 6, -20, '+'}, + {X minus_8, X minus_8 +13, X minus_8 + 13, -40, '+'}, + {X minus_9, X minus_9 +26, X minus_9 + 26, -80, '+'}, + {X minus_10, X minus_10+29, X minus_10 + 29,-136, '+'}, + {X minus_11, X minus_11+29, X minus_11 + 29,-242, '+'}, +}; + +const FLONUM_TYPE flonum_positive_powers_of_ten [] = { + {X zero, X zero, X zero, 0, '+'}, + {X plus_1, X plus_1 + 0, X plus_1 + 0, 0, '+'}, + {X plus_2, X plus_2 + 0, X plus_2 + 0, 0, '+'}, + {X plus_3, X plus_3 + 0, X plus_3 + 0, 0, '+'}, + {X plus_4, X plus_4 + 1, X plus_4 + 1, 0, '+'}, + {X plus_5, X plus_5 + 2, X plus_5 + 2, 1, '+'}, + {X plus_6, X plus_6 + 4, X plus_6 + 4, 2, '+'}, + {X plus_7, X plus_7 + 9, X plus_7 + 9, 4, '+'}, + {X plus_8, X plus_8 + 18, X plus_8 + 18, 8, '+'}, + {X plus_9, X plus_9 + 29, X plus_9 + 29, 24, '+'}, + {X plus_10, X plus_10 + 29, X plus_10 + 29, 77, '+'}, + {X plus_11, X plus_11 + 29, X plus_11 + 29, 183, '+'}, +}; + +#ifdef VMS +dummy1() +{ +} +#endif +/* end: flonum_const.c */ diff --git a/gas/hex-value.c b/gas/hex-value.c new file mode 100644 index 0000000..64420f5 --- /dev/null +++ b/gas/hex-value.c @@ -0,0 +1,57 @@ +/* hex_value.c - char=>radix-value - + Copyright (C) 1987, 1990, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* static const char rcsid[] = "$Id$"; */ + +/* + * Export: Hex_value[]. Converts digits to their radix-values. + * As distributed assumes 8 bits per char (256 entries) and ASCII. + */ + +#define __ (42) /* blatently illegal digit value */ + /* exceeds any normal radix */ +#if !defined(__STDC__) && !defined(const) +#define const /* empty */ +#endif +const char +hex_value [256] = { /* for fast ASCII -> binary */ + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, __, __, __, __, __, __, + __, 10, 11, 12, 13, 14, 15, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, 10, 11, 12, 13, 14, 15, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, + __, __, __, __, __, __, __, __, __, __, __, __, __, __, __, __ + }; + +#ifdef VMS +dummy2() +{ +} +#endif +/* end:hex_value.c */ diff --git a/gas/strstr.c b/gas/strstr.c new file mode 100644 index 0000000..9823249 --- /dev/null +++ b/gas/strstr.c @@ -0,0 +1,55 @@ +/* strstr - find first occurrence of wanted in s + Copyright (C) 1989, 1990, 1991 Free Software Foundation. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* static const char rcsid[] = "$Id$"; */ + + /* If your compiler is really ansi, then you don't need this. */ +#ifndef __STDC__ + +#define SIZET int + +#define NULL 0 + +#include <string.h> + +char * /* found string, or NULL if none */ +strstr(s, wanted) +char *s; +char *wanted; +{ + register char *scan; + register SIZET len; + register char firstc; + + /* + * The odd placement of the two tests is so "" is findable. + * Also, we inline the first char for speed. + * The ++ on scan has been moved down for optimization. + */ + firstc = *wanted; + len = strlen(wanted); + for (scan = s; *scan != firstc || strncmp(scan, wanted, len) != 0; ) + if (*scan++ == '\0') + return(NULL); + return(scan); +} /* strstr() */ + +#endif /* __STDC__ */ + +/* end of strstr.c */ diff --git a/gas/testscripts/doboth b/gas/testscripts/doboth new file mode 100755 index 0000000..a8c3358 --- /dev/null +++ b/gas/testscripts/doboth @@ -0,0 +1,20 @@ +#!/bin/sh +# $Id$ + +x=$1 ; shift +y=$1 ; shift + +rm tmp.0 > /dev/null 2>&1 +ln -s $x tmp.0 +$* tmp.0 > tmp.1 + +rm tmp.0 +ln -s $y tmp.0 +$* tmp.0 > tmp.2 + +rm tmp.0 + +diff -c tmp.1 tmp.2 +exit + +#eof diff --git a/gas/testscripts/doobjcmp b/gas/testscripts/doobjcmp new file mode 100755 index 0000000..9fbe46b --- /dev/null +++ b/gas/testscripts/doobjcmp @@ -0,0 +1,89 @@ +#!/bin/sh +# $Id$ +# compare two object files, in depth. + +x=$1 +y=$2 +BOTH="$1 $2" + + +# if they cmp, we're fine. +if (cmp $BOTH > /dev/null) +then + exit 0 +fi + +# otherwise, we must look closer. +if (doboth $BOTH size) +then + echo Sizes ok. +else + echo Sizes differ: + size $BOTH +# exit 1 +fi + +if (doboth $BOTH objdump +header) +then + echo Headers ok. +else + echo Header differences. +# exit 1 +fi + +if (doboth $BOTH objdump +text > /dev/null) +then + echo Text ok. +else + echo Text differences. +# doboth $BOTH objdump +text +# exit 1 +fi + +if (doboth $BOTH objdump +data > /dev/null) +then + echo Data ok. +else + echo Data differences. +# doboth $BOTH objdump +data +# exit 1 +fi + +if (doboth $BOTH objdump +symbols > /dev/null) +then + echo Symbols ok. +else + echo -n Symbol differences... + + if (doboth $BOTH dounsortsymbols) + then + echo but symbols are simply ordered differently. +# echo Now what to do about relocs'?' +# exit 1 + else + echo and symbols differ in content. + exit 1 + fi +fi + +# of course, if there were symbol diffs, then the reloc symbol indexes +# will be off. + +if (doboth $BOTH objdump -r > /dev/null) +then + echo Reloc ok. +else + echo -n Reloc differences... + + if (doboth $BOTH dounsortreloc) + then + echo but relocs are simply ordered differently. + else + echo and relocs differ in content. + exit 1 + fi +fi + +exit + +# eof diff --git a/gas/testscripts/dostriptest b/gas/testscripts/dostriptest new file mode 100755 index 0000000..4b89df8 --- /dev/null +++ b/gas/testscripts/dostriptest @@ -0,0 +1,15 @@ +#!/bin/sh +# $Id$ + +x=striptest.xx.$$ +y=striptest.yy.$$ + +cp $1 $x +strip $x +cp $2 $y +strip $y + +doobjcmp $x $y +exit + +#eof diff --git a/gas/testscripts/dotest b/gas/testscripts/dotest new file mode 100755 index 0000000..8c7a28c --- /dev/null +++ b/gas/testscripts/dotest @@ -0,0 +1,44 @@ +#!/bin/sh +# ad hoc debug tool +# $Id$ + +x=$1 +y=$2 + +xout=`basename $x`.xxx.$$ +yout=`basename $x`.yyy.$$ + +mkdir $xout +mkdir $yout + +for i in *.s +do + echo Testing $i... + object=`basename $i .s`.o + $x $i -o $xout/$object + $y $i -o $yout/$object + +# if they cmp, we're ok. Otherwise we have to look closer. + + if (cmp $xout/$object $yout/$object) + then + echo $i is ok. + else + if (doobjcmp $xout/$object $yout/$object) + then + echo Not the same but objcmp ok. + else + exit 1 + fi + fi + + echo +done + +rm -rf $xout $yout + +exit 0 + +# EOF + + diff --git a/gas/testscripts/dounsortreloc b/gas/testscripts/dounsortreloc new file mode 100755 index 0000000..d8da0a9 --- /dev/null +++ b/gas/testscripts/dounsortreloc @@ -0,0 +1,9 @@ +#!/bin/sh +# $Id$ +# objdump the reloc table, but strip off the headings and reloc +# numbers and sort the result. Intended for use in comparing reloc +# tables that may not be in the same order. + +objdump +reloc +omit-relocation-numbers +omit-symbol-numbers $1 \ + | sort +#eof diff --git a/gas/testscripts/dounsortsymbols b/gas/testscripts/dounsortsymbols new file mode 100755 index 0000000..8fb6db3 --- /dev/null +++ b/gas/testscripts/dounsortsymbols @@ -0,0 +1,9 @@ +#!/bin/sh +# $Id$ +# objdump the symbol table, but strip off the headings and symbol +# numbers and sort the result. Intended for use in comparing symbol +# tables that may not be in the same order. + +objdump +symbols +omit-symbol-numbers $1 \ + | sort +#eof diff --git a/gas/xmalloc.c b/gas/xmalloc.c new file mode 100644 index 0000000..6602987 --- /dev/null +++ b/gas/xmalloc.c @@ -0,0 +1,71 @@ +/* xmalloc.c - get memory or bust + Copyright (C) 1987, 1990, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + +/* static const char rcsid[] = "$Id$"; */ + +/* +NAME + xmalloc() - get memory or bust +INDEX + xmalloc() uses malloc() + +SYNOPSIS + char * my_memory; + + my_memory = xmalloc(42); / * my_memory gets address of 42 chars * / + +DESCRIPTION + + Use xmalloc() as an "error-free" malloc(). It does almost the same job. + When it cannot honour your request for memory it BOMBS your program + with a "virtual memory exceeded" message. Malloc() returns NULL and + does not bomb your program. + +SEE ALSO + malloc() + +*/ +#include <stdio.h> + +#ifdef __STDC__ +#include <stdlib.h> +#else +#ifdef USG +#include <malloc.h> +#else + char * malloc(); +#endif /* USG */ +#endif /* __STDC__ */ + +#define error as_fatal + +char * xmalloc(n) + long n; +{ + char * retval; + void error(); + + if ((retval = malloc ((unsigned)n)) == NULL) + { + error("virtual memory exceeded"); + } + return (retval); +} + +/* end: xmalloc.c */ diff --git a/gas/xrealloc.c b/gas/xrealloc.c new file mode 100644 index 0000000..83d3ce6 --- /dev/null +++ b/gas/xrealloc.c @@ -0,0 +1,70 @@ +/* xrealloc.c -new memory or bust- + Copyright (C) 1987, 1990, 1991 Free Software Foundation, Inc. + +This file is part of GAS, the GNU Assembler. + +GAS is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 1, or (at your option) +any later version. + +GAS is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. + +You should have received a copy of the GNU General Public License +along with GAS; see the file COPYING. If not, write to +the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */ + + +/* static const char rcsid[] = "$Id$"; */ + +/* + +NAME + xrealloc () - get more memory or bust +INDEX + xrealloc () uses realloc () +SYNOPSIS + char *my_memory; + + my_memory = xrealloc (my_memory, 42); + / * my_memory gets (perhaps new) address of 42 chars * / + +DESCRIPTION + + Use xrealloc () as an "error-free" realloc ().It does almost the same + job. When it cannot honour your request for memory it BOMBS your + program with a "virtual memory exceeded" message. Realloc() returns + NULL and does not bomb your program. + +SEE ALSO + realloc () +*/ + +#ifdef __STDC__ +#include <stdlib.h> +#else +#ifdef USG +#include <malloc.h> +#else + char *realloc (); +#endif /* USG */ +#endif /* __STDC__ */ + +#define error as_fatal + +char * +xrealloc (ptr, n) +register char *ptr; +long n; +{ + void error(); + + if ((ptr = realloc (ptr, (unsigned)n)) == 0) + error ("virtual memory exceeded"); + return (ptr); +} + +/* end: xrealloc.c */ |