summaryrefslogtreecommitdiffstats
path: root/llvm/docs/WritingAnLLVMPass.rst
diff options
context:
space:
mode:
authorJonathan Roelofs <jonathan@codesourcery.com>2015-10-23 17:42:51 +0000
committerJonathan Roelofs <jonathan@codesourcery.com>2015-10-23 17:42:51 +0000
commit939d4a8cbc042bf9f2c78f1b1fab6c41c2bf9aba (patch)
tree82476bf5cf3708367b186575ba24623847d534a0 /llvm/docs/WritingAnLLVMPass.rst
parent28ba6fda48dfbab210d27aa4a551f97fcb53eaf9 (diff)
downloadbcm5719-llvm-939d4a8cbc042bf9f2c78f1b1fab6c41c2bf9aba.tar.gz
bcm5719-llvm-939d4a8cbc042bf9f2c78f1b1fab6c41c2bf9aba.zip
Fix another reference to in-source builds
llvm-svn: 251127
Diffstat (limited to 'llvm/docs/WritingAnLLVMPass.rst')
-rw-r--r--llvm/docs/WritingAnLLVMPass.rst17
1 files changed, 8 insertions, 9 deletions
diff --git a/llvm/docs/WritingAnLLVMPass.rst b/llvm/docs/WritingAnLLVMPass.rst
index a35802811b6..241066842b7 100644
--- a/llvm/docs/WritingAnLLVMPass.rst
+++ b/llvm/docs/WritingAnLLVMPass.rst
@@ -203,9 +203,8 @@ As a whole, the ``.cpp`` file looks like:
static RegisterPass<Hello> X("hello", "Hello World Pass", false, false);
Now that it's all together, compile the file with a simple "``gmake``" command
-in the local directory and you should get a new file
-"``Debug+Asserts/lib/Hello.so``" under the top level directory of the LLVM
-source tree (not in the local directory). Note that everything in this file is
+from the top level of your build directory and you should get a new file
+"``Debug+Asserts/lib/Hello.so``". Note that everything in this file is
contained in an anonymous namespace --- this reflects the fact that passes
are self contained units that do not need external interfaces (although they
can have them) to be useful.
@@ -225,7 +224,7 @@ will work):
.. code-block:: console
- $ opt -load ../../../Debug+Asserts/lib/Hello.so -hello < hello.bc > /dev/null
+ $ opt -load ../../Debug+Asserts/lib/Hello.so -hello < hello.bc > /dev/null
Hello: __main
Hello: puts
Hello: main
@@ -242,7 +241,7 @@ To see what happened to the other string you registered, try running
.. code-block:: console
- $ opt -load ../../../Debug+Asserts/lib/Hello.so -help
+ $ opt -load ../../Debug+Asserts/lib/Hello.so -help
OVERVIEW: llvm .bc -> .bc modular optimizer
USAGE: opt [options] <input bitcode>
@@ -269,7 +268,7 @@ you queue up. For example:
.. code-block:: console
- $ opt -load ../../../Debug+Asserts/lib/Hello.so -hello -time-passes < hello.bc > /dev/null
+ $ opt -load ../../Debug+Asserts/lib/Hello.so -hello -time-passes < hello.bc > /dev/null
Hello: __main
Hello: puts
Hello: main
@@ -1089,7 +1088,7 @@ passes. Lets try it out with the gcse and licm passes:
.. code-block:: console
- $ opt -load ../../../Debug+Asserts/lib/Hello.so -gcse -licm --debug-pass=Structure < hello.bc > /dev/null
+ $ opt -load ../../Debug+Asserts/lib/Hello.so -gcse -licm --debug-pass=Structure < hello.bc > /dev/null
Module Pass Manager
Function Pass Manager
Dominator Set Construction
@@ -1126,7 +1125,7 @@ Lets see how this changes when we run the :ref:`Hello World
.. code-block:: console
- $ opt -load ../../../Debug+Asserts/lib/Hello.so -gcse -hello -licm --debug-pass=Structure < hello.bc > /dev/null
+ $ opt -load ../../Debug+Asserts/lib/Hello.so -gcse -hello -licm --debug-pass=Structure < hello.bc > /dev/null
Module Pass Manager
Function Pass Manager
Dominator Set Construction
@@ -1167,7 +1166,7 @@ Now when we run our pass, we get this output:
.. code-block:: console
- $ opt -load ../../../Debug+Asserts/lib/Hello.so -gcse -hello -licm --debug-pass=Structure < hello.bc > /dev/null
+ $ opt -load ../../Debug+Asserts/lib/Hello.so -gcse -hello -licm --debug-pass=Structure < hello.bc > /dev/null
Pass Arguments: -gcse -hello -licm
Module Pass Manager
Function Pass Manager
OpenPOWER on IntegriCloud