blob: ebc3fb772e81b83cde3580435d90091552434a71 [file] [log] [blame]
Bill Wendling29f569c2012-06-20 10:36:41 +00001================
2The LLVM Lexicon
3================
4
5.. note::
6
7 This document is a work in progress!
8
9Definitions
10===========
11
12A
13-
14
15**ADCE**
16 Aggressive Dead Code Elimination
17
Sean Silva6c95b972013-02-13 21:17:20 +000018**AST**
19 Abstract Syntax Tree.
20
21 Due to Clang's influence (mostly the fact that parsing and semantic
22 analysis are so intertwined for C and especially C++), the typical
23 working definition of AST in the LLVM community is roughly "the
24 compiler's first complete symbolic (as opposed to textual)
25 representation of an input program".
26 As such, an "AST" might be a more general graph instead of a "tree"
27 (consider the symbolic representation for the type of a typical "linked
28 list node"). This working definition is closer to what some authors
29 call an "annotated abstract syntax tree".
30
31 Consult your favorite compiler book or search engine for more details.
32
Bill Wendling29f569c2012-06-20 10:36:41 +000033B
34-
35
Dmitri Gribenkoa2d35d12012-12-11 23:13:23 +000036.. _lexicon-bb-vectorization:
37
Dmitri Gribenko2378c5e2012-10-13 17:34:49 +000038**BB Vectorization**
Dmitri Gribenkoa2d35d12012-12-11 23:13:23 +000039 Basic-Block Vectorization
Bill Wendling29f569c2012-06-20 10:36:41 +000040
Brian Gesiak4a487562017-05-04 16:50:37 +000041**BDCE**
42 Bit-tracking dead code elimination. Some bit-wise instructions (shifts,
43 ands, ors, etc.) "kill" some of their input bits -- that is, they make it
44 such that those bits can be either zero or one without affecting control or
45 data flow of a program. The BDCE pass removes instructions that only
46 compute these dead bits.
47
Dmitri Gribenko2378c5e2012-10-13 17:34:49 +000048**BURS**
Bill Wendling29f569c2012-06-20 10:36:41 +000049 Bottom Up Rewriting System --- A method of instruction selection for code
50 generation. An example is the `BURG
51 <http://www.program-transformation.org/Transform/BURG>`_ tool.
52
53C
54-
55
Nick Kledzik267d31e2015-05-20 22:04:06 +000056**CFI**
57 Call Frame Information. Used in DWARF debug info and in C++ unwind info
58 to show how the function prolog lays out the stack frame.
59
60**CIE**
61 Common Information Entry. A kind of CFI used to reduce the size of FDEs.
62 The compiler creates a CIE which contains the information common across all
63 the FDEs. Each FDE then points to its CIE.
64
Bill Wendling29f569c2012-06-20 10:36:41 +000065**CSE**
66 Common Subexpression Elimination. An optimization that removes common
67 subexpression compuation. For example ``(a+b)*(a+b)`` has two subexpressions
68 that are the same: ``(a+b)``. This optimization would perform the addition
Sanjay Patel8a1ce762014-06-26 22:18:51 +000069 only once and then perform the multiply (but only if it's computationally
Bill Wendling29f569c2012-06-20 10:36:41 +000070 correct/safe).
71
72D
73-
74
75**DAG**
76 Directed Acyclic Graph
77
78.. _derived pointer:
79.. _derived pointers:
80
81**Derived Pointer**
82 A pointer to the interior of an object, such that a garbage collector is
83 unable to use the pointer for reachability analysis. While a derived pointer
84 is live, the corresponding object pointer must be kept in a root, otherwise
85 the collector might free the referenced object. With copying collectors,
86 derived pointers pose an additional hazard that they may be invalidated at
87 any `safe point`_. This term is used in opposition to `object pointer`_.
88
89**DSA**
90 Data Structure Analysis
91
92**DSE**
93 Dead Store Elimination
94
95F
96-
97
98**FCA**
99 First Class Aggregate
100
Nick Kledzik267d31e2015-05-20 22:04:06 +0000101**FDE**
102 Frame Description Entry. A kind of CFI used to describe the stack frame of
103 one function.
104
Bill Wendling29f569c2012-06-20 10:36:41 +0000105G
106-
107
108**GC**
109 Garbage Collection. The practice of using reachability analysis instead of
110 explicit memory management to reclaim unused memory.
111
112H
113-
114
115.. _heap:
116
117**Heap**
118 In garbage collection, the region of memory which is managed using
119 reachability analysis.
120
121I
122-
123
124**IPA**
125 Inter-Procedural Analysis. Refers to any variety of code analysis that
126 occurs between procedures, functions or compilation units (modules).
127
128**IPO**
129 Inter-Procedural Optimization. Refers to any variety of code optimization
130 that occurs between procedures, functions or compilation units (modules).
131
132**ISel**
133 Instruction Selection
134
135L
136-
137
138**LCSSA**
139 Loop-Closed Static Single Assignment Form
140
Sean Silvaa1c4da92015-06-04 20:28:09 +0000141**LGTM**
142 "Looks Good To Me". In a review thread, this indicates that the
143 reviewer thinks that the patch is okay to commit.
144
Bill Wendling29f569c2012-06-20 10:36:41 +0000145**LICM**
146 Loop Invariant Code Motion
147
Nick Kledzik267d31e2015-05-20 22:04:06 +0000148**LSDA**
149 Language Specific Data Area. C++ "zero cost" unwinding is built on top a
150 generic unwinding mechanism. As the unwinder walks each frame, it calls
151 a "personality" function to do language specific analysis. Each function's
152 FDE points to an optional LSDA which is passed to the personality function.
153 For C++, the LSDA contain info about the type and location of catch
154 statements in that function.
155
Bill Wendling29f569c2012-06-20 10:36:41 +0000156**Load-VN**
157 Load Value Numbering
158
159**LTO**
160 Link-Time Optimization
161
162M
163-
164
165**MC**
166 Machine Code
167
Sean Silva5e44ffd2014-09-06 00:19:16 +0000168N
169-
170
171**NFC**
172 "No functional change". Used in a commit message to indicate that a patch
173 is a pure refactoring/cleanup.
174 Usually used in the first line, so it is visible without opening the
175 actual commit email.
176
Bill Wendling29f569c2012-06-20 10:36:41 +0000177O
178-
179.. _object pointer:
180.. _object pointers:
181
182**Object Pointer**
183 A pointer to an object such that the garbage collector is able to trace
184 references contained within the object. This term is used in opposition to
185 `derived pointer`_.
186
187P
188-
189
Brian Gesiak49f8c022016-10-06 16:39:22 +0000190**PR**
191 Problem report. A bug filed on `the LLVM Bug Tracking System
Ismail Donmezc7ff8142017-02-17 08:26:11 +0000192 <https://bugs.llvm.org/enter_bug.cgi>`_.
Brian Gesiak49f8c022016-10-06 16:39:22 +0000193
Bill Wendling29f569c2012-06-20 10:36:41 +0000194**PRE**
195 Partial Redundancy Elimination
196
197R
198-
199
200**RAUW**
201
202 Replace All Uses With. The functions ``User::replaceUsesOfWith()``,
203 ``Value::replaceAllUsesWith()``, and
204 ``Constant::replaceUsesOfWithOnConstant()`` implement the replacement of one
205 Value with another by iterating over its def/use chain and fixing up all of
206 the pointers to point to the new value. See
Sanjay Patel8c982302014-07-14 19:52:36 +0000207 also `def/use chains <ProgrammersManual.html#iterating-over-def-use-use-def-chains>`_.
Bill Wendling29f569c2012-06-20 10:36:41 +0000208
209**Reassociation**
210 Rearranging associative expressions to promote better redundancy elimination
211 and other optimization. For example, changing ``(A+B-A)`` into ``(B+A-A)``,
212 permitting it to be optimized into ``(B+0)`` then ``(B)``.
213
214.. _roots:
215.. _stack roots:
216
217**Root**
218 In garbage collection, a pointer variable lying outside of the `heap`_ from
219 which the collector begins its reachability analysis. In the context of code
220 generation, "root" almost always refers to a "stack root" --- a local or
Dmitri Gribenko2378c5e2012-10-13 17:34:49 +0000221 temporary variable within an executing function.
Bill Wendling29f569c2012-06-20 10:36:41 +0000222
223**RPO**
224 Reverse postorder
225
226S
227-
228
229.. _safe point:
230
231**Safe Point**
232 In garbage collection, it is necessary to identify `stack roots`_ so that
233 reachability analysis may proceed. It may be infeasible to provide this
234 information for every instruction, so instead the information may is
235 calculated only at designated safe points. With a copying collector,
236 `derived pointers`_ must not be retained across safe points and `object
237 pointers`_ must be reloaded from stack roots.
238
239**SDISel**
240 Selection DAG Instruction Selection.
241
242**SCC**
243 Strongly Connected Component
244
245**SCCP**
246 Sparse Conditional Constant Propagation
247
Dmitri Gribenkoa2d35d12012-12-11 23:13:23 +0000248**SLP**
249 Superword-Level Parallelism, same as :ref:`Basic-Block Vectorization
250 <lexicon-bb-vectorization>`.
251
Sanjay Patel2413af22017-05-12 21:30:31 +0000252**Splat**
253 Splat refers to a vector of identical scalar elements.
254
255 The term is based on the PowerPC Altivec instructions that provided
256 this functionality in hardware. For example, "vsplth" and the corresponding
257 software intrinsic "vec_splat()". Examples of other hardware names for this
258 action include "duplicate" (ARM) and "broadcast" (x86).
259
Bill Wendling29f569c2012-06-20 10:36:41 +0000260**SRoA**
261 Scalar Replacement of Aggregates
262
263**SSA**
264 Static Single Assignment
265
266**Stack Map**
267 In garbage collection, metadata emitted by the code generator which
268 identifies `roots`_ within the stack frame of an executing function.
Dmitri Gribenko2378c5e2012-10-13 17:34:49 +0000269
270T
271-
272
273**TBAA**
274 Type-Based Alias Analysis
275