NASM汇编器指南：安装与使用

需积分: 10 36 浏览量更新于2024-08-01 收藏 687KB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"nasmdoc.pdf 是一份关于 NASM（Netwide Assembler）的详细文档，主要介绍了如何使用这款强大的开放源代码编译器。无论是在Windows还是Linux环境下，NASM都能出色地完成汇编语言的编译工作。用户可以从www.nasm.org下载NASM。此外，如果在Windows XP或WIN7系统中需要链接器，文档中也提到可以在此资源中找到alink.exe。NASM不仅是一个汇编器，还支持链接功能。文档版权属于1996年至2010年的NASM开发团队，并遵循在NASM归档文件中的"LICENSE"文件所规定的许可协议。" NASM是Netwide Assembler的简称，是一个功能强大的开源汇编器，版本为2.09。它不仅支持多种操作系统，如MS-DOS、Windows以及各种Unix变体，而且具有简洁的命令行语法，使得在不同平台上编译汇编程序变得简单易行。文档的主要内容分为多个章节，如： 1. 引言： - 1.1节介绍了NASM是什么，讨论了为何需要另一个汇编器，同时提到了软件的授权条件。 - 1.2节提供了联系信息，方便用户获取技术支持或进行交流。 - 1.3节详细阐述了安装NASM的步骤，包括在MS-DOS/Windows环境和Unix环境下的安装方法。 2. 运行NASM： - 2.1节详细解释了NASM的命令行语法，包括如何指定输出文件名（-o选项）、输出文件格式（-f选项）、生成列表文件（-l选项）、制作Makefile依赖项（-M、-MG、-MF、-MD、-MT选项）等，这些功能帮助开发者更好地管理和构建项目。通过这份文档，用户可以深入了解NASM的功能，学习如何有效地利用NASM进行汇编语言编程，无论是初学者还是有经验的开发者，都能从中获益。对于需要在不同操作系统下工作的开发者来说，NASM是一个不可或缺的工具，因为它提供了跨平台的兼容性和高效性。同时，文档提供的详细指令和选项解释，使得用户能够快速上手并充分利用NASM的强大功能。

资源详情

资源推荐

1.3.2 Installing NASM under Unix

Once you’ve obtained the Unix source archive for NASM, nasm−XXX.tar.gz (where XXX denotes the

version number of NASM contained in the archive), unpack it into a directory such as /usr/local/src.

The archive, when unpacked, will create its own subdirectory nasm−XXX.

NASM is an auto−configuring package: once you’ve unpacked it, cd to the directory it’s been unpacked into

and type ./configure. This shell script will find the best C compiler to use for building NASM and set up

Makefiles accordingly.

Once NASM has auto−configured, you can type make to build the nasm and ndisasm binaries, and then

make install to install them in /usr/local/bin and install the man pages nasm.1 and

ndisasm.1 in /usr/local/man/man1. Alternatively, you can give options such as −−prefix to the

configure script (see the file INSTALL for more details), or install the programs yourself.

NASM also comes with a set of utilities for handling the RDOFF custom object−file format, which are in the

rdoff subdirectory of the NASM archive. You can build these with make rdf and install them with

make rdf_install, if you want them.

Chapter 2: Running NASM

2.1 NASM Command−Line Syntax

To assemble a file, you issue a command of the form

nasm −f <format> <filename> [−o <output>]

For example,

nasm −f elf myfile.asm

will assemble myfile.asm into an ELF object file myfile.o. And

nasm −f bin myfile.asm −o myfile.com

will assemble myfile.asm into a raw binary file myfile.com.

To produce a listing file, with the hex codes output from NASM displayed on the left of the original sources,

use the −l option to give a listing file name, for example:

nasm −f coff myfile.asm −l myfile.lst

To get further usage instructions from NASM, try typing

nasm −h

As −hf, this will also list the available output file formats, and what they are.

If you use Linux but aren’t sure whether your system is a.out or ELF, type

file nasm

(in the directory in which you put the NASM binary when you installed it). If it says something like

nasm: ELF 32−bit LSB executable i386 (386 and up) Version 1

then your system is ELF, and you should use the option −f elf when you want NASM to produce Linux

object files. If it says

nasm: Linux/i386 demand−paged executable (QMAGIC)

or something similar, your system is a.out, and you should use −f aout instead (Linux a.out systems

have long been obsolete, and are rare these days.)

Like Unix compilers and assemblers, NASM is silent unless it goes wrong: you won’t see any output at all,

unless it gives error messages.

2.1.1 The −o Option: Specifying the Output File Name

