From f00785ff349f24e7aea15339dd8293d369ffdc58 Mon Sep 17 00:00:00 2001 From: Brian Gaeke Date: Tue, 18 Nov 2003 06:18:09 +0000 Subject: [PATCH] Update to reflect the fact that llvm-nm can read archives now. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@10061 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/CommandGuide/llvm-nm.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/CommandGuide/llvm-nm.html b/docs/CommandGuide/llvm-nm.html index 6238b756d52..91d89583da7 100644 --- a/docs/CommandGuide/llvm-nm.html +++ b/docs/CommandGuide/llvm-nm.html @@ -17,10 +17,11 @@ LLVM: llvm-nm tool

DESCRIPTION

The llvm-nm utility lists the names of symbols from the -LLVM bytecode files named on the command line, along with some -ancillary information about each symbol. If no filename is specified, -or - is used as a filename, llvm-nm reads its input from standard -input.

+LLVM bytecode files, or ar(1) archives containing LLVM +bytecode files, named on the command line. Each symbol is listed along +with some simple information about its provenance. If no filename is specified, +or - is used as a filename, llvm-nm will process a bytecode file +on its standard input stream.

llvm-nm's default output format is the traditional BSD nm(1) output format. Each such output record consists of an @@ -97,8 +98,7 @@ the bytecode file.

BUGS

-llvm-nm cannot currently see inside ar(1) library -archive files, like nm(1) can. It cannot demangle C++ mangled +llvm-nm cannot demangle C++ mangled names, like GNU nm(1) can.

EXIT STATUS