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
diff --git a/docs/CommandGuide/llvm-nm.html b/docs/CommandGuide/llvm-nm.html
index 6238b75..91d8958 100644
--- a/docs/CommandGuide/llvm-nm.html
+++ b/docs/CommandGuide/llvm-nm.html
@@ -17,10 +17,11 @@
<h3>DESCRIPTION</h3>
<p>The <tt>llvm-nm</tt> 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, <tt>llvm-nm</tt> reads its input from standard
-input.</p>
+LLVM bytecode files, or <tt>ar(1)</tt> 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, <tt>llvm-nm</tt> will process a bytecode file
+on its standard input stream.</p>
<p><tt>llvm-nm</tt>'s default output format is the traditional BSD
<tt>nm(1)</tt> output format. Each such output record consists of an
@@ -97,8 +98,7 @@
<h3>BUGS</h3>
-<tt>llvm-nm</tt> cannot currently see inside <tt>ar(1)</tt> library
-archive files, like <tt>nm(1)</tt> can. It cannot demangle C++ mangled
+<tt>llvm-nm</tt> cannot demangle C++ mangled
names, like GNU <tt>nm(1)</tt> can.
<h3>EXIT STATUS</h3>