as_en.html

万能汇编工具

than providing a dozen of precompiled binaries for machines I
sometimes only have limited access to...
<P>
People who have read this enumeration up to this point will notice       
that world's best-selling operating system coming from Redmont is
missing in this enumeration. People who know me personally will know
that I do not regard Windows to be a pat solution (regardless if its
3.X, 95, or NT). Frankly said, I am a 'windows hater'. A large number
of people will now regard this to be somewhere between obsolete and
ridiculous, and they will tell me that I withhold AS from a large
part of potential users, but they will have to live with it: I
primarily continue to improve AS because I have fun doing it; AS is a
non-commercial project and I therefore take the freedom not to look
at potential market shares. I select platforms for me where I have
fun programming, and I definitely do not have any fun when
programming for Windows! By the way, there was a time when I had to
write Windows programs so I do not simply jabber without having an
idea what I am talking about. If someone wants to port AS into this
direction, I will not stand in his way, but (s)he should not expect
anything more from me than providing sources (which is why (s)he will
have to deal with questions like 'why does AS not work any more after
I changed the JUNK-CAD 18.53 registry entry from upper to lower
case?').
<P>

<H1><A NAME="sect_2_">2. Assembler Usage</A></H1>
<P>
<BLOCKQUOTE>
<DIV ALIGN=LEFT>
    <I> Scotty: Captain, we din' can reference it!<BR>
    Kirk: Analysis, Mr. Spock?<BR>
    Spock: Captain, it doesn't appear in the symbol table.<BR>
    Kirk: Then it's of external origin?<BR>
    Spock: Affirmative.<BR>
    Kirk: Mr. Sulu, go to pass two.<BR>
    Sulu: Aye aye, sir, going to pass two.<BR>
    </I>
</DIV>
</BLOCKQUOTE>
<P>

<H2><A NAME="sect_2_1_">2.1. Hardware Requirements</A></H2>
<P>
The hardware requirements of AS vary substantially from version to
version:
<P>
The DOS version will principally run on any IBM-compatible PC,           
ranging from a PC/XT with 4-dot-little megahertz up to a Pentium.
However, similar to other programs, the fun using AS increases the
better your hardware is. An XT user without a hard drive will
probably have significant trouble placing the overlay file on a
floppy because it is larger than 500 Kbytes...the PC should therefore
have at least a hard drive, allowing acceptable loading times. AS is
not very advanced in its main memory needs: the program itself
allocates less than 300 Kbytes main memory, AS should therefore work
on machines with at least 512 Kbytes of memory.
<P>
The version of AS compiled for the DOS Protected Mode Interface          
(DPMI) requires at least 1 Mbyte of free extended memory. A total
memory capacity of at least 2 Mbytes is therefore the absolute
minimum given one does not have other tools in the XMS (like disk
caches, RAM disks, or a hi-loaded DOS); the needs will rise then
appropriately. If one uses the DPMI version in a DOS box of OS/2, one
has to assure that DPMI has been enabled via the box's DOS settings
(set to<TT> on</TT> or<TT> auto</TT>) and that a sufficient amount of
XMS memory has been assigned to the box. The virtual memory
management of OS/2 will free you from thinking about the amount of
free real memory.
<P>
The hardware requirements of the OS/2 version mainly result from the     
needs of the underlying operating system, i.e. at minimum an 80386SX
processor, 8 Mbytes of RAM (resp. 4 Mbytes without the graphical user
interface) and 100..150 Mbytes of hard disk space. AS2 is only a
16-bit application and therefore it should also work on older OS/2
versions (thereby reducing the processor needs to at least an 80286
processor); I had however no chance to test this.
<P>
The C version of AS is delivered as source code and therefore            
requires a UNIX or OS/2 system equipped with a C compiler. The
compiler has to fulfill the ANSI standard (GNU-C for example is
ANSI-compliant). You can look up in the<TT> README</TT> file whether
your UNIX system has already been tested so that the necessary
definitions have been made. You should reserve about 15 Mbytes of
free hard disk space for compilation; this value (and the amount
needed after compilation to store the compiled programs) strongly
differs from system to system, so you should take this value only as
a rough approximation.
<P>

<H2><A NAME="sect_2_2_">2.2. Delivery</A></H2>
<P>
Principally, you can obtain AS in one of two forms: as a<EM>
binary</EM> or a<EM> source</EM> distribution. In case of a binary
distribution, one gets AS, the accomanying tools and auxiliary files
readily compiled, so you can immediately start to use it after
unpacking the archive to the desired destination on your hard drive.
Binary distibutions are made for widespread platforms, where either
the majority of users does not have a compiler or the compilation is
tricky (currently, this includes DOS and OS/2). A source distribution
in contrast contains the complete set of C sources to generate AS; it
is ultimately a snapshot of the source tree I use for development on
AS. The generation of AS from the sources and their structure is
described in detail in appendix <A HREF="#ref_ChapSource">I</A>,
which is why at this place, only the contents and installation of a
binary distribution will be described:
<P>
The contents of the archive is separated into several subdirectories,
therefore you get a directory subtree immediately after unpacking
without having to sort out things manually. The individual
directories contain the following groups of files:
<UL>
<LI> <TT> BIN</TT>: executable programs, text resources;</LI>
<LI> <TT> INCLUDE</TT>: include files for assembler programs, e.g.
    register definitions or standard macros;</LI>
<LI> <TT> MAN</TT>: quick references for the individual programs in Unix
    'man' format.</LI>
</UL>
A list of the files found in every binary distribution is given in
tables <A HREF="#ref_TabCommonPackageList1">2.1</A> to <A
HREF="#ref_TabCommonPackageList3">2.3</A>. In case a file listed in
one of these (or the following) tables is missing, someone took a nap
during copying (probably me)...
<P>

<CENTER>
<P><CENTER><TABLE SUMMARY="No Summary" BORDER=1 CELLPADDING=5>
<TR ALIGN=LEFT>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>File</TH>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>function</TH>
</TR>
<TR ALIGN=LEFT>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT><B> Directory BIN</B></TD>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT></TD>
</TR>
<TR ALIGN=LEFT>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>AS.EXE<BR>
PLIST.EXE<BR>
PBIND.EXE<BR>
P2HEX.EXE<BR>
P2BIN.EXE<BR>
AS.MSG<BR>
PLIST.MSG<BR>
PBIND.MSG<BR>
P2HEX.MSG<BR>
P2BIN.MSG<BR>
TOOLS.MSG<BR>
CMDARG.MSG<BR>
IOERRS.MSG</TH>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>executable of assembler<BR>
lists contents of code files<BR>
merges code files<BR>
converts code files to hex files<BR>
converts code files to binary files<BR>
text resources for AS<BR>
text resources for PLIST<BR>
text resources for PBIND<BR>
text resources for P2HEX<BR>
text resources for P2BIN<BR>
common text resources for all tools<BR>
common text resources for all programs<BR>
</TH>
</TR>
<TR ALIGN=LEFT>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT><B> Directory DOC</B></TD>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT></TD>
</TR>
<TR ALIGN=LEFT>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>AS_DE.DOC<BR>
AS_DE.HTML<BR>
AS_DE.TEX<BR>
AS_EN.DOC<BR>
AS_EN.HTML<BR>
AS_EN.TEX</TH>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>german documentation, ASCII format<BR>
german documentation, HTML format<BR>
german documentation, LaTeX format<BR>
english documentation, ASCII format<BR>
english documentation, HTML format<BR>
english documentation, LaTeX format</TH>
</TR>
<TR ALIGN=LEFT>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT><B> Directory INCLUDE</B></TD>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT></TD>
</TR>
<TR ALIGN=LEFT>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT>BITFUNCS.INC<BR>
CTYPE.INC<BR>
<BR>
80C50X.INC<BR>
80C552.INC<BR>
H8_3048.INC<BR>
REG166.INC<BR>
REG251.INC<BR>
REG29K.INC</TD>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT>functions for bit manipulation<BR>
functions for classification of<BR>
characters<BR>
register addresses SAB C50x<BR>
register addresses 80C552<BR>
register addresses H8/3048<BR>
addresses and instruction macros 80C166/167<BR>
addresses and bits 80C251<BR>
peripheral addresses AMD 2924x</TD>
</TR>
</TABLE></CENTER>
</CENTER>
<P><CENTER>Table 2.1: Standard Contents of a Binary Distribution - Part 1<A
           NAME="ref_TabCommonPackageList1"></A>
</CENTER><P>


<CENTER>
<P><CENTER><TABLE SUMMARY="No Summary" BORDER=1 CELLPADDING=5>
<TR ALIGN=LEFT>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>File</TH>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>Function</TH>
</TR>
<TR ALIGN=LEFT>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT><B> Directory INCLUDE</B></TD>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT></TD>
</TR>
<TR ALIGN=LEFT>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT>REG53X.INC<BR>
REG683XX.INC<BR>
REG7000.INC<BR>
REG78K0.INC<BR>
REG96.INC<BR>
REGACE.INC<BR>
REGAVR.INC<BR>
REGCOP8.INC<BR>
REGGP32.INC<BR>
REGHC12.INC<BR>
REGM16C.INC<BR>
REGMSP.INC<BR>
REGST9.INC<BR>
REGZ380.INC<BR>
STDDEF04.INC<BR>
STDDEF16.INC<BR>
<BR>
STDDEF17.INC<BR>
STDDEF18.INC<BR>
STDDEF2X.INC<BR>
STDDEF37.INC<BR>
STDDEF3X.INC<BR>
STDDEF47.INC<BR>
STDDEF51.INC<BR>
<BR>
STDDEF56K.INC<BR>
STDDEF5X.INC<BR>
STDDEF60.INC<BR>
<BR>
STDDEF62.INC<BR>
STDDEF75.INC</TD>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT>register addresses H8/53x<BR>
register addresses 68332/68340/68360<BR>
register addresses TMS70Cxx<BR>
register addresses 78K0<BR>
register addresses MCS-96<BR>
register addresses ACE<BR>
register and bit addresses AVR family<BR>
register addresses COP8<BR>
register addresses 68HC908GP32<BR>
register addresses 68HC12<BR>
register addresses Mitsubishi M16C<BR>
register addresses TI MSP430<BR>
register and Makrodefinitionen ST9<BR>
register addresses Z380<BR>
register addresses 6804<BR>
instruction macros and register addresses<BR>
PIC16C5x<BR>
register addresses PIC17C4x<BR>
register addresses PIC16C8x<BR>
register addresses TMS3202x<BR>
register and bit addresses TMS370xxx<BR>
peripheral addresses TMS320C3x<BR>
instruction macros TLCS-47<BR>
definition of SFRs and bits for<BR>
8051/8052/80515<BR>
register addresses DSP56000<BR>
peripheral addresses TMS320C5x<BR>
instruction macros and register addresses<BR>
PowerPC<BR>
register addresses and Makros ST6<BR>
register addresses 75K0</TD>
</TR>
</TABLE></CENTER>
</CENTER>
<P><CENTER>Table 2.2: Standard Contents of a Binary Distribution - Part 2<A
           NAME="ref_TabCommonPackageList2"></A>
</CENTER><P>


<CENTER>
<P><CENTER><TABLE SUMMARY="No Summary" BORDER=1 CELLPADDING=5>
<TR ALIGN=LEFT>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>File</TH>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>Function</TH>
</TR>
<TR ALIGN=LEFT>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT><B> Directory INCLUDE</B></TD>
<TD VALIGN=TOP NOWRAP ALIGN=LEFT></TD>
</TR>
<TR ALIGN=LEFT>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>STDDEF87.INC<BR>
STDDEF90.INC<BR>
STDDEF96.INC<BR>
STDDEFXA.INC<BR>
STDDEFZ8.INC</TH>
<TH VALIGN=TOP NOWRAP ALIGN=LEFT>register and memory addresses TLCS-870<BR>
register and memory addresses TLCS-90<BR>
register and memory addresses TLCS-900<BR>
SFR and bit addresses Philips XA<BR>
register addresses Z8 family</TH>