summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRafael Espindola <rafael.espindola@gmail.com>2010-08-08 21:14:26 +0000
committerRafael Espindola <rafael.espindola@gmail.com>2010-08-08 21:14:26 +0000
commit53843f8edb1ff86f29a1857bb8015deb7cadbce2 (patch)
tree6782b0982f73d7bd756e42fd5e5dbf0b8edecbff
parent991808005a27b2e0049e124bf69250281276c317 (diff)
downloadllvm-53843f8edb1ff86f29a1857bb8015deb7cadbce2.tar.gz
llvm-53843f8edb1ff86f29a1857bb8015deb7cadbce2.tar.bz2
llvm-53843f8edb1ff86f29a1857bb8015deb7cadbce2.tar.xz
s/libLLVMgold/LLVMgold/g
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@110552 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/GoldPlugin.html8
-rw-r--r--tools/gold/README.txt4
2 files changed, 6 insertions, 6 deletions
diff --git a/docs/GoldPlugin.html b/docs/GoldPlugin.html
index 66e099bad0..3f2e9fb2e6 100644
--- a/docs/GoldPlugin.html
+++ b/docs/GoldPlugin.html
@@ -79,7 +79,7 @@ placed.
the plugin <tt>.so</tt> file. To find out what link command <tt>gcc</tt>
would run in a given situation, run <tt>gcc -v <em>[...]</em></tt> and look
for the line where it runs <tt>collect2</tt>. Replace that with
- <tt>ld-new -plugin /path/to/libLLVMgold.so</tt> to test it out. Once you're
+ <tt>ld-new -plugin /path/to/LLVMgold.so</tt> to test it out. Once you're
ready to switch to using gold, backup your existing <tt>/usr/bin/ld</tt>
then replace it with <tt>ld-new</tt>.</p>
<p>You can produce bitcode files from <tt>llvm-gcc</tt> using
@@ -91,7 +91,7 @@ placed.
linker, which is why you need gold to be the installed system linker in your
path.</p>
<p>If you want <tt>ar</tt> and <tt>nm</tt> to work seamlessly as well, install
- <tt>libLLVMgold.so</tt> to <tt>/usr/lib/bfd-plugins</tt>. If you built your
+ <tt>LLVMgold.so</tt> to <tt>/usr/lib/bfd-plugins</tt>. If you built your
own gold, be sure to install the <tt>ar</tt> and <tt>nm-new</tt> you built to
<tt>/usr/bin</tt>.
<p>
@@ -157,9 +157,9 @@ $ llvm-gcc -use-gold-plugin a.a b.o -o main # &lt;-- link with LLVMgold plugin
bitcode, everything is in place for an easy to use LTO build of autotooled
projects:</p>
<ul>
- <li>Follow the instructions <a href="#build">on how to build libLLVMgold.so</a>.</li>
+ <li>Follow the instructions <a href="#build">on how to build LLVMgold.so</a>.</li>
<li>Install the newly built binutils to <tt>$PREFIX</tt></li>
- <li>Copy <tt>Release/lib/libLLVMgold.so</tt> to
+ <li>Copy <tt>Release/lib/LLVMgold.so</tt> to
<tt>$PREFIX/libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/</tt> and
<tt>$PREFIX/lib/bfd-plugins/</tt></li>
<li>Set environment variables (<tt>$PREFIX</tt> is where you installed llvm-gcc and
diff --git a/tools/gold/README.txt b/tools/gold/README.txt
index 92ee3d16af..a906a9083e 100644
--- a/tools/gold/README.txt
+++ b/tools/gold/README.txt
@@ -14,8 +14,8 @@ Then build binutils with "make all-gold".
To build the LLVMgold plugin, configure LLVM with the option
--with-binutils-include=/path/to/binutils/src/include/ --enable-pic. To use the
-plugin, run "ld-new --plugin /path/to/libLLVMgold.so".
-Without PIC libLTO and libLLVMgold are not being built (because they would fail
+plugin, run "ld-new --plugin /path/to/LLVMgold.so".
+Without PIC libLTO and LLVMgold are not being built (because they would fail
link on x86-64 with a relocation error: PIC and non-PIC can't be combined).
As an alternative to passing --enable-pic, you can use 'make ENABLE_PIC=1' in
your entire LLVM build.