NASM will normally choose the name of your output file for you; precisely how it does this is dependent on

the object file format. For Microsoft object file formats (obj, win32 and win64), it will remove the .asm

extension (or whatever extension you like to use – NASM doesn’t care) from your source file name and

substitute .obj. For Unix object file formats (aout, as86, coff, elf32, elf64, ieee, macho32 and

macho64) it will substitute .o. For dbg, rdf, ith and srec, it will use .dbg, .rdf, .ith and .srec,

respectively, and for the bin format it will simply remove the extension, so that myfile.asm produces the

output file myfile.

If the output file already exists, NASM will overwrite it, unless it has the same name as the input file, in

which case it will give a warning and use nasm.out as the output file name instead.

For situations in which this behaviour is unacceptable, NASM provides the −o command−line option, which

allows you to specify your desired output file name. You invoke −o by following it with the name you wish

for the output file, either with or without an intervening space. For example:

nasm −f bin program.asm −o program.com

nasm −f bin driver.asm −odriver.sys

Note that this is a small o, and is different from a capital O , which is used to specify the number of

optimisation passes required. See section 2.1.22.

2.1.2 The −f Option: Specifying the Output File Format

If you do not supply the −f option to NASM, it will choose an output file format for you itself. In the

distribution versions of NASM, the default is always bin; if you’ve compiled your own copy of NASM, you

can redefine OF_DEFAULT at compile time and choose what you want the default to be.

Like −o, the intervening space between −f and the output file format is optional; so −f elf and −felf are

both valid.

A complete list of the available output file formats can be given by issuing the command nasm −hf.

2.1.3 The −l Option: Generating a Listing File

If you supply the −l option to NASM, followed (with the usual optional space) by a file name, NASM will

generate a source−listing file for you, in which addresses and generated code are listed on the left, and the

actual source code, with expansions of multi−line macros (except those which specifically request no

expansion in source listings: see section 4.3.10) on the right. For example:

nasm −f elf myfile.asm −l myfile.lst

If a list file is selected, you may turn off listing for a section of your source with [list −], and turn it back

on with [list +], (the default, obviously). There is no "user form" (without the brackets). This can be used

to list only sections of interest, avoiding excessively long listings.

2.1.4 The −M Option: Generate Makefile Dependencies

This option can be used to generate makefile dependencies on stdout. This can be redirected to a file for

further processing. For example:

nasm −M myfile.asm > myfile.dep

2.1.5 The −MG Option: Generate Makefile Dependencies

This option can be used to generate makefile dependencies on stdout. This differs from the −M option in that if

a nonexisting file is encountered, it is assumed to be a generated file and is added to the dependency list

without a prefix.

2.1.6 The −MF Option: Set Makefile Dependency File

This option can be used with the −M or −MG options to send the output to a file, rather than to stdout. For

example:

nasm −M −MF myfile.dep myfile.asm

2.1.7 The −MD Option: Assemble and Generate Dependencies

The −MD option acts as the combination of the −M and −MF options (i.e. a filename has to be specified.)

However, unlike the −M or −MG options, −MD does not inhibit the normal operation of the assembler. Use this

to automatically generate updated dependencies with every assembly session. For example:

nasm −f elf −o myfile.o −MD myfile.dep myfile.asm

2.1.8 The −MT Option: Dependency Target Name

The −MT option can be used to override the default name of the dependency target. This is normally the same

as the output filename, specified by the −o option.

2.1.9 The −MQ Option: Dependency Target Name (Quoted)

The −MQ option acts as the −MT option, except it tries to quote characters that have special meaning in

Makefile syntax. This is not foolproof, as not all characters with special meaning are quotable in Make.

2.1.10 The −MP Option: Emit phony targets

When used with any of the dependency generation options, the −MP option causes NASM to emit a phony

target without dependencies for each header file. This prevents Make from complaining if a header file has

been removed.

2.1.11 The −F Option: Selecting a Debug Information Format

This option is used to select the format of the debug information emitted into the output file, to be used by a

debugger (or will be). Prior to version 2.03.01, the use of this switch did not enable output of the selected

debug info format. Use −g, see section 2.1.12, to enable output. Versions 2.03.01 and later automatically

enable −g if −F is specified.

A complete list of the available debug file formats for an output format can be seen by issuing the command

nasm −f <format> −y. Not all output formats currently support debugging output. See section 2.1.26.

This should not be confused with the −f dbg output format option which is not built into NASM by default.

For information on how to enable it when building from the sources, see section 7.14.

2.1.12 The −g Option: Enabling Debug Information.

