summaryrefslogtreecommitdiffstats
path: root/gnu/llvm/docs/MergeFunctions.rst
diff options
context:
space:
mode:
authorpatrick <patrick@openbsd.org>2017-01-14 19:55:43 +0000
committerpatrick <patrick@openbsd.org>2017-01-14 19:55:43 +0000
commitbd3306aecb3a15e8967143b8cdbbccf2b1b19b74 (patch)
tree309a8132b44564b9e634c0da6815187ce8eab27c /gnu/llvm/docs/MergeFunctions.rst
parentkillp -a should not kill the window if only one pane. (diff)
downloadwireguard-openbsd-bd3306aecb3a15e8967143b8cdbbccf2b1b19b74.tar.xz
wireguard-openbsd-bd3306aecb3a15e8967143b8cdbbccf2b1b19b74.zip
Import LLVM 3.9.1 including clang and lld.
Diffstat (limited to 'gnu/llvm/docs/MergeFunctions.rst')
-rw-r--r--gnu/llvm/docs/MergeFunctions.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/gnu/llvm/docs/MergeFunctions.rst b/gnu/llvm/docs/MergeFunctions.rst
index b2f6030edc1..b87cea68ba5 100644
--- a/gnu/llvm/docs/MergeFunctions.rst
+++ b/gnu/llvm/docs/MergeFunctions.rst
@@ -56,7 +56,7 @@ As a good start point, Kaleidoscope tutorial could be used:
Especially it's important to understand chapter 3 of tutorial:
-:doc:`tutorial/LangImpl3`
+:doc:`tutorial/LangImpl03`
Reader also should know how passes work in LLVM, they could use next article as
a reference and start point here:
@@ -394,7 +394,7 @@ and in right function "*FR*". And every part of *left* place is equal to the
corresponding part of *right* place, and (!) both parts use *Value* instances,
for example:
-.. code-block:: llvm
+.. code-block:: text
instr0 i32 %LV ; left side, function FL
instr0 i32 %RV ; right side, function FR
@@ -409,13 +409,13 @@ in "*FL*" and "*FR*".
Consider small example here:
-.. code-block:: llvm
+.. code-block:: text
define void %f(i32 %pf0, i32 %pf1) {
instr0 i32 %pf0 instr1 i32 %pf1 instr2 i32 123
}
-.. code-block:: llvm
+.. code-block:: text
define void %g(i32 %pg0, i32 %pg1) {
instr0 i32 %pg0 instr1 i32 %pg0 instr2 i32 123
@@ -697,7 +697,7 @@ Below is detailed body description.
If “F” may be overridden
------------------------
As follows from ``mayBeOverridden`` comments: “whether the definition of this
-global may be replaced by something non-equivalent at link time”. If so, thats
+global may be replaced by something non-equivalent at link time”. If so, that's
ok: we can use alias to *F* instead of *G* or change call instructions itself.
HasGlobalAliases, removeUsers