blob: 8b0d84564087766838113fb161334f41d8a3ef0d [file] [log] [blame]
hbono@chromium.org8c354912012-11-14 05:27:15 +00001'\" t
ajwong@chromium.org45afe012009-10-23 19:20:20 +00002.\" Title: yasm
3.\" Author: Peter Johnson <peter@tortall.net>
hbono@chromium.org8c354912012-11-14 05:27:15 +00004.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
ajwong@chromium.org45afe012009-10-23 19:20:20 +00005.\" Date: April 2007
6.\" Manual: The Yasm Modular Assembler
7.\" Source: Yasm
hbono@chromium.org8c354912012-11-14 05:27:15 +00008.\" Language: English
ajwong@chromium.org45afe012009-10-23 19:20:20 +00009.\"
10.TH "YASM" "1" "April 2007" "Yasm" "The Yasm Modular Assembler"
hbono@chromium.org8c354912012-11-14 05:27:15 +000011.\" -----------------------------------------------------------------
12.\" * set default formatting
13.\" -----------------------------------------------------------------
ajwong@chromium.org45afe012009-10-23 19:20:20 +000014.\" disable hyphenation
15.nh
16.\" disable justification (adjust text to left margin only)
17.ad l
hbono@chromium.org8c354912012-11-14 05:27:15 +000018.\" -----------------------------------------------------------------
19.\" * MAIN CONTENT STARTS HERE *
20.\" -----------------------------------------------------------------
ajwong@chromium.org45afe012009-10-23 19:20:20 +000021.SH "NAME"
22yasm \- The Yasm Modular Assembler
23.SH "SYNOPSIS"
hbono@chromium.org8c354912012-11-14 05:27:15 +000024.HP \w'\fByasm\fR\ 'u
ajwong@chromium.org45afe012009-10-23 19:20:20 +000025\fByasm\fR [\fB\-f\ \fR\fB\fIformat\fR\fR] [\fB\-o\ \fR\fB\fIoutfile\fR\fR] [\fB\fIother\ options\fR\fR...] {\fIinfile\fR}
hbono@chromium.org8c354912012-11-14 05:27:15 +000026.HP \w'\fByasm\fR\ 'u
ajwong@chromium.org45afe012009-10-23 19:20:20 +000027\fByasm\fR \fB\-h\fR
28.SH "DESCRIPTION"
29.PP
30The Yasm Modular Assembler is a portable, retargetable assembler written under the
31\(lqnew\(rq
hbono@chromium.org8c354912012-11-14 05:27:15 +000032(2 or 3 clause) BSD license\&. Yasm currently supports the x86 and AMD64 instruction sets, accepts NASM and GAS assembler syntaxes, outputs binary, ELF32, ELF64, COFF, Win32, and Win64 object formats, and generates source debugging information in STABS, DWARF 2, and CodeView 8 formats\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +000033.PP
34YASM consists of the
35\fByasm\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +000036command, libyasm, the core backend library, and a large number of modules\&. Currently, libyasm and the loadable modules are statically built into the
ajwong@chromium.org45afe012009-10-23 19:20:20 +000037\fByasm\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +000038executable\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +000039.PP
40The
41\fByasm\fR
42command assembles the file infile and directs output to the file
43\fIoutfile\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +000044if specified\&. If
ajwong@chromium.org45afe012009-10-23 19:20:20 +000045\fIoutfile\fR
46is not specified,
47\fByasm\fR
48will derive a default output file name from the name of its input file, usually by appending
hbono@chromium.org8c354912012-11-14 05:27:15 +000049\&.o
ajwong@chromium.org45afe012009-10-23 19:20:20 +000050or
hbono@chromium.org8c354912012-11-14 05:27:15 +000051\&.obj, or by removing all extensions for a raw binary file\&. Failing that, the output file name will be
52yasm\&.out\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +000053.PP
54If called with an
55\fIinfile\fR
56of
57\(lq\-\(rq,
58\fByasm\fR
59assembles the standard input and directs output to the file
60\fIoutfile\fR, or
hbono@chromium.org8c354912012-11-14 05:27:15 +000061yasm\&.out
ajwong@chromium.org45afe012009-10-23 19:20:20 +000062if no
63\fIoutfile\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +000064is specified\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +000065.SH "OPTIONS"
66.PP
hbono@chromium.org8c354912012-11-14 05:27:15 +000067Many options may be given in one of two forms: either a dash followed by a single letter, or two dashes followed by a long option name\&. Options are listed in alphabetical order\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +000068.SS "General Options"
69.PP
70\fB\-a \fR\fB\fIarch\fR\fR or \fB\-\-arch=\fR\fB\fIarch\fR\fR: Select target architecture
71.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +000072Selects the target architecture\&. The default architecture is
73\(lqx86\(rq, which supports both the IA\-32 and derivatives and AMD64 instruction sets\&. To print a list of available architectures to standard output, use
ajwong@chromium.org45afe012009-10-23 19:20:20 +000074\(lqhelp\(rq
75as
hbono@chromium.org8c354912012-11-14 05:27:15 +000076\fIarch\fR\&. See
ajwong@chromium.org45afe012009-10-23 19:20:20 +000077\fByasm_arch\fR(7)
hbono@chromium.org8c354912012-11-14 05:27:15 +000078for a list of supported architectures\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +000079.RE
80.PP
81\fB\-f \fR\fB\fIformat\fR\fR or \fB\-\-oformat=\fR\fB\fIformat\fR\fR: Select object format
82.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +000083Selects the output object format\&. The default object format is
84\(lqbin\(rq, which is a flat format binary with no relocation\&. To print a list of available object formats to standard output, use
ajwong@chromium.org45afe012009-10-23 19:20:20 +000085\(lqhelp\(rq
86as
hbono@chromium.org8c354912012-11-14 05:27:15 +000087\fIformat\fR\&. See
ajwong@chromium.org45afe012009-10-23 19:20:20 +000088\fByasm_objfmts\fR(7)
hbono@chromium.org8c354912012-11-14 05:27:15 +000089for a list of supported object formats\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +000090.RE
91.PP
92\fB\-g \fR\fB\fIdebug\fR\fR or \fB\-\-dformat=\fR\fB\fIdebug\fR\fR: Select debugging format
93.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +000094Selects the debugging format for debug information\&. Debugging information can be used by a debugger to associate executable code back to the source file or get data structure and type information\&. Available debug formats vary between different object formats;
ajwong@chromium.org45afe012009-10-23 19:20:20 +000095\fByasm\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +000096will error when an invalid combination is selected\&. The default object format is selected by the object format\&. To print a list of available debugging formats to standard output, use
ajwong@chromium.org45afe012009-10-23 19:20:20 +000097\(lqhelp\(rq
98as
hbono@chromium.org8c354912012-11-14 05:27:15 +000099\fIdebug\fR\&. See
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000100\fByasm_dbgfmts\fR(7)
hbono@chromium.org8c354912012-11-14 05:27:15 +0000101for a list of supported debugging formats\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000102.RE
103.PP
104\fB\-L \fR\fB\fIlist\fR\fR or \fB\-\-lformat=\fR\fB\fIlist\fR\fR: Select list file format
105.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000106Selects the format/style of the output list file\&. List files typically intermix the original source with the machine code generated by the assembler\&. The default list format is
107\(lqnasm\(rq, which mimics the NASM list file format\&. To print a list of available list file formats to standard output, use
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000108\(lqhelp\(rq
109as
hbono@chromium.org8c354912012-11-14 05:27:15 +0000110\fIlist\fR\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000111.RE
112.PP
113\fB\-l \fR\fB\fIlistfile\fR\fR or \fB\-\-list=\fR\fB\fIlistfile\fR\fR: Specify list filename
114.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000115Specifies the name of the output list file\&. If this option is not used, no list file is generated\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000116.RE
117.PP
118\fB\-m \fR\fB\fImachine\fR\fR or \fB\-\-machine=\fR\fB\fImachine\fR\fR: Select target machine architecture
119.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000120Selects the target machine architecture\&. Essentially a subtype of the selected architecture, the machine type selects between major subsets of an architecture\&. For example, for the
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000121\(lqx86\(rq
122architecture, the two available machines are
123\(lqx86\(rq, which is used for the IA\-32 and derivative 32\-bit instruction set, and
hbono@chromium.org8c354912012-11-14 05:27:15 +0000124\(lqamd64\(rq, which is used for the 64\-bit instruction set\&. This differentiation is required to generate the proper object file for relocatable object formats such as COFF and ELF\&. To print a list of available machines for a given architecture to standard output, use
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000125\(lqhelp\(rq
126as
127\fImachine\fR
128and the given architecture using
hbono@chromium.org8c354912012-11-14 05:27:15 +0000129\fB\-a \fR\fB\fIarch\fR\fR\&. See
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000130\fByasm_arch\fR(7)
hbono@chromium.org8c354912012-11-14 05:27:15 +0000131for more details\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000132.RE
133.PP
134\fB\-o \fR\fB\fIfilename\fR\fR or \fB\-\-objfile=\fR\fB\fIfilename\fR\fR: Specify object filename
135.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000136Specifies the name of the output file, overriding any default name generated by Yasm\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000137.RE
138.PP
139\fB\-p \fR\fB\fIparser\fR\fR or \fB\-\-parser=\fR\fB\fIparser\fR\fR: Select parser
140.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000141Selects the parser (the assembler syntax)\&. The default parser is
142\(lqnasm\(rq, which emulates the syntax of NASM, the Netwide Assembler\&. Another available parser is
143\(lqgas\(rq, which emulates the syntax of GNU AS\&. To print a list of available parsers to standard output, use
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000144\(lqhelp\(rq
145as
hbono@chromium.org8c354912012-11-14 05:27:15 +0000146\fIparser\fR\&. See
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000147\fByasm_parsers\fR(7)
hbono@chromium.org8c354912012-11-14 05:27:15 +0000148for a list of supported parsers\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000149.RE
150.PP
151\fB\-r \fR\fB\fIpreproc\fR\fR or \fB\-\-preproc=\fR\fB\fIpreproc\fR\fR: Select preprocessor
152.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000153Selects the preprocessor to use on the input file before passing it to the parser\&. Preprocessors often provide macro functionality that is not included in the main parser\&. The default preprocessor is
154\(lqnasm\(rq, which is an imported version of the actual NASM preprocessor\&. A
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000155\(lqraw\(rq
hbono@chromium.org8c354912012-11-14 05:27:15 +0000156preprocessor is also available, which simply skips the preprocessing step, passing the input file directly to the parser\&. To print a list of available preprocessors to standard output, use
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000157\(lqhelp\(rq
158as
hbono@chromium.org8c354912012-11-14 05:27:15 +0000159\fIpreproc\fR\&.
160.RE
161.PP
162\fB\-h\fR or \fB\-\-help\fR: Print a summary of options
163.RS 4
164Prints a summary of invocation options\&. All other options are ignored, and no output file is generated\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000165.RE
166.PP
167\fB\-\-version\fR: Get the Yasm version
168.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000169This option causes Yasm to prints the version number of Yasm as well as a license summary to standard output\&. All other options are ignored, and no output file is generated\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000170.RE
171.SS "Warning Options"
172.PP
173\fB\-W\fR
174options have two contrary forms:
175\fB\-W\fR\fB\fIname\fR\fR
176and
hbono@chromium.org8c354912012-11-14 05:27:15 +0000177\fB\-Wno\-\fR\fB\fIname\fR\fR\&. Only the non\-default forms are shown here\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000178.PP
179The warning options are handled in the order given on the command line, so if
180\fB\-w\fR
181is followed by
182\fB\-Worphan\-labels\fR, all warnings are turned off
183\fIexcept\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +0000184for orphan\-labels\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000185.PP
186\fB\-w\fR: Inhibit all warning messages
187.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000188This option causes Yasm to inhibit all warning messages\&. As discussed above, this option may be followed by other options to re\-enable specified warnings\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000189.RE
190.PP
191\fB\-Werror\fR: Treat warnings as errors
192.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000193This option causes Yasm to treat all warnings as errors\&. Normally warnings do not prevent an object file from being generated and do not result in a failure exit status from
194\fByasm\fR, whereas errors do\&. This option makes warnings equivalent to errors in terms of this behavior\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000195.RE
196.PP
197\fB\-Wno\-unrecognized\-char\fR: Do not warn on unrecognized input characters
198.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000199Causes Yasm to not warn on unrecognized characters found in the input\&. Normally Yasm will generate a warning for any non\-ASCII character found in the input file\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000200.RE
201.PP
202\fB\-Worphan\-labels\fR: Warn on labels lacking a trailing option
203.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000204When using the NASM\-compatible parser, causes Yasm to warn about labels found alone on a line without a trailing colon\&. While these are legal labels in NASM syntax, they may be unintentional, due to typos or macro definition ordering\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000205.RE
206.PP
207\fB\-X \fR\fB\fIstyle\fR\fR: Change error/warning reporting style
208.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000209Selects a specific output style for error and warning messages\&. The default is
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000210\(lqgnu\(rq
211style, which mimics the output of
hbono@chromium.org8c354912012-11-14 05:27:15 +0000212\fBgcc\fR\&. The
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000213\(lqvc\(rq
hbono@chromium.org8c354912012-11-14 05:27:15 +0000214style is also available, which mimics the output of Microsoft\'s Visual C++ compiler\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000215.sp
216This option is available so that Yasm integrates more naturally into IDE environments such as
217Visual Studio
218or
hbono@chromium.org8c354912012-11-14 05:27:15 +0000219Emacs, allowing the IDE to correctly recognize the error/warning message as such and link back to the offending line of source code\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000220.RE
221.SS "Preprocessor Options"
222.PP
223While these preprocessor options theoretically will affect any preprocessor, the only preprocessor currently in Yasm is the
224\(lqnasm\(rq
hbono@chromium.org8c354912012-11-14 05:27:15 +0000225preprocessor\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000226.PP
227\fB\-D \fR\fB\fImacro[=value]\fR\fR: Pre\-define a macro
228.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000229Pre\-defines a single\-line macro\&. The value is optional (if no value is given, the macro is still defined, but to an empty value)\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000230.RE
231.PP
232\fB\-e\fR or \fB\-\-preproc\-only\fR: Only preprocess
233.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000234Stops assembly after the preprocessing stage; preprocessed output is sent to the specified output name or, if no output name is specified, the standard output\&. No object file is produced\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000235.RE
236.PP
237\fB\-I \fR\fB\fIpath\fR\fR: Add include file path
238.RS 4
239Adds directory
240\fIpath\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +0000241to the search path for include files\&. The search path defaults to only including the directory in which the source file resides\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000242.RE
243.PP
244\fB\-P \fR\fB\fIfilename\fR\fR: Pre\-include a file
245.RS 4
246Pre\-includes file
247\fIfilename\fR, making it look as though
248\fIfilename\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +0000249was prepended to the input\&. Can be useful for prepending multi\-line macros that the
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000250\fB\-D\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +0000251can\'t support\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000252.RE
253.PP
254\fB\-U \fR\fB\fImacro\fR\fR: Undefine a macro
255.RS 4
256Undefines a single\-line macro (may be either a built\-in macro or one defined earlier in the command line with
hbono@chromium.org8c354912012-11-14 05:27:15 +0000257\fB\-D\fR\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000258.RE
259.SH "EXAMPLES"
260.PP
261To assemble NASM syntax, 32\-bit x86 source
hbono@chromium.org8c354912012-11-14 05:27:15 +0000262source\&.asm
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000263into ELF file
hbono@chromium.org8c354912012-11-14 05:27:15 +0000264source\&.o, warning on orphan labels:
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000265.sp
hbono@chromium.org8c354912012-11-14 05:27:15 +0000266.if n \{\
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000267.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000268.\}
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000269.nf
hbono@chromium.org8c354912012-11-14 05:27:15 +0000270yasm \-f elf32 \-Worphan\-labels source\&.asm
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000271.fi
hbono@chromium.org8c354912012-11-14 05:27:15 +0000272.if n \{\
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000273.RE
hbono@chromium.org8c354912012-11-14 05:27:15 +0000274.\}
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000275.PP
276To assemble NASM syntax AMD64 source
hbono@chromium.org8c354912012-11-14 05:27:15 +0000277x\&.asm
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000278into Win64 file
hbono@chromium.org8c354912012-11-14 05:27:15 +0000279object\&.obj:
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000280.sp
hbono@chromium.org8c354912012-11-14 05:27:15 +0000281.if n \{\
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000282.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000283.\}
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000284.nf
hbono@chromium.org8c354912012-11-14 05:27:15 +0000285yasm \-f win64 \-o object\&.obj x\&.asm
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000286.fi
hbono@chromium.org8c354912012-11-14 05:27:15 +0000287.if n \{\
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000288.RE
hbono@chromium.org8c354912012-11-14 05:27:15 +0000289.\}
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000290.PP
291To assemble already preprocessed NASM syntax x86 source
hbono@chromium.org8c354912012-11-14 05:27:15 +0000292y\&.asm
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000293into flat binary file
hbono@chromium.org8c354912012-11-14 05:27:15 +0000294y\&.com:
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000295.sp
hbono@chromium.org8c354912012-11-14 05:27:15 +0000296.if n \{\
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000297.RS 4
hbono@chromium.org8c354912012-11-14 05:27:15 +0000298.\}
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000299.nf
hbono@chromium.org8c354912012-11-14 05:27:15 +0000300yasm \-f bin \-r raw \-o y\&.com y\&.asm
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000301.fi
hbono@chromium.org8c354912012-11-14 05:27:15 +0000302.if n \{\
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000303.RE
hbono@chromium.org8c354912012-11-14 05:27:15 +0000304.\}
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000305.SH "DIAGNOSTICS"
306.PP
307The
308\fByasm\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +0000309command exits 0 on success, and nonzero if an error occurs\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000310.SH "COMPATIBILITY"
311.PP
hbono@chromium.org8c354912012-11-14 05:27:15 +0000312Yasm\'s NASM parser and preprocessor, while they strive to be as compatible as possible with NASM, have a few incompatibilities due to YASM\'s different internal structure\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000313.PP
hbono@chromium.org8c354912012-11-14 05:27:15 +0000314Yasm\'s GAS parser and preprocessor are missing a number of features present in GNU AS\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000315.SH "RESTRICTIONS"
316.PP
hbono@chromium.org8c354912012-11-14 05:27:15 +0000317As object files are often architecture and machine dependent, not all combinations of object formats, architectures, and machines are legal; trying to use an invalid combination will result in an error\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000318.PP
hbono@chromium.org8c354912012-11-14 05:27:15 +0000319There is no support for symbol maps\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000320.SH "SEE ALSO"
321.PP
322\fByasm_arch\fR(7),
323\fByasm_dbgfmts\fR(7),
324\fByasm_objfmts\fR(7),
325\fByasm_parsers\fR(7)
326.PP
327Related tools:
328\fBas\fR(1),
329\fBld\fR(1),
330\fBnasm\fR(1)
331.SH "BUGS"
332.PP
333When using the
334\(lqx86\(rq
335architecture, it is overly easy to generate AMD64 code (using the
336\fBBITS 64\fR
337directive) and generate a 32\-bit object file (by failing to specify
338\fB\-m amd64\fR
hbono@chromium.org8c354912012-11-14 05:27:15 +0000339or selecting a 64\-bit object format such as ELF64 on the command line)\&.
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000340.SH "AUTHOR"
341.PP
hbono@chromium.org8c354912012-11-14 05:27:15 +0000342\fBPeter Johnson\fR <\&peter@tortall\&.net\&>
343.RS 4
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000344Author.
hbono@chromium.org8c354912012-11-14 05:27:15 +0000345.RE
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000346.SH "COPYRIGHT"
hbono@chromium.org8c354912012-11-14 05:27:15 +0000347.br
ajwong@chromium.org45afe012009-10-23 19:20:20 +0000348Copyright \(co 2004, 2005, 2006, 2007 Peter Johnson
349.br