This option can be used to generate debugging information in the specified format. See section 2.1.11. Using

−g without −F results in emitting debug info in the default format, if any, for the selected output format. If no

debug information is currently implemented in the selected output format, −g is silently ignored.

2.1.13 The −X Option: Selecting an Error Reporting Format

This option can be used to select an error reporting format for any error messages that might be produced by

NASM.

Currently, two error reporting formats may be selected. They are the −Xvc option and the −Xgnu option. The

GNU format is the default and looks like this:

filename.asm:65: error: specific error message

where filename.asm is the name of the source file in which the error was detected, 65 is the source file

line number on which the error was detected, error is the severity of the error (this could be warning),

and specific error message is a more detailed text message which should help pinpoint the exact

problem.

The other format, specified by −Xvc is the style used by Microsoft Visual C++ and some other programs. It

looks like this:

filename.asm(65) : error: specific error message

where the only difference is that the line number is in parentheses instead of being delimited by colons.

See also the Visual C++ output format, section 7.5.

2.1.14 The −Z Option: Send Errors to a File

Under MS−DOS it can be difficult (though there are ways) to redirect the standard−error output of a program

to a file. Since NASM usually produces its warning and error messages on stderr, this can make it hard to

capture the errors if (for example) you want to load them into an editor.

NASM therefore provides the −Z option, taking a filename argument which causes errors to be sent to the

specified files rather than standard error. Therefore you can redirect the errors into a file by typing

nasm −Z myfile.err −f obj myfile.asm

In earlier versions of NASM, this option was called −E, but it was changed since −E is an option

conventionally used for preprocessing only, with disastrous results. See section 2.1.20.

2.1.15 The −s Option: Send Errors to stdout

The −s option redirects error messages to stdout rather than stderr, so it can be redirected under

MS−DOS. To assemble the file myfile.asm and pipe its output to the more program, you can type:

nasm −s −f obj myfile.asm | more

See also the −Z option, section 2.1.14.

2.1.16 The −i Option: Include File Search Directories

When NASM sees the %include or %pathsearch directive in a source file (see section 4.6.1, section

4.6.2 or section 3.2.3), it will search for the given file not only in the current directory, but also in any

directories specified on the command line by the use of the −i option. Therefore you can include files from a

macro library, for example, by typing

nasm −ic:\macrolib\ −f obj myfile.asm

(As usual, a space between −i and the path name is allowed, and optional).

NASM, in the interests of complete source−code portability, does not understand the file naming conventions

of the OS it is running on; the string you provide as an argument to the −i option will be prepended exactly as

written to the name of the include file. Therefore the trailing backslash in the above example is necessary.

Under Unix, a trailing forward slash is similarly necessary.

(You can use this to your advantage, if you’re really perverse, by noting that the option −ifoo will cause

%include "bar.i" to search for the file foobar.i...)

If you want to define a standard include search path, similar to /usr/include on Unix systems, you

should place one or more −i directives in the NASMENV environment variable (see section 2.1.28).

For Makefile compatibility with many C compilers, this option can also be specified as −I.

2.1.17 The −p Option: Pre−Include a File

NASM allows you to specify files to be pre−included into your source file, by the use of the −p option. So

running

nasm myfile.asm −p myinc.inc

is equivalent to running nasm myfile.asm and placing the directive %include "myinc.inc" at the

start of the file.

For consistency with the −I, −D and −U options, this option can also be specified as −P.

2.1.18 The −d Option: Pre−Define a Macro

Just as the −p option gives an alternative to placing %include directives at the start of a source file, the −d

option gives an alternative to placing a %define directive. You could code

剩余217页未读，继续阅读

codeferever

粉丝: 19
资源: 4

NASM汇编器指南：安装与使用

Nasm中文手册 PDF格式

NASM中文手册.pdf

Nasm中文手册.pdf(含目录索引)

nasm-2.15.05

我把NASM这个文件夹放在D盘，把filename.asm放在D:\NASM\example这个路径，我打开命令行，输入cdD:\NASM\example，然后输入D:\nasm\nasm.exe -f win32filename.asm，为什么显示filename.asm:122: error: parser:instruction expected?哪里出错了?是我命令输错了吗?

-DENABLE_NASM=on ..

nasm centos

centos nasm更新版本

linux 下载nasm最新版本

centos7安装nasm

cento安装nasm最新版本

linux 源码安装nasm

linux安装NASM

nasm windows

nasm shell

写一个nasm代码，在windows平台下输出helloworld！

vpp nasm is not installed!

nasm纠正性训练指南pdf

linux更新nasm

ubuntu安装nasm

最新资源