[llvm-commits] [llvm] r165334 - /llvm/trunk/docs/GoldPlugin.rst

[Dmitri Gribenko]

Author: gribozavr
Date: Fri Oct  5 15:50:05 2012
New Revision: 165334

URL: http://llvm.org/viewvc/llvm-project?rev=165334&view=rev
Log:
GoldPlugin.rst: minor typesetting fixes.

Modified:
    llvm/trunk/docs/GoldPlugin.rst

Modified: llvm/trunk/docs/GoldPlugin.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/GoldPlugin.rst?rev=165334&r1=165333&r2=165334&view=diff
==============================================================================
--- llvm/trunk/docs/GoldPlugin.rst (original)
+++ llvm/trunk/docs/GoldPlugin.rst Fri Oct  5 15:50:05 2012
@@ -76,11 +76,11 @@
 Any of these flags will also cause ``clang`` to look for the gold plugin in
 the ``lib`` directory under its prefix and pass the ``-plugin`` option to
 ``ld``. It will not look for an alternate linker, which is why you need
-gold to be the installed system linker in your path.``
+gold to be the installed system linker in your path.
 
 If you want ``ar`` and ``nm`` to work seamlessly as well, install
 ``LLVMgold.so`` to ``/usr/lib/bfd-plugins``. If you built your own gold, be
-sure to install the ``ar`` and ``nm-new`` you built to ``/usr/bin``
+sure to install the ``ar`` and ``nm-new`` you built to ``/usr/bin``.
 
 
 Example of link time optimization
@@ -181,6 +181,6 @@
 =========
 
 Gold is licensed under the GPLv3. LLVMgold uses the interface file
-``plugin-api.h`` from gold which means that the resulting LLVMgold.so
+``plugin-api.h`` from gold which means that the resulting ``LLVMgold.so``
 binary is also GPLv3. This can still be used to link non-GPLv3 programs
 just as much as gold could without the plugin.