summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEli Bendersky <eliben@google.com>2013-06-07 20:24:43 +0000
committerEli Bendersky <eliben@google.com>2013-06-07 20:24:43 +0000
commit88fe6824ee72e2700befa83886782f48314fe1c3 (patch)
tree4c96a7b316a754bbd0f21eb9d63021a0356ab35c /docs
parent9a6b9bffa53bfa5e1a8373b31b2ddfa7b6bd7b30 (diff)
downloadllvm-88fe6824ee72e2700befa83886782f48314fe1c3.tar.gz
llvm-88fe6824ee72e2700befa83886782f48314fe1c3.tar.bz2
llvm-88fe6824ee72e2700befa83886782f48314fe1c3.tar.xz
Add more explicit link targets to headers in LangRef.rst
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@183555 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r--docs/LangRef.rst18
1 files changed, 18 insertions, 0 deletions
diff --git a/docs/LangRef.rst b/docs/LangRef.rst
index 4c3a4789f7..949dc4a876 100644
--- a/docs/LangRef.rst
+++ b/docs/LangRef.rst
@@ -1367,6 +1367,8 @@ transformation. A strong type system makes it easier to read the
generated code and enables novel analyses and transformations that are
not feasible to perform on normal three address code representations.
+.. _typeclassifications:
+
Type Classifications
--------------------
@@ -1880,6 +1882,8 @@ followed by 4 hexadecimal digits. All hexadecimal formats are big-endian
There are no constants of type x86mmx.
+.. _complexconstants:
+
Complex Constants
-----------------
@@ -2201,6 +2205,8 @@ instruction.
Finally, some targets may provide defined semantics when using the value
as the operand to an inline assembly, but that is target specific.
+.. _constantexprs:
+
Constant Expressions
--------------------
@@ -2305,6 +2311,8 @@ The following is the syntax for constant expressions:
Other Values
============
+.. _inlineasmexprs:
+
Inline Assembler Expressions
----------------------------
@@ -2906,6 +2914,8 @@ Each individual option is required to be either a valid option for the target's
linker, or an option that is reserved by the target specific assembly writer or
object file emitter. No other aspect of these options is defined by the IR.
+.. _intrinsicglobalvariables:
+
Intrinsic Global Variables
==========================
@@ -2915,6 +2925,8 @@ All globals of this sort should have a section specified as
"``llvm.metadata``". This section and all globals that start with
"``llvm.``" are reserved for use by LLVM.
+.. _gv_llvmused:
+
The '``llvm.used``' Global Variable
-----------------------------------
@@ -2946,6 +2958,8 @@ On some targets, the code generator must emit a directive to the
assembler or object file to prevent the assembler and linker from
molesting the symbol.
+.. _gv_llvmcompilerused:
+
The '``llvm.compiler.used``' Global Variable
--------------------------------------------
@@ -2958,6 +2972,8 @@ by ``@llvm.used``.
This is a rare construct that should only be used in rare circumstances,
and should not be exposed to source languages.
+.. _gv_llvmglobalctors:
+
The '``llvm.global_ctors``' Global Variable
-------------------------------------------
@@ -2972,6 +2988,8 @@ array will be called in ascending order of priority (i.e. lowest first)
when the module is loaded. The order of functions with the same priority
is not defined.
+.. _llvmglobaldtors:
+
The '``llvm.global_dtors``' Global Variable
-------------------------------------------