blob: 166ce0790c1113333101ad9ba7c79f196c6b9e1e [file] [log] [blame]
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
2 "http://www.w3.org/TR/html4/strict.dtd">
3<html>
4<head>
Bill Wendling48839d92009-05-17 05:52:39 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Chris Lattnerbdfb3392004-01-05 05:06:33 +00006 <title>Source Level Debugging with LLVM</title>
7 <link rel="stylesheet" href="llvm.css" type="text/css">
8</head>
9<body>
10
11<div class="doc_title">Source Level Debugging with LLVM</div>
12
Reid Spencerd3f876c2004-11-01 08:19:36 +000013<table class="layout" style="width:100%">
14 <tr class="layout">
15 <td class="left">
Chris Lattnerbdfb3392004-01-05 05:06:33 +000016<ul>
Misha Brukman82873732004-05-12 19:21:57 +000017 <li><a href="#introduction">Introduction</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +000018 <ol>
19 <li><a href="#phil">Philosophy behind LLVM debugging information</a></li>
Jim Laskey383e0092006-03-23 17:54:33 +000020 <li><a href="#consumers">Debug information consumers</a></li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +000021 <li><a href="#debugopt">Debugging optimized code</a></li>
Misha Brukman82873732004-05-12 19:21:57 +000022 </ol></li>
Misha Brukman82873732004-05-12 19:21:57 +000023 <li><a href="#format">Debugging information format</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +000024 <ol>
Jim Laskeycec12a52006-03-14 18:08:46 +000025 <li><a href="#debug_info_descriptors">Debug information descriptors</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +000026 <ul>
Jim Laskeycec12a52006-03-14 18:08:46 +000027 <li><a href="#format_compile_units">Compile unit descriptors</a></li>
Devang Patel4b945502010-03-09 00:44:10 +000028 <li><a href="#format_files">File descriptors</a></li>
Jim Laskeycec12a52006-03-14 18:08:46 +000029 <li><a href="#format_global_variables">Global variable descriptors</a></li>
30 <li><a href="#format_subprograms">Subprogram descriptors</a></li>
Jim Laskey3d11bee2006-03-15 19:10:52 +000031 <li><a href="#format_blocks">Block descriptors</a></li>
Jim Laskeycec12a52006-03-14 18:08:46 +000032 <li><a href="#format_basic_type">Basic type descriptors</a></li>
33 <li><a href="#format_derived_type">Derived type descriptors</a></li>
34 <li><a href="#format_composite_type">Composite type descriptors</a></li>
35 <li><a href="#format_subrange">Subrange descriptors</a></li>
36 <li><a href="#format_enumeration">Enumerator descriptors</a></li>
Jim Laskey383e0092006-03-23 17:54:33 +000037 <li><a href="#format_variables">Local variables</a></li>
Misha Brukman82873732004-05-12 19:21:57 +000038 </ul></li>
Jim Laskeycec12a52006-03-14 18:08:46 +000039 <li><a href="#format_common_intrinsics">Debugger intrinsic functions</a>
40 <ul>
Jim Laskeycec12a52006-03-14 18:08:46 +000041 <li><a href="#format_common_declare">llvm.dbg.declare</a></li>
Victor Hernandez67a1a542010-01-11 22:53:48 +000042 <li><a href="#format_common_value">llvm.dbg.value</a></li>
Jim Laskeycec12a52006-03-14 18:08:46 +000043 </ul></li>
Misha Brukman82873732004-05-12 19:21:57 +000044 </ol></li>
Devang Patel744950d2009-11-25 23:28:01 +000045 <li><a href="#format_common_lifetime">Object lifetimes and scoping</a></li>
Misha Brukman82873732004-05-12 19:21:57 +000046 <li><a href="#ccxx_frontend">C/C++ front-end specific debug information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +000047 <ol>
Jim Laskeycec12a52006-03-14 18:08:46 +000048 <li><a href="#ccxx_compile_units">C/C++ source file information</a></li>
49 <li><a href="#ccxx_global_variable">C/C++ global variable information</a></li>
50 <li><a href="#ccxx_subprogram">C/C++ function information</a></li>
51 <li><a href="#ccxx_basic_types">C/C++ basic types</a></li>
52 <li><a href="#ccxx_derived_types">C/C++ derived types</a></li>
53 <li><a href="#ccxx_composite_types">C/C++ struct/union types</a></li>
54 <li><a href="#ccxx_enumeration_types">C/C++ enumeration types</a></li>
Misha Brukman82873732004-05-12 19:21:57 +000055 </ol></li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +000056</ul>
Misha Brukman82873732004-05-12 19:21:57 +000057</td>
Reid Spencerd3f876c2004-11-01 08:19:36 +000058<td class="right">
Misha Brukmane849a1a2004-05-12 21:26:16 +000059<img src="img/venusflytrap.jpg" alt="A leafy and green bug eater" width="247"
Misha Brukman82873732004-05-12 19:21:57 +000060height="369">
61</td>
Reid Spencerd3f876c2004-11-01 08:19:36 +000062</tr></table>
Misha Brukman82873732004-05-12 19:21:57 +000063
Chris Lattner7911ce22004-05-23 21:07:27 +000064<div class="doc_author">
Jim Laskeycec12a52006-03-14 18:08:46 +000065 <p>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a>
Jim Laskeyc760a922007-03-14 19:32:21 +000066 and <a href="mailto:jlaskey@mac.com">Jim Laskey</a></p>
Chris Lattner7911ce22004-05-23 21:07:27 +000067</div>
68
Chris Lattnerbdfb3392004-01-05 05:06:33 +000069
70<!-- *********************************************************************** -->
Misha Brukman94218a72004-12-09 20:27:37 +000071<div class="doc_section"><a name="introduction">Introduction</a></div>
72<!-- *********************************************************************** -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +000073
74<div class="doc_text">
75
76<p>This document is the central repository for all information pertaining to
Bill Wendling48839d92009-05-17 05:52:39 +000077 debug information in LLVM. It describes the <a href="#format">actual format
78 that the LLVM debug information</a> takes, which is useful for those
79 interested in creating front-ends or dealing directly with the information.
Chris Lattner8ad2f982009-07-18 21:47:15 +000080 Further, this document provides specific examples of what debug information
Bill Wendling48839d92009-05-17 05:52:39 +000081 for C/C++.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +000082
83</div>
84
85<!-- ======================================================================= -->
86<div class="doc_subsection">
87 <a name="phil">Philosophy behind LLVM debugging information</a>
88</div>
89
90<div class="doc_text">
91
Misha Brukman82873732004-05-12 19:21:57 +000092<p>The idea of the LLVM debugging information is to capture how the important
Bill Wendling48839d92009-05-17 05:52:39 +000093 pieces of the source-language's Abstract Syntax Tree map onto LLVM code.
94 Several design aspects have shaped the solution that appears here. The
95 important ones are:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +000096
Misha Brukman82873732004-05-12 19:21:57 +000097<ul>
Bill Wendling48839d92009-05-17 05:52:39 +000098 <li>Debugging information should have very little impact on the rest of the
99 compiler. No transformations, analyses, or code generators should need to
100 be modified because of debugging information.</li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000101
Bill Wendling48839d92009-05-17 05:52:39 +0000102 <li>LLVM optimizations should interact in <a href="#debugopt">well-defined and
103 easily described ways</a> with the debugging information.</li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000104
Bill Wendling48839d92009-05-17 05:52:39 +0000105 <li>Because LLVM is designed to support arbitrary programming languages,
106 LLVM-to-LLVM tools should not need to know anything about the semantics of
107 the source-level-language.</li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000108
Bill Wendling48839d92009-05-17 05:52:39 +0000109 <li>Source-level languages are often <b>widely</b> different from one another.
110 LLVM should not put any restrictions of the flavor of the source-language,
111 and the debugging information should work with any language.</li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000112
Bill Wendling48839d92009-05-17 05:52:39 +0000113 <li>With code generator support, it should be possible to use an LLVM compiler
114 to compile a program to native machine code and standard debugging
115 formats. This allows compatibility with traditional machine-code level
116 debuggers, like GDB or DBX.</li>
Misha Brukman82873732004-05-12 19:21:57 +0000117</ul>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000118
Bill Wendling48839d92009-05-17 05:52:39 +0000119<p>The approach used by the LLVM implementation is to use a small set
120 of <a href="#format_common_intrinsics">intrinsic functions</a> to define a
121 mapping between LLVM program objects and the source-level objects. The
Devang Patele4b27562009-08-28 23:24:31 +0000122 description of the source-level program is maintained in LLVM metadata
123 in an <a href="#ccxx_frontend">implementation-defined format</a>
Bill Wendling48839d92009-05-17 05:52:39 +0000124 (the C/C++ front-end currently uses working draft 7 of
125 the <a href="http://www.eagercon.com/dwarf/dwarf3std.htm">DWARF 3
126 standard</a>).</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000127
Jim Laskeycec12a52006-03-14 18:08:46 +0000128<p>When a program is being debugged, a debugger interacts with the user and
Bill Wendling48839d92009-05-17 05:52:39 +0000129 turns the stored debug information into source-language specific information.
130 As such, a debugger must be aware of the source-language, and is thus tied to
131 a specific language or family of languages.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000132
133</div>
134
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000135<!-- ======================================================================= -->
136<div class="doc_subsection">
Jim Laskey383e0092006-03-23 17:54:33 +0000137 <a name="consumers">Debug information consumers</a>
138</div>
139
140<div class="doc_text">
Bill Wendling48839d92009-05-17 05:52:39 +0000141
Jim Laskey383e0092006-03-23 17:54:33 +0000142<p>The role of debug information is to provide meta information normally
Bill Wendling48839d92009-05-17 05:52:39 +0000143 stripped away during the compilation process. This meta information provides
144 an LLVM user a relationship between generated code and the original program
145 source code.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000146
Chris Lattnerc3107782010-04-05 04:11:11 +0000147<p>Currently, debug information is consumed by DwarfDebug to produce dwarf
Bill Wendling48839d92009-05-17 05:52:39 +0000148 information used by the gdb debugger. Other targets could use the same
149 information to produce stabs or other debug forms.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000150
151<p>It would also be reasonable to use debug information to feed profiling tools
Bill Wendling48839d92009-05-17 05:52:39 +0000152 for analysis of generated code, or, tools for reconstructing the original
153 source from generated code.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000154
155<p>TODO - expound a bit more.</p>
156
157</div>
158
159<!-- ======================================================================= -->
160<div class="doc_subsection">
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000161 <a name="debugopt">Debugging optimized code</a>
162</div>
163
164<div class="doc_text">
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000165
Misha Brukman82873732004-05-12 19:21:57 +0000166<p>An extremely high priority of LLVM debugging information is to make it
Bill Wendling48839d92009-05-17 05:52:39 +0000167 interact well with optimizations and analysis. In particular, the LLVM debug
168 information provides the following guarantees:</p>
Misha Brukman82873732004-05-12 19:21:57 +0000169
170<ul>
Bill Wendling48839d92009-05-17 05:52:39 +0000171 <li>LLVM debug information <b>always provides information to accurately read
172 the source-level state of the program</b>, regardless of which LLVM
173 optimizations have been run, and without any modification to the
174 optimizations themselves. However, some optimizations may impact the
175 ability to modify the current state of the program with a debugger, such
176 as setting program variables, or calling functions that have been
177 deleted.</li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000178
Bill Wendling48839d92009-05-17 05:52:39 +0000179 <li>LLVM optimizations gracefully interact with debugging information. If
180 they are not aware of debug information, they are automatically disabled
181 as necessary in the cases that would invalidate the debug info. This
182 retains the LLVM features, making it easy to write new
183 transformations.</li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000184
Bill Wendling48839d92009-05-17 05:52:39 +0000185 <li>As desired, LLVM optimizations can be upgraded to be aware of the LLVM
186 debugging information, allowing them to update the debugging information
187 as they perform aggressive optimizations. This means that, with effort,
188 the LLVM optimizers could optimize debug code just as well as non-debug
189 code.</li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000190
Bill Wendling48839d92009-05-17 05:52:39 +0000191 <li>LLVM debug information does not prevent many important optimizations from
192 happening (for example inlining, basic block reordering/merging/cleanup,
193 tail duplication, etc), further reducing the amount of the compiler that
194 eventually is "aware" of debugging information.</li>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000195
Bill Wendling48839d92009-05-17 05:52:39 +0000196 <li>LLVM debug information is automatically optimized along with the rest of
197 the program, using existing facilities. For example, duplicate
198 information is automatically merged by the linker, and unused information
199 is automatically removed.</li>
Misha Brukman82873732004-05-12 19:21:57 +0000200</ul>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000201
Misha Brukman82873732004-05-12 19:21:57 +0000202<p>Basically, the debug information allows you to compile a program with
Bill Wendling48839d92009-05-17 05:52:39 +0000203 "<tt>-O0 -g</tt>" and get full debug information, allowing you to arbitrarily
204 modify the program as it executes from a debugger. Compiling a program with
205 "<tt>-O3 -g</tt>" gives you full debug information that is always available
206 and accurate for reading (e.g., you get accurate stack traces despite tail
207 call elimination and inlining), but you might lose the ability to modify the
208 program and call functions where were optimized out of the program, or
209 inlined away completely.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000210
Misha Brukman96e00812008-12-16 02:54:22 +0000211<p><a href="TestingGuide.html#quicktestsuite">LLVM test suite</a> provides a
Bill Wendling48839d92009-05-17 05:52:39 +0000212 framework to test optimizer's handling of debugging information. It can be
213 run like this:</p>
Devang Patela5c05aa2008-11-21 19:35:57 +0000214
215<div class="doc_code">
216<pre>
217% cd llvm/projects/test-suite/MultiSource/Benchmarks # or some other level
218% make TEST=dbgopt
219</pre>
220</div>
221
Bill Wendling48839d92009-05-17 05:52:39 +0000222<p>This will test impact of debugging information on optimization passes. If
223 debugging information influences optimization passes then it will be reported
224 as a failure. See <a href="TestingGuide.html">TestingGuide</a> for more
225 information on LLVM test infrastructure and how to run various tests.</p>
Devang Patela5c05aa2008-11-21 19:35:57 +0000226
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000227</div>
228
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000229<!-- *********************************************************************** -->
230<div class="doc_section">
Chris Lattner8ff75902004-01-06 05:31:32 +0000231 <a name="format">Debugging information format</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000232</div>
233<!-- *********************************************************************** -->
234
235<div class="doc_text">
236
237<p>LLVM debugging information has been carefully designed to make it possible
Bill Wendling48839d92009-05-17 05:52:39 +0000238 for the optimizer to optimize the program and debugging information without
239 necessarily having to know anything about debugging information. In
John Criswellb34500f2010-03-17 15:01:50 +0000240 particular, the use of metadata avoids duplicated debugging information from
Devang Patele4b27562009-08-28 23:24:31 +0000241 the beginning, and the global dead code elimination pass automatically
242 deletes debugging information for a function if it decides to delete the
243 function. </p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000244
245<p>To do this, most of the debugging information (descriptors for types,
Bill Wendling48839d92009-05-17 05:52:39 +0000246 variables, functions, source files, etc) is inserted by the language
Devang Patele4b27562009-08-28 23:24:31 +0000247 front-end in the form of LLVM metadata. </p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000248
Jim Laskeycec12a52006-03-14 18:08:46 +0000249<p>Debug information is designed to be agnostic about the target debugger and
Bill Wendling48839d92009-05-17 05:52:39 +0000250 debugging information representation (e.g. DWARF/Stabs/etc). It uses a
Devang Patele4b27562009-08-28 23:24:31 +0000251 generic pass to decode the information that represents variables, types,
252 functions, namespaces, etc: this allows for arbitrary source-language
253 semantics and type-systems to be used, as long as there is a module
254 written for the target debugger to interpret the information. </p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000255
Misha Brukman82873732004-05-12 19:21:57 +0000256<p>To provide basic functionality, the LLVM debugger does have to make some
Bill Wendling48839d92009-05-17 05:52:39 +0000257 assumptions about the source-level language being debugged, though it keeps
258 these to a minimum. The only common features that the LLVM debugger assumes
Devang Patel4b945502010-03-09 00:44:10 +0000259 exist are <a href="#format_files">source files</a>,
Bill Wendling48839d92009-05-17 05:52:39 +0000260 and <a href="#format_global_variables">program objects</a>. These abstract
261 objects are used by a debugger to form stack traces, show information about
262 local variables, etc.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000263
264<p>This section of the documentation first describes the representation aspects
Bill Wendling48839d92009-05-17 05:52:39 +0000265 common to any source-language. The <a href="#ccxx_frontend">next section</a>
266 describes the data layout conventions used by the C and C++ front-ends.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000267
268</div>
269
270<!-- ======================================================================= -->
271<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000272 <a name="debug_info_descriptors">Debug information descriptors</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000273</div>
274
275<div class="doc_text">
Bill Wendling48839d92009-05-17 05:52:39 +0000276
Jim Laskeycec12a52006-03-14 18:08:46 +0000277<p>In consideration of the complexity and volume of debug information, LLVM
Devang Patele4b27562009-08-28 23:24:31 +0000278 provides a specification for well formed debug descriptors. </p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000279
Jim Laskeycec12a52006-03-14 18:08:46 +0000280<p>Consumers of LLVM debug information expect the descriptors for program
Bill Wendling48839d92009-05-17 05:52:39 +0000281 objects to start in a canonical format, but the descriptors can include
282 additional information appended at the end that is source-language
283 specific. All LLVM debugging information is versioned, allowing backwards
284 compatibility in the case that the core structures need to change in some
285 way. Also, all debugging information objects start with a tag to indicate
286 what type of object it is. The source-language is allowed to define its own
287 objects, by using unreserved tag numbers. We recommend using with tags in
Benjamin Kramer8040cd32009-10-12 14:46:08 +0000288 the range 0x1000 through 0x2000 (there is a defined enum DW_TAG_user_base =
Bill Wendling48839d92009-05-17 05:52:39 +0000289 0x1000.)</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000290
Devang Patele4b27562009-08-28 23:24:31 +0000291<p>The fields of debug descriptors used internally by LLVM
Nick Lewycky655fd032010-03-31 07:50:17 +0000292 are restricted to only the simple data types <tt>i32</tt>, <tt>i1</tt>,
293 <tt>float</tt>, <tt>double</tt>, <tt>mdstring</tt> and <tt>mdnode</tt>. </p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000294
Bill Wendling48839d92009-05-17 05:52:39 +0000295<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000296<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000297!1 = metadata !{
Nick Lewycky655fd032010-03-31 07:50:17 +0000298 i32, ;; A tag
Bill Wendling48839d92009-05-17 05:52:39 +0000299 ...
300}
Misha Brukman82873732004-05-12 19:21:57 +0000301</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000302</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000303
Jim Laskey7089f452006-06-16 13:14:03 +0000304<p><a name="LLVMDebugVersion">The first field of a descriptor is always an
Nick Lewycky655fd032010-03-31 07:50:17 +0000305 <tt>i32</tt> containing a tag value identifying the content of the
Bill Wendling48839d92009-05-17 05:52:39 +0000306 descriptor. The remaining fields are specific to the descriptor. The values
307 of tags are loosely bound to the tag values of DWARF information entries.
308 However, that does not restrict the use of the information supplied to DWARF
309 targets. To facilitate versioning of debug information, the tag is augmented
Nick Lewycky655fd032010-03-31 07:50:17 +0000310 with the current debug version (LLVMDebugVersion = 8 &lt;&lt; 16 or 0x80000 or
Devang Patel4b945502010-03-09 00:44:10 +0000311 524288.)</a></p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000312
Jim Laskey7089f452006-06-16 13:14:03 +0000313<p>The details of the various descriptors follow.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000314
315</div>
316
317<!-- ======================================================================= -->
318<div class="doc_subsubsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000319 <a name="format_compile_units">Compile unit descriptors</a>
320</div>
321
322<div class="doc_text">
323
Bill Wendling48839d92009-05-17 05:52:39 +0000324<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000325<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000326!0 = metadata !{
327 i32, ;; Tag = 17 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
328 ;; (DW_TAG_compile_unit)
329 i32, ;; Unused field.
330 i32, ;; DWARF language identifier (ex. DW_LANG_C89)
331 metadata, ;; Source file name
332 metadata, ;; Source file directory (includes trailing slash)
333 metadata ;; Producer (ex. "4.0.1 LLVM (LLVM research group)")
334 i1, ;; True if this is a main compile unit.
335 i1, ;; True if this is optimized.
336 metadata, ;; Flags
337 i32 ;; Runtime version
Bill Wendling48839d92009-05-17 05:52:39 +0000338}
Jim Laskeycec12a52006-03-14 18:08:46 +0000339</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000340</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000341
Bill Wendling48839d92009-05-17 05:52:39 +0000342<p>These descriptors contain a source language ID for the file (we use the DWARF
343 3.0 ID numbers, such as <tt>DW_LANG_C89</tt>, <tt>DW_LANG_C_plus_plus</tt>,
344 <tt>DW_LANG_Cobol74</tt>, etc), three strings describing the filename,
345 working directory of the compiler, and an identifier string for the compiler
346 that produced it.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000347
Bill Wendling48839d92009-05-17 05:52:39 +0000348<p>Compile unit descriptors provide the root context for objects declared in a
Devang Patel4b945502010-03-09 00:44:10 +0000349 specific compilation unit. File descriptors are defined using this context.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000350
Devang Patel4b945502010-03-09 00:44:10 +0000351</div>
352
353<!-- ======================================================================= -->
354<div class="doc_subsubsection">
355 <a name="format_files">File descriptors</a>
356</div>
357
358<div class="doc_text">
359
360<div class="doc_code">
361<pre>
362!0 = metadata !{
363 i32, ;; Tag = 41 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
364 ;; (DW_TAG_file_type)
365 metadata, ;; Source file name
366 metadata, ;; Source file directory (includes trailing slash)
367 metadata ;; Reference to compile unit where defined
368}
369</pre>
370</div>
371
John Criswellb34500f2010-03-17 15:01:50 +0000372<p>These descriptors contain information for a file. Global variables and top
Devang Patel4b945502010-03-09 00:44:10 +0000373 level functions would be defined using this context.k File descriptors also
374 provide context for source line correspondence. </p>
375
376<p>Each input file is encoded as a separate file descriptor in LLVM debugging
377 information output. Each file descriptor would be defined using a
378 compile unit. </p>
Bill Wendling48839d92009-05-17 05:52:39 +0000379
Jim Laskeycec12a52006-03-14 18:08:46 +0000380</div>
381
382<!-- ======================================================================= -->
383<div class="doc_subsubsection">
384 <a name="format_global_variables">Global variable descriptors</a>
385</div>
386
387<div class="doc_text">
388
Bill Wendling48839d92009-05-17 05:52:39 +0000389<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000390<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000391!1 = metadata !{
392 i32, ;; Tag = 52 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
393 ;; (DW_TAG_variable)
394 i32, ;; Unused field.
395 metadata, ;; Reference to context descriptor
396 metadata, ;; Name
397 metadata, ;; Display name (fully qualified C++ name)
398 metadata, ;; MIPS linkage name (for C++)
Devang Patel4b945502010-03-09 00:44:10 +0000399 metadata, ;; Reference to file where defined
Devang Patele4b27562009-08-28 23:24:31 +0000400 i32, ;; Line number where defined
401 metadata, ;; Reference to type descriptor
402 i1, ;; True if the global is local to compile unit (static)
403 i1, ;; True if the global is defined in the compile unit (not extern)
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000404 {}* ;; Reference to the global variable
Bill Wendling48839d92009-05-17 05:52:39 +0000405}
Jim Laskeycec12a52006-03-14 18:08:46 +0000406</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000407</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000408
409<p>These descriptors provide debug information about globals variables. The
410provide details such as name, type and where the variable is defined.</p>
411
412</div>
413
414<!-- ======================================================================= -->
415<div class="doc_subsubsection">
416 <a name="format_subprograms">Subprogram descriptors</a>
417</div>
418
419<div class="doc_text">
420
Bill Wendling48839d92009-05-17 05:52:39 +0000421<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000422<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000423!2 = metadata !{
424 i32, ;; Tag = 46 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
425 ;; (DW_TAG_subprogram)
426 i32, ;; Unused field.
427 metadata, ;; Reference to context descriptor
428 metadata, ;; Name
429 metadata, ;; Display name (fully qualified C++ name)
430 metadata, ;; MIPS linkage name (for C++)
Devang Patel4b945502010-03-09 00:44:10 +0000431 metadata, ;; Reference to file where defined
Devang Patele4b27562009-08-28 23:24:31 +0000432 i32, ;; Line number where defined
433 metadata, ;; Reference to type descriptor
434 i1, ;; True if the global is local to compile unit (static)
435 i1 ;; True if the global is defined in the compile unit (not extern)
Devang Patel80ecc152010-06-04 22:49:55 +0000436 i32 ;; Virtuality, e.g. dwarf::DW_VIRTUALITY__virtual
437 i32 ;; Index into a virtual function
438 metadata, ;; indicates which base type contains the vtable pointer for the
439 ;; derived class
440 i1 ;; isArtificial
441 i1 ;; isOptimized
442 Function *;; Pointer to LLVM function
Bill Wendling48839d92009-05-17 05:52:39 +0000443}
Jim Laskeycec12a52006-03-14 18:08:46 +0000444</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000445</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000446
447<p>These descriptors provide debug information about functions, methods and
Bill Wendling48839d92009-05-17 05:52:39 +0000448 subprograms. They provide details such as name, return types and the source
449 location where the subprogram is defined.</p>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000450
451</div>
Bill Wendling48839d92009-05-17 05:52:39 +0000452
Jim Laskey3d11bee2006-03-15 19:10:52 +0000453<!-- ======================================================================= -->
454<div class="doc_subsubsection">
455 <a name="format_blocks">Block descriptors</a>
456</div>
457
458<div class="doc_text">
459
Bill Wendling48839d92009-05-17 05:52:39 +0000460<div class="doc_code">
Jim Laskey3d11bee2006-03-15 19:10:52 +0000461<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000462!3 = metadata !{
Devang Patelc79dda22010-10-04 16:51:59 +0000463 i32, ;; Tag = 11 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_lexical_block)
Devang Patel7f271fc2010-10-01 22:45:00 +0000464 metadata,;; Reference to context descriptor
465 i32, ;; Line number
466 i32 ;; Column number
Bill Wendling48839d92009-05-17 05:52:39 +0000467}
Jim Laskey3d11bee2006-03-15 19:10:52 +0000468</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000469</div>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000470
471<p>These descriptors provide debug information about nested blocks within a
Devang Patel7f271fc2010-10-01 22:45:00 +0000472 subprogram. The line number and column numbers are used to dinstinguish
473 two lexical blocks at same depth. </p>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000474
Jim Laskeycec12a52006-03-14 18:08:46 +0000475</div>
476
477<!-- ======================================================================= -->
478<div class="doc_subsubsection">
479 <a name="format_basic_type">Basic type descriptors</a>
480</div>
481
482<div class="doc_text">
483
Bill Wendling48839d92009-05-17 05:52:39 +0000484<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000485<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000486!4 = metadata !{
487 i32, ;; Tag = 36 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
488 ;; (DW_TAG_base_type)
489 metadata, ;; Reference to context (typically a compile unit)
490 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000491 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000492 i32, ;; Line number where defined (may be 0)
493 i64, ;; Size in bits
494 i64, ;; Alignment in bits
495 i64, ;; Offset in bits
496 i32, ;; Flags
497 i32 ;; DWARF type encoding
Bill Wendling48839d92009-05-17 05:52:39 +0000498}
Jim Laskeycec12a52006-03-14 18:08:46 +0000499</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000500</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000501
502<p>These descriptors define primitive types used in the code. Example int, bool
Bill Wendling48839d92009-05-17 05:52:39 +0000503 and float. The context provides the scope of the type, which is usually the
504 top level. Since basic types are not usually user defined the compile unit
505 and line number can be left as NULL and 0. The size, alignment and offset
506 are expressed in bits and can be 64 bit values. The alignment is used to
507 round the offset when embedded in a
508 <a href="#format_composite_type">composite type</a> (example to keep float
509 doubles on 64 bit boundaries.) The offset is the bit offset if embedded in
510 a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000511
512<p>The type encoding provides the details of the type. The values are typically
Bill Wendling48839d92009-05-17 05:52:39 +0000513 one of the following:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000514
Bill Wendling48839d92009-05-17 05:52:39 +0000515<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000516<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000517DW_ATE_address = 1
518DW_ATE_boolean = 2
519DW_ATE_float = 4
520DW_ATE_signed = 5
521DW_ATE_signed_char = 6
522DW_ATE_unsigned = 7
523DW_ATE_unsigned_char = 8
Jim Laskeycec12a52006-03-14 18:08:46 +0000524</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000525</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000526
527</div>
528
529<!-- ======================================================================= -->
530<div class="doc_subsubsection">
531 <a name="format_derived_type">Derived type descriptors</a>
532</div>
533
534<div class="doc_text">
535
Bill Wendling48839d92009-05-17 05:52:39 +0000536<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000537<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000538!5 = metadata !{
539 i32, ;; Tag (see below)
540 metadata, ;; Reference to context
541 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000542 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000543 i32, ;; Line number where defined (may be 0)
Devang Patel0ffd10b2010-10-01 19:19:30 +0000544 i64, ;; Size in bits
545 i64, ;; Alignment in bits
546 i64, ;; Offset in bits
Devang Patele4b27562009-08-28 23:24:31 +0000547 metadata ;; Reference to type derived from
Bill Wendling48839d92009-05-17 05:52:39 +0000548}
Jim Laskeycec12a52006-03-14 18:08:46 +0000549</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000550</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000551
552<p>These descriptors are used to define types derived from other types. The
553value of the tag varies depending on the meaning. The following are possible
Misha Brukman96e00812008-12-16 02:54:22 +0000554tag values:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000555
Bill Wendling48839d92009-05-17 05:52:39 +0000556<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000557<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000558DW_TAG_formal_parameter = 5
559DW_TAG_member = 13
560DW_TAG_pointer_type = 15
561DW_TAG_reference_type = 16
562DW_TAG_typedef = 22
563DW_TAG_const_type = 38
564DW_TAG_volatile_type = 53
565DW_TAG_restrict_type = 55
Jim Laskeycec12a52006-03-14 18:08:46 +0000566</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000567</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000568
Bill Wendling48839d92009-05-17 05:52:39 +0000569<p><tt>DW_TAG_member</tt> is used to define a member of
570 a <a href="#format_composite_type">composite type</a>
571 or <a href="#format_subprograms">subprogram</a>. The type of the member is
572 the <a href="#format_derived_type">derived
573 type</a>. <tt>DW_TAG_formal_parameter</tt> is used to define a member which
574 is a formal argument of a subprogram.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000575
Bill Wendling48839d92009-05-17 05:52:39 +0000576<p><tt>DW_TAG_typedef</tt> is used to provide a name for the derived type.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000577
Bill Wendling48839d92009-05-17 05:52:39 +0000578<p><tt>DW_TAG_pointer_type</tt>,<tt>DW_TAG_reference_type</tt>,
579 <tt>DW_TAG_const_type</tt>, <tt>DW_TAG_volatile_type</tt>
580 and <tt>DW_TAG_restrict_type</tt> are used to qualify
581 the <a href="#format_derived_type">derived type</a>. </p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000582
583<p><a href="#format_derived_type">Derived type</a> location can be determined
Bill Wendling48839d92009-05-17 05:52:39 +0000584 from the compile unit and line number. The size, alignment and offset are
585 expressed in bits and can be 64 bit values. The alignment is used to round
586 the offset when embedded in a <a href="#format_composite_type">composite
587 type</a> (example to keep float doubles on 64 bit boundaries.) The offset is
588 the bit offset if embedded in a <a href="#format_composite_type">composite
589 type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000590
591<p>Note that the <tt>void *</tt> type is expressed as a
Bill Wendling48839d92009-05-17 05:52:39 +0000592 <tt>llvm.dbg.derivedtype.type</tt> with tag of <tt>DW_TAG_pointer_type</tt>
593 and <tt>NULL</tt> derived type.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000594
595</div>
596
597<!-- ======================================================================= -->
598<div class="doc_subsubsection">
599 <a name="format_composite_type">Composite type descriptors</a>
600</div>
601
602<div class="doc_text">
603
Bill Wendling48839d92009-05-17 05:52:39 +0000604<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000605<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000606!6 = metadata !{
607 i32, ;; Tag (see below)
608 metadata, ;; Reference to context
609 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000610 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000611 i32, ;; Line number where defined (may be 0)
612 i64, ;; Size in bits
613 i64, ;; Alignment in bits
614 i64, ;; Offset in bits
615 i32, ;; Flags
616 metadata, ;; Reference to type derived from
617 metadata, ;; Reference to array of member descriptors
618 i32 ;; Runtime languages
Bill Wendling48839d92009-05-17 05:52:39 +0000619}
Jim Laskeycec12a52006-03-14 18:08:46 +0000620</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000621</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000622
623<p>These descriptors are used to define types that are composed of 0 or more
624elements. The value of the tag varies depending on the meaning. The following
Misha Brukman96e00812008-12-16 02:54:22 +0000625are possible tag values:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000626
Bill Wendling48839d92009-05-17 05:52:39 +0000627<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000628<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000629DW_TAG_array_type = 1
630DW_TAG_enumeration_type = 4
631DW_TAG_structure_type = 19
632DW_TAG_union_type = 23
633DW_TAG_vector_type = 259
Bruno Cardoso Lopesd80ddc02009-05-29 17:08:57 +0000634DW_TAG_subroutine_type = 21
635DW_TAG_inheritance = 28
Jim Laskeycec12a52006-03-14 18:08:46 +0000636</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000637</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000638
Jim Laskeyf8a01a92006-06-15 20:51:43 +0000639<p>The vector flag indicates that an array type is a native packed vector.</p>
640
Jim Laskey7089f452006-06-16 13:14:03 +0000641<p>The members of array types (tag = <tt>DW_TAG_array_type</tt>) or vector types
Bill Wendling48839d92009-05-17 05:52:39 +0000642 (tag = <tt>DW_TAG_vector_type</tt>) are <a href="#format_subrange">subrange
643 descriptors</a>, each representing the range of subscripts at that level of
644 indexing.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000645
646<p>The members of enumeration types (tag = <tt>DW_TAG_enumeration_type</tt>) are
Bill Wendling48839d92009-05-17 05:52:39 +0000647 <a href="#format_enumeration">enumerator descriptors</a>, each representing
648 the definition of enumeration value for the set.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000649
650<p>The members of structure (tag = <tt>DW_TAG_structure_type</tt>) or union (tag
Bill Wendling48839d92009-05-17 05:52:39 +0000651 = <tt>DW_TAG_union_type</tt>) types are any one of
652 the <a href="#format_basic_type">basic</a>,
653 <a href="#format_derived_type">derived</a>
654 or <a href="#format_composite_type">composite</a> type descriptors, each
655 representing a field member of the structure or union.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000656
Jim Laskey4a9df242006-08-21 21:21:06 +0000657<p>For C++ classes (tag = <tt>DW_TAG_structure_type</tt>), member descriptors
Bill Wendling48839d92009-05-17 05:52:39 +0000658 provide information about base classes, static members and member
659 functions. If a member is a <a href="#format_derived_type">derived type
660 descriptor</a> and has a tag of <tt>DW_TAG_inheritance</tt>, then the type
661 represents a base class. If the member of is
662 a <a href="#format_global_variables">global variable descriptor</a> then it
663 represents a static member. And, if the member is
664 a <a href="#format_subprograms">subprogram descriptor</a> then it represents
665 a member function. For static members and member
666 functions, <tt>getName()</tt> returns the members link or the C++ mangled
667 name. <tt>getDisplayName()</tt> the simplied version of the name.</p>
Jim Laskey4a9df242006-08-21 21:21:06 +0000668
Bill Wendling48839d92009-05-17 05:52:39 +0000669<p>The first member of subroutine (tag = <tt>DW_TAG_subroutine_type</tt>) type
670 elements is the return type for the subroutine. The remaining elements are
671 the formal arguments to the subroutine.</p>
Jim Laskey094ee722006-06-20 21:13:20 +0000672
Jim Laskeycec12a52006-03-14 18:08:46 +0000673<p><a href="#format_composite_type">Composite type</a> location can be
Bill Wendling48839d92009-05-17 05:52:39 +0000674 determined from the compile unit and line number. The size, alignment and
675 offset are expressed in bits and can be 64 bit values. The alignment is used
676 to round the offset when embedded in
677 a <a href="#format_composite_type">composite type</a> (as an example, to keep
678 float doubles on 64 bit boundaries.) The offset is the bit offset if embedded
679 in a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000680
681</div>
682
683<!-- ======================================================================= -->
684<div class="doc_subsubsection">
685 <a name="format_subrange">Subrange descriptors</a>
686</div>
687
688<div class="doc_text">
689
Bill Wendling48839d92009-05-17 05:52:39 +0000690<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000691<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000692%<a href="#format_subrange">llvm.dbg.subrange.type</a> = type {
693 i32, ;; Tag = 33 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_subrange_type)
694 i64, ;; Low value
695 i64 ;; High value
696}
Jim Laskeycec12a52006-03-14 18:08:46 +0000697</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000698</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000699
700<p>These descriptors are used to define ranges of array subscripts for an array
Bill Wendling48839d92009-05-17 05:52:39 +0000701 <a href="#format_composite_type">composite type</a>. The low value defines
702 the lower bounds typically zero for C/C++. The high value is the upper
703 bounds. Values are 64 bit. High - low + 1 is the size of the array. If low
704 == high the array will be unbounded.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000705
706</div>
707
708<!-- ======================================================================= -->
709<div class="doc_subsubsection">
710 <a name="format_enumeration">Enumerator descriptors</a>
711</div>
712
713<div class="doc_text">
714
Bill Wendling48839d92009-05-17 05:52:39 +0000715<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000716<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000717!6 = metadata !{
718 i32, ;; Tag = 40 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
719 ;; (DW_TAG_enumerator)
720 metadata, ;; Name
721 i64 ;; Value
Bill Wendling48839d92009-05-17 05:52:39 +0000722}
Jim Laskeycec12a52006-03-14 18:08:46 +0000723</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000724</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000725
Bill Wendling48839d92009-05-17 05:52:39 +0000726<p>These descriptors are used to define members of an
727 enumeration <a href="#format_composite_type">composite type</a>, it
728 associates the name to the value.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000729
730</div>
731
732<!-- ======================================================================= -->
Jim Laskey383e0092006-03-23 17:54:33 +0000733<div class="doc_subsubsection">
734 <a name="format_variables">Local variables</a>
735</div>
736
737<div class="doc_text">
Bill Wendling48839d92009-05-17 05:52:39 +0000738
739<div class="doc_code">
Jim Laskey383e0092006-03-23 17:54:33 +0000740<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000741!7 = metadata !{
742 i32, ;; Tag (see below)
743 metadata, ;; Context
744 metadata, ;; Name
Devang Patel4b945502010-03-09 00:44:10 +0000745 metadata, ;; Reference to file where defined
Devang Patele4b27562009-08-28 23:24:31 +0000746 i32, ;; Line number where defined
747 metadata ;; Type descriptor
Bill Wendling48839d92009-05-17 05:52:39 +0000748}
Jim Laskey383e0092006-03-23 17:54:33 +0000749</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000750</div>
Jim Laskey383e0092006-03-23 17:54:33 +0000751
752<p>These descriptors are used to define variables local to a sub program. The
Bill Wendling48839d92009-05-17 05:52:39 +0000753 value of the tag depends on the usage of the variable:</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000754
Bill Wendling48839d92009-05-17 05:52:39 +0000755<div class="doc_code">
Jim Laskey383e0092006-03-23 17:54:33 +0000756<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000757DW_TAG_auto_variable = 256
758DW_TAG_arg_variable = 257
759DW_TAG_return_variable = 258
Jim Laskey383e0092006-03-23 17:54:33 +0000760</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000761</div>
Jim Laskey383e0092006-03-23 17:54:33 +0000762
763<p>An auto variable is any variable declared in the body of the function. An
Bill Wendling48839d92009-05-17 05:52:39 +0000764 argument variable is any variable that appears as a formal argument to the
765 function. A return variable is used to track the result of a function and
766 has no source correspondent.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000767
Jim Laskey2d395d92006-03-24 09:20:27 +0000768<p>The context is either the subprogram or block where the variable is defined.
Bill Wendling48839d92009-05-17 05:52:39 +0000769 Name the source variable name. Compile unit and line indicate where the
770 variable was defined. Type descriptor defines the declared type of the
771 variable.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000772
773</div>
774
775<!-- ======================================================================= -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000776<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000777 <a name="format_common_intrinsics">Debugger intrinsic functions</a>
778</div>
779
780<div class="doc_text">
781
782<p>LLVM uses several intrinsic functions (name prefixed with "llvm.dbg") to
Bill Wendling48839d92009-05-17 05:52:39 +0000783 provide debug information at various points in generated code.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000784
785</div>
786
787<!-- ======================================================================= -->
788<div class="doc_subsubsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000789 <a name="format_common_declare">llvm.dbg.declare</a>
790</div>
791
792<div class="doc_text">
793<pre>
Devang Patel4c7c0c62010-10-01 19:22:16 +0000794 void %<a href="#format_common_declare">llvm.dbg.declare</a>(metadata, metadata)
Jim Laskeycec12a52006-03-14 18:08:46 +0000795</pre>
796
Jim Laskey2d395d92006-03-24 09:20:27 +0000797<p>This intrinsic provides information about a local element (ex. variable.) The
Devang Patel4c7c0c62010-10-01 19:22:16 +0000798 first argument is metadata holding alloca for the variable.</tt>. The
Bill Wendling48839d92009-05-17 05:52:39 +0000799 second argument is
800 the <tt>%<a href="#format_variables">llvm.dbg.variable</a></tt> containing
Devang Patele4b27562009-08-28 23:24:31 +0000801 the description of the variable. </p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000802
803</div>
804
805<!-- ======================================================================= -->
Victor Hernandez67a1a542010-01-11 22:53:48 +0000806<div class="doc_subsubsection">
807 <a name="format_common_value">llvm.dbg.value</a>
808</div>
809
810<div class="doc_text">
811<pre>
Dan Gohman3dfb3cf2010-05-28 17:07:41 +0000812 void %<a href="#format_common_value">llvm.dbg.value</a>(metadata, i64, metadata)
Victor Hernandez67a1a542010-01-11 22:53:48 +0000813</pre>
814
815<p>This intrinsic provides information when a user source variable is set to a
816 new value. The first argument is the new value (wrapped as metadata). The
817 second argument is the offset in the user source variable where the new value
818 is written. The third argument is
819 the <tt>%<a href="#format_variables">llvm.dbg.variable</a></tt> containing
820 the description of the user source variable. </p>
821
822</div>
823
824<!-- ======================================================================= -->
Jim Laskeycec12a52006-03-14 18:08:46 +0000825<div class="doc_subsection">
Chris Lattner8ff75902004-01-06 05:31:32 +0000826 <a name="format_common_lifetime">Object lifetimes and scoping</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000827</div>
828
829<div class="doc_text">
Bill Wendlingcf493b82009-12-01 00:53:11 +0000830<p>In many languages, the local variables in functions can have their lifetimes
831 or scopes limited to a subset of a function. In the C family of languages,
Bill Wendling48839d92009-05-17 05:52:39 +0000832 for example, variables are only live (readable and writable) within the
833 source block that they are defined in. In functional languages, values are
834 only readable after they have been defined. Though this is a very obvious
Bill Wendlingcf493b82009-12-01 00:53:11 +0000835 concept, it is non-trivial to model in LLVM, because it has no notion of
Bill Wendling48839d92009-05-17 05:52:39 +0000836 scoping in this sense, and does not want to be tied to a language's scoping
837 rules.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000838
Bill Wendlingcf493b82009-12-01 00:53:11 +0000839<p>In order to handle this, the LLVM debug format uses the metadata attached to
Nick Lewycky655fd032010-03-31 07:50:17 +0000840 llvm instructions to encode line number and scoping information. Consider
841 the following C fragment, for example:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000842
Bill Wendling48839d92009-05-17 05:52:39 +0000843<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000844<pre>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008451. void foo() {
Devang Patel744950d2009-11-25 23:28:01 +00008462. int X = 21;
8473. int Y = 22;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008484. {
Devang Patel744950d2009-11-25 23:28:01 +00008495. int Z = 23;
8506. Z = X;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008517. }
Devang Patel744950d2009-11-25 23:28:01 +00008528. X = Y;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008539. }
Misha Brukman82873732004-05-12 19:21:57 +0000854</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000855</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000856
Jim Laskeycec12a52006-03-14 18:08:46 +0000857<p>Compiled to LLVM, this function would be represented like this:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000858
Bill Wendling48839d92009-05-17 05:52:39 +0000859<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000860<pre>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000861define void @foo() nounwind ssp {
Jim Laskeycec12a52006-03-14 18:08:46 +0000862entry:
Bill Wendling02216ff2009-12-01 00:59:58 +0000863 %X = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
864 %Y = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
865 %Z = alloca i32, align 4 ; &lt;i32*&gt; [#uses=3]
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000866 %0 = bitcast i32* %X to {}* ; &lt;{}*&gt; [#uses=1]
867 call void @llvm.dbg.declare({}* %0, metadata !0), !dbg !7
Devang Patel744950d2009-11-25 23:28:01 +0000868 store i32 21, i32* %X, !dbg !8
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000869 %1 = bitcast i32* %Y to {}* ; &lt;{}*&gt; [#uses=1]
870 call void @llvm.dbg.declare({}* %1, metadata !9), !dbg !10
Devang Patel744950d2009-11-25 23:28:01 +0000871 store i32 22, i32* %Y, !dbg !11
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000872 %2 = bitcast i32* %Z to {}* ; &lt;{}*&gt; [#uses=1]
873 call void @llvm.dbg.declare({}* %2, metadata !12), !dbg !14
Devang Patel744950d2009-11-25 23:28:01 +0000874 store i32 23, i32* %Z, !dbg !15
Bill Wendling02216ff2009-12-01 00:59:58 +0000875 %tmp = load i32* %X, !dbg !16 ; &lt;i32&gt; [#uses=1]
876 %tmp1 = load i32* %Y, !dbg !16 ; &lt;i32&gt; [#uses=1]
877 %add = add nsw i32 %tmp, %tmp1, !dbg !16 ; &lt;i32&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000878 store i32 %add, i32* %Z, !dbg !16
Bill Wendling02216ff2009-12-01 00:59:58 +0000879 %tmp2 = load i32* %Y, !dbg !17 ; &lt;i32&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000880 store i32 %tmp2, i32* %X, !dbg !17
881 ret void, !dbg !18
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000882}
Devang Patel744950d2009-11-25 23:28:01 +0000883
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000884declare void @llvm.dbg.declare({}*, metadata) nounwind readnone
Devang Patel744950d2009-11-25 23:28:01 +0000885
886!0 = metadata !{i32 459008, metadata !1, metadata !"X",
887 metadata !3, i32 2, metadata !6}; [ DW_TAG_auto_variable ]
888!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
889!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo", metadata !"foo",
890 metadata !"foo", metadata !3, i32 1, metadata !4,
891 i1 false, i1 true}; [DW_TAG_subprogram ]
892!3 = metadata !{i32 458769, i32 0, i32 12, metadata !"foo.c",
893 metadata !"/private/tmp", metadata !"clang 1.1", i1 true,
894 i1 false, metadata !"", i32 0}; [DW_TAG_compile_unit ]
895!4 = metadata !{i32 458773, metadata !3, metadata !"", null, i32 0, i64 0, i64 0,
896 i64 0, i32 0, null, metadata !5, i32 0}; [DW_TAG_subroutine_type ]
897!5 = metadata !{null}
898!6 = metadata !{i32 458788, metadata !3, metadata !"int", metadata !3, i32 0,
899 i64 32, i64 32, i64 0, i32 0, i32 5}; [DW_TAG_base_type ]
900!7 = metadata !{i32 2, i32 7, metadata !1, null}
901!8 = metadata !{i32 2, i32 3, metadata !1, null}
902!9 = metadata !{i32 459008, metadata !1, metadata !"Y", metadata !3, i32 3,
903 metadata !6}; [ DW_TAG_auto_variable ]
904!10 = metadata !{i32 3, i32 7, metadata !1, null}
905!11 = metadata !{i32 3, i32 3, metadata !1, null}
906!12 = metadata !{i32 459008, metadata !13, metadata !"Z", metadata !3, i32 5,
907 metadata !6}; [ DW_TAG_auto_variable ]
908!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
909!14 = metadata !{i32 5, i32 9, metadata !13, null}
910!15 = metadata !{i32 5, i32 5, metadata !13, null}
911!16 = metadata !{i32 6, i32 5, metadata !13, null}
912!17 = metadata !{i32 8, i32 3, metadata !1, null}
913!18 = metadata !{i32 9, i32 1, metadata !2, null}
Misha Brukman82873732004-05-12 19:21:57 +0000914</pre>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000915</div>
916
Bill Wendlingcf493b82009-12-01 00:53:11 +0000917<p>This example illustrates a few important details about LLVM debugging
918 information. In particular, it shows how the <tt>llvm.dbg.declare</tt>
919 intrinsic and location information, which are attached to an instruction,
920 are applied together to allow a debugger to analyze the relationship between
921 statements, variable definitions, and the code used to implement the
922 function.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000923
Bill Wendlingcf493b82009-12-01 00:53:11 +0000924<div class="doc_code">
Bill Wendling02216ff2009-12-01 00:59:58 +0000925<pre>
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000926call void @llvm.dbg.declare({}* %0, metadata !0), !dbg !7
Bill Wendlingcf493b82009-12-01 00:53:11 +0000927</pre>
928</div>
929
930<p>The first intrinsic
Devang Patel744950d2009-11-25 23:28:01 +0000931 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000932 encodes debugging information for the variable <tt>X</tt>. The metadata
933 <tt>!dbg !7</tt> attached to the intrinsic provides scope information for the
934 variable <tt>X</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000935
Bill Wendlingcf493b82009-12-01 00:53:11 +0000936<div class="doc_code">
937<pre>
938!7 = metadata !{i32 2, i32 7, metadata !1, null}
939!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
940!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo",
941 metadata !"foo", metadata !"foo", metadata !3, i32 1,
942 metadata !4, i1 false, i1 true}; [DW_TAG_subprogram ]
943</pre>
944</div>
945
946<p>Here <tt>!7</tt> is metadata providing location information. It has four
947 fields: line number, column number, scope, and original scope. The original
948 scope represents inline location if this instruction is inlined inside a
949 caller, and is null otherwise. In this example, scope is encoded by
Devang Patel744950d2009-11-25 23:28:01 +0000950 <tt>!1</tt>. <tt>!1</tt> represents a lexical block inside the scope
951 <tt>!2</tt>, where <tt>!2</tt> is a
Bill Wendlingcf493b82009-12-01 00:53:11 +0000952 <a href="#format_subprograms">subprogram descriptor</a>. This way the
953 location information attached to the intrinsics indicates that the
954 variable <tt>X</tt> is declared at line number 2 at a function level scope in
955 function <tt>foo</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000956
Devang Patel744950d2009-11-25 23:28:01 +0000957<p>Now lets take another example.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000958
Bill Wendlingcf493b82009-12-01 00:53:11 +0000959<div class="doc_code">
Bill Wendling02216ff2009-12-01 00:59:58 +0000960<pre>
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000961call void @llvm.dbg.declare({}* %2, metadata !12), !dbg !14
Bill Wendlingcf493b82009-12-01 00:53:11 +0000962</pre>
963</div>
964
965<p>The second intrinsic
Devang Patel744950d2009-11-25 23:28:01 +0000966 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000967 encodes debugging information for variable <tt>Z</tt>. The metadata
968 <tt>!dbg !14</tt> attached to the intrinsic provides scope information for
969 the variable <tt>Z</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000970
Bill Wendlingcf493b82009-12-01 00:53:11 +0000971<div class="doc_code">
972<pre>
973!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
974!14 = metadata !{i32 5, i32 9, metadata !13, null}
975</pre>
976</div>
Bill Wendling48839d92009-05-17 05:52:39 +0000977
John Criswellb34500f2010-03-17 15:01:50 +0000978<p>Here <tt>!14</tt> indicates that <tt>Z</tt> is declared at line number 5 and
Bill Wendlingcf493b82009-12-01 00:53:11 +0000979 column number 9 inside of lexical scope <tt>!13</tt>. The lexical scope
980 itself resides inside of lexical scope <tt>!1</tt> described above.</p>
981
982<p>The scope information attached with each instruction provides a
983 straightforward way to find instructions covered by a scope.</p>
984
Bill Wendling48839d92009-05-17 05:52:39 +0000985</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000986
987<!-- *********************************************************************** -->
988<div class="doc_section">
Chris Lattner8ff75902004-01-06 05:31:32 +0000989 <a name="ccxx_frontend">C/C++ front-end specific debug information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000990</div>
Misha Brukman94218a72004-12-09 20:27:37 +0000991<!-- *********************************************************************** -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000992
993<div class="doc_text">
994
Misha Brukman82873732004-05-12 19:21:57 +0000995<p>The C and C++ front-ends represent information about the program in a format
Bill Wendling48839d92009-05-17 05:52:39 +0000996 that is effectively identical
997 to <a href="http://www.eagercon.com/dwarf/dwarf3std.htm">DWARF 3.0</a> in
998 terms of information content. This allows code generators to trivially
999 support native debuggers by generating standard dwarf information, and
1000 contains enough information for non-dwarf targets to translate it as
1001 needed.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001002
Jim Laskeycec12a52006-03-14 18:08:46 +00001003<p>This section describes the forms used to represent C and C++ programs. Other
Bill Wendling48839d92009-05-17 05:52:39 +00001004 languages could pattern themselves after this (which itself is tuned to
1005 representing programs in the same way that DWARF 3 does), or they could
1006 choose to provide completely different forms if they don't fit into the DWARF
1007 model. As support for debugging information gets added to the various LLVM
1008 source-language front-ends, the information used should be documented
1009 here.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001010
Jim Laskeycec12a52006-03-14 18:08:46 +00001011<p>The following sections provide examples of various C/C++ constructs and the
Bill Wendling48839d92009-05-17 05:52:39 +00001012 debug information that would best describe those constructs.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001013
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001014</div>
1015
1016<!-- ======================================================================= -->
1017<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +00001018 <a name="ccxx_compile_units">C/C++ source file information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001019</div>
1020
1021<div class="doc_text">
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001022
Bill Wendling48839d92009-05-17 05:52:39 +00001023<p>Given the source files <tt>MySource.cpp</tt> and <tt>MyHeader.h</tt> located
1024 in the directory <tt>/Users/mine/sources</tt>, the following code:</p>
Chris Lattner8ff75902004-01-06 05:31:32 +00001025
Bill Wendling48839d92009-05-17 05:52:39 +00001026<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001027<pre>
1028#include "MyHeader.h"
Chris Lattner8ff75902004-01-06 05:31:32 +00001029
Jim Laskeycec12a52006-03-14 18:08:46 +00001030int main(int argc, char *argv[]) {
1031 return 0;
1032}
1033</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001034</div>
Chris Lattner8ff75902004-01-06 05:31:32 +00001035
Misha Brukman96e00812008-12-16 02:54:22 +00001036<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001037
Bill Wendling48839d92009-05-17 05:52:39 +00001038<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001039<pre>
1040...
1041;;
Devang Patel4b945502010-03-09 00:44:10 +00001042;; Define the compile unit for the main source file "/Users/mine/sources/MySource.cpp".
Jim Laskeycec12a52006-03-14 18:08:46 +00001043;;
Devang Patel4b945502010-03-09 00:44:10 +00001044!2 = metadata !{
1045 i32 524305, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001046 i32 0, ;; Unused
1047 i32 4, ;; Language Id
1048 metadata !"MySource.cpp",
1049 metadata !"/Users/mine/sources",
1050 metadata !"4.2.1 (Based on Apple Inc. build 5649) (LLVM build 00)",
1051 i1 true, ;; Main Compile Unit
1052 i1 false, ;; Optimized compile unit
1053 metadata !"", ;; Compiler flags
1054 i32 0} ;; Runtime version
1055
Jim Laskeycec12a52006-03-14 18:08:46 +00001056;;
Devang Patel4b945502010-03-09 00:44:10 +00001057;; Define the file for the file "/Users/mine/sources/MySource.cpp".
Jim Laskeycec12a52006-03-14 18:08:46 +00001058;;
Devang Patele4b27562009-08-28 23:24:31 +00001059!1 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001060 i32 524329, ;; Tag
1061 metadata !"MySource.cpp",
Devang Patele4b27562009-08-28 23:24:31 +00001062 metadata !"/Users/mine/sources",
Devang Patel9fea9c22010-07-13 16:53:20 +00001063 metadata !2 ;; Compile unit
Devang Patel4b945502010-03-09 00:44:10 +00001064}
1065
1066;;
1067;; Define the file for the file "/Users/mine/sources/Myheader.h"
1068;;
1069!3 = metadata !{
1070 i32 524329, ;; Tag
1071 metadata !"Myheader.h"
1072 metadata !"/Users/mine/sources",
Devang Patel9fea9c22010-07-13 16:53:20 +00001073 metadata !2 ;; Compile unit
Devang Patel4b945502010-03-09 00:44:10 +00001074}
Jim Laskeycec12a52006-03-14 18:08:46 +00001075
Jim Laskeycec12a52006-03-14 18:08:46 +00001076...
1077</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001078</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001079
Devang Pateld98ec5f2010-03-26 19:08:36 +00001080<p>llvm::Instruction provides easy access to metadata attached with an
1081instruction. One can extract line number information encoded in LLVM IR
1082using <tt>Instruction::getMetadata()</tt> and
1083<tt>DILocation::getLineNumber()</tt>.
1084<pre>
1085 if (MDNode *N = I->getMetadata("dbg")) { // Here I is an LLVM instruction
1086 DILocation Loc(N); // DILocation is in DebugInfo.h
1087 unsigned Line = Loc.getLineNumber();
1088 StringRef File = Loc.getFilename();
1089 StringRef Dir = Loc.getDirectory();
1090 }
1091</pre>
Chris Lattner8ff75902004-01-06 05:31:32 +00001092</div>
1093
1094<!-- ======================================================================= -->
1095<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +00001096 <a name="ccxx_global_variable">C/C++ global variable information</a>
Chris Lattner8ff75902004-01-06 05:31:32 +00001097</div>
1098
1099<div class="doc_text">
Jim Laskeycec12a52006-03-14 18:08:46 +00001100
Misha Brukman96e00812008-12-16 02:54:22 +00001101<p>Given an integer global variable declared as follows:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001102
Bill Wendling48839d92009-05-17 05:52:39 +00001103<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001104<pre>
1105int MyGlobal = 100;
1106</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001107</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001108
Misha Brukman96e00812008-12-16 02:54:22 +00001109<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001110
Bill Wendling48839d92009-05-17 05:52:39 +00001111<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001112<pre>
1113;;
Jim Laskeycec12a52006-03-14 18:08:46 +00001114;; Define the global itself.
1115;;
1116%MyGlobal = global int 100
1117...
1118;;
Devang Patele4b27562009-08-28 23:24:31 +00001119;; List of debug info of globals
Jim Laskeycec12a52006-03-14 18:08:46 +00001120;;
Devang Patele4b27562009-08-28 23:24:31 +00001121!llvm.dbg.gv = !{!0}
Jim Laskeycec12a52006-03-14 18:08:46 +00001122
1123;;
1124;; Define the global variable descriptor. Note the reference to the global
1125;; variable anchor and the global variable itself.
1126;;
Devang Patele4b27562009-08-28 23:24:31 +00001127!0 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001128 i32 524340, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001129 i32 0, ;; Unused
1130 metadata !1, ;; Context
1131 metadata !"MyGlobal", ;; Name
1132 metadata !"MyGlobal", ;; Display Name
1133 metadata !"MyGlobal", ;; Linkage Name
Devang Patel4b945502010-03-09 00:44:10 +00001134 metadata !3, ;; Compile Unit
Devang Patele4b27562009-08-28 23:24:31 +00001135 i32 1, ;; Line Number
Devang Patel4b945502010-03-09 00:44:10 +00001136 metadata !4, ;; Type
Devang Patele4b27562009-08-28 23:24:31 +00001137 i1 false, ;; Is a local variable
1138 i1 true, ;; Is this a definition
1139 i32* @MyGlobal ;; The global variable
1140}
1141
Jim Laskeycec12a52006-03-14 18:08:46 +00001142;;
1143;; Define the basic type of 32 bit signed integer. Note that since int is an
1144;; intrinsic type the source file is NULL and line 0.
1145;;
Devang Patel4b945502010-03-09 00:44:10 +00001146!4 = metadata !{
1147 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001148 metadata !1, ;; Context
1149 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001150 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001151 i32 0, ;; Line number
1152 i64 32, ;; Size in Bits
1153 i64 32, ;; Align in Bits
1154 i64 0, ;; Offset in Bits
1155 i32 0, ;; Flags
1156 i32 5 ;; Encoding
1157}
Jim Laskeycec12a52006-03-14 18:08:46 +00001158
Jim Laskeycec12a52006-03-14 18:08:46 +00001159</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001160</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001161
Chris Lattner8ff75902004-01-06 05:31:32 +00001162</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001163
Jim Laskeycec12a52006-03-14 18:08:46 +00001164<!-- ======================================================================= -->
1165<div class="doc_subsection">
1166 <a name="ccxx_subprogram">C/C++ function information</a>
1167</div>
1168
1169<div class="doc_text">
1170
Misha Brukman96e00812008-12-16 02:54:22 +00001171<p>Given a function declared as follows:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001172
Bill Wendling48839d92009-05-17 05:52:39 +00001173<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001174<pre>
1175int main(int argc, char *argv[]) {
1176 return 0;
1177}
1178</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001179</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001180
Misha Brukman96e00812008-12-16 02:54:22 +00001181<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001182
Bill Wendling48839d92009-05-17 05:52:39 +00001183<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001184<pre>
1185;;
Jim Laskeycec12a52006-03-14 18:08:46 +00001186;; Define the anchor for subprograms. Note that the second field of the
1187;; anchor is 46, which is the same as the tag for subprograms
1188;; (46 = DW_TAG_subprogram.)
1189;;
Devang Patel4b945502010-03-09 00:44:10 +00001190!6 = metadata !{
1191 i32 524334, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001192 i32 0, ;; Unused
1193 metadata !1, ;; Context
1194 metadata !"main", ;; Name
1195 metadata !"main", ;; Display name
1196 metadata !"main", ;; Linkage name
Devang Patel4b945502010-03-09 00:44:10 +00001197 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001198 i32 1, ;; Line number
Devang Patel4b945502010-03-09 00:44:10 +00001199 metadata !4, ;; Type
Devang Patele4b27562009-08-28 23:24:31 +00001200 i1 false, ;; Is local
1201 i1 true ;; Is definition
1202}
Jim Laskeycec12a52006-03-14 18:08:46 +00001203;;
1204;; Define the subprogram itself.
1205;;
Devang Patele4b27562009-08-28 23:24:31 +00001206define i32 @main(i32 %argc, i8** %argv) {
Jim Laskeycec12a52006-03-14 18:08:46 +00001207...
1208}
1209</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001210</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001211
1212</div>
1213
1214<!-- ======================================================================= -->
1215<div class="doc_subsection">
1216 <a name="ccxx_basic_types">C/C++ basic types</a>
1217</div>
1218
1219<div class="doc_text">
1220
Misha Brukman96e00812008-12-16 02:54:22 +00001221<p>The following are the basic type descriptors for C/C++ core types:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001222
1223</div>
1224
1225<!-- ======================================================================= -->
1226<div class="doc_subsubsection">
1227 <a name="ccxx_basic_type_bool">bool</a>
1228</div>
1229
1230<div class="doc_text">
1231
Bill Wendling48839d92009-05-17 05:52:39 +00001232<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001233<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001234!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001235 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001236 metadata !1, ;; Context
1237 metadata !"bool", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001238 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001239 i32 0, ;; Line number
1240 i64 8, ;; Size in Bits
1241 i64 8, ;; Align in Bits
1242 i64 0, ;; Offset in Bits
1243 i32 0, ;; Flags
1244 i32 2 ;; Encoding
1245}
Jim Laskeycec12a52006-03-14 18:08:46 +00001246</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001247</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001248
1249</div>
1250
1251<!-- ======================================================================= -->
1252<div class="doc_subsubsection">
1253 <a name="ccxx_basic_char">char</a>
1254</div>
1255
1256<div class="doc_text">
1257
Bill Wendling48839d92009-05-17 05:52:39 +00001258<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001259<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001260!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001261 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001262 metadata !1, ;; Context
1263 metadata !"char", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001264 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001265 i32 0, ;; Line number
1266 i64 8, ;; Size in Bits
1267 i64 8, ;; Align in Bits
1268 i64 0, ;; Offset in Bits
1269 i32 0, ;; Flags
1270 i32 6 ;; Encoding
1271}
Jim Laskeycec12a52006-03-14 18:08:46 +00001272</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001273</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001274
1275</div>
1276
1277<!-- ======================================================================= -->
1278<div class="doc_subsubsection">
1279 <a name="ccxx_basic_unsigned_char">unsigned char</a>
1280</div>
1281
1282<div class="doc_text">
1283
Bill Wendling48839d92009-05-17 05:52:39 +00001284<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001285<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001286!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001287 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001288 metadata !1, ;; Context
1289 metadata !"unsigned char",
Devang Patel4b945502010-03-09 00:44:10 +00001290 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001291 i32 0, ;; Line number
1292 i64 8, ;; Size in Bits
1293 i64 8, ;; Align in Bits
1294 i64 0, ;; Offset in Bits
1295 i32 0, ;; Flags
1296 i32 8 ;; Encoding
1297}
Jim Laskeycec12a52006-03-14 18:08:46 +00001298</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001299</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001300
1301</div>
1302
1303<!-- ======================================================================= -->
1304<div class="doc_subsubsection">
1305 <a name="ccxx_basic_short">short</a>
1306</div>
1307
1308<div class="doc_text">
1309
Bill Wendling48839d92009-05-17 05:52:39 +00001310<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001311<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001312!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001313 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001314 metadata !1, ;; Context
1315 metadata !"short int",
Devang Patel4b945502010-03-09 00:44:10 +00001316 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001317 i32 0, ;; Line number
1318 i64 16, ;; Size in Bits
1319 i64 16, ;; Align in Bits
1320 i64 0, ;; Offset in Bits
1321 i32 0, ;; Flags
1322 i32 5 ;; Encoding
1323}
Jim Laskeycec12a52006-03-14 18:08:46 +00001324</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001325</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001326
1327</div>
1328
1329<!-- ======================================================================= -->
1330<div class="doc_subsubsection">
1331 <a name="ccxx_basic_unsigned_short">unsigned short</a>
1332</div>
1333
1334<div class="doc_text">
1335
Bill Wendling48839d92009-05-17 05:52:39 +00001336<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001337<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001338!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001339 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001340 metadata !1, ;; Context
1341 metadata !"short unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001342 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001343 i32 0, ;; Line number
1344 i64 16, ;; Size in Bits
1345 i64 16, ;; Align in Bits
1346 i64 0, ;; Offset in Bits
1347 i32 0, ;; Flags
1348 i32 7 ;; Encoding
1349}
Jim Laskeycec12a52006-03-14 18:08:46 +00001350</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001351</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001352
1353</div>
1354
1355<!-- ======================================================================= -->
1356<div class="doc_subsubsection">
1357 <a name="ccxx_basic_int">int</a>
1358</div>
1359
1360<div class="doc_text">
1361
Bill Wendling48839d92009-05-17 05:52:39 +00001362<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001363<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001364!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001365 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001366 metadata !1, ;; Context
1367 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001368 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001369 i32 0, ;; Line number
1370 i64 32, ;; Size in Bits
1371 i64 32, ;; Align in Bits
1372 i64 0, ;; Offset in Bits
1373 i32 0, ;; Flags
1374 i32 5 ;; Encoding
1375}
Bill Wendling48839d92009-05-17 05:52:39 +00001376</pre></div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001377
1378</div>
1379
1380<!-- ======================================================================= -->
1381<div class="doc_subsubsection">
1382 <a name="ccxx_basic_unsigned_int">unsigned int</a>
1383</div>
1384
1385<div class="doc_text">
1386
Bill Wendling48839d92009-05-17 05:52:39 +00001387<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001388<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001389!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001390 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001391 metadata !1, ;; Context
1392 metadata !"unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001393 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001394 i32 0, ;; Line number
1395 i64 32, ;; Size in Bits
1396 i64 32, ;; Align in Bits
1397 i64 0, ;; Offset in Bits
1398 i32 0, ;; Flags
1399 i32 7 ;; Encoding
1400}
Jim Laskeycec12a52006-03-14 18:08:46 +00001401</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001402</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001403
1404</div>
1405
1406<!-- ======================================================================= -->
1407<div class="doc_subsubsection">
1408 <a name="ccxx_basic_long_long">long long</a>
1409</div>
1410
1411<div class="doc_text">
1412
Bill Wendling48839d92009-05-17 05:52:39 +00001413<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001414<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001415!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001416 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001417 metadata !1, ;; Context
1418 metadata !"long long int",
Devang Patel4b945502010-03-09 00:44:10 +00001419 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001420 i32 0, ;; Line number
1421 i64 64, ;; Size in Bits
1422 i64 64, ;; Align in Bits
1423 i64 0, ;; Offset in Bits
1424 i32 0, ;; Flags
1425 i32 5 ;; Encoding
1426}
Jim Laskeycec12a52006-03-14 18:08:46 +00001427</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001428</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001429
1430</div>
1431
1432<!-- ======================================================================= -->
1433<div class="doc_subsubsection">
1434 <a name="ccxx_basic_unsigned_long_long">unsigned long long</a>
1435</div>
1436
1437<div class="doc_text">
1438
Bill Wendling48839d92009-05-17 05:52:39 +00001439<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001440<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001441!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001442 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001443 metadata !1, ;; Context
1444 metadata !"long long unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001445 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001446 i32 0, ;; Line number
1447 i64 64, ;; Size in Bits
1448 i64 64, ;; Align in Bits
1449 i64 0, ;; Offset in Bits
1450 i32 0, ;; Flags
1451 i32 7 ;; Encoding
1452}
Jim Laskeycec12a52006-03-14 18:08:46 +00001453</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001454</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001455
1456</div>
1457
1458<!-- ======================================================================= -->
1459<div class="doc_subsubsection">
1460 <a name="ccxx_basic_float">float</a>
1461</div>
1462
1463<div class="doc_text">
1464
Bill Wendling48839d92009-05-17 05:52:39 +00001465<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001466<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001467!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001468 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001469 metadata !1, ;; Context
1470 metadata !"float",
Devang Patel4b945502010-03-09 00:44:10 +00001471 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001472 i32 0, ;; Line number
1473 i64 32, ;; Size in Bits
1474 i64 32, ;; Align in Bits
1475 i64 0, ;; Offset in Bits
1476 i32 0, ;; Flags
1477 i32 4 ;; Encoding
1478}
Jim Laskeycec12a52006-03-14 18:08:46 +00001479</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001480</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001481
1482</div>
1483
1484<!-- ======================================================================= -->
1485<div class="doc_subsubsection">
1486 <a name="ccxx_basic_double">double</a>
1487</div>
1488
1489<div class="doc_text">
1490
Bill Wendling48839d92009-05-17 05:52:39 +00001491<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001492<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001493!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001494 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001495 metadata !1, ;; Context
1496 metadata !"double",;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001497 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001498 i32 0, ;; Line number
1499 i64 64, ;; Size in Bits
1500 i64 64, ;; Align in Bits
1501 i64 0, ;; Offset in Bits
1502 i32 0, ;; Flags
1503 i32 4 ;; Encoding
1504}
Jim Laskeycec12a52006-03-14 18:08:46 +00001505</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001506</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001507
1508</div>
1509
1510<!-- ======================================================================= -->
1511<div class="doc_subsection">
1512 <a name="ccxx_derived_types">C/C++ derived types</a>
1513</div>
1514
1515<div class="doc_text">
1516
Misha Brukman96e00812008-12-16 02:54:22 +00001517<p>Given the following as an example of C/C++ derived type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001518
Bill Wendling48839d92009-05-17 05:52:39 +00001519<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001520<pre>
1521typedef const int *IntPtr;
1522</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001523</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001524
Misha Brukman96e00812008-12-16 02:54:22 +00001525<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001526
Bill Wendling48839d92009-05-17 05:52:39 +00001527<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001528<pre>
1529;;
1530;; Define the typedef "IntPtr".
1531;;
Devang Patele4b27562009-08-28 23:24:31 +00001532!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001533 i32 524310, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001534 metadata !1, ;; Context
1535 metadata !"IntPtr", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001536 metadata !3, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001537 i32 0, ;; Line number
1538 i64 0, ;; Size in bits
1539 i64 0, ;; Align in bits
1540 i64 0, ;; Offset in bits
1541 i32 0, ;; Flags
1542 metadata !4 ;; Derived From type
1543}
Jim Laskeycec12a52006-03-14 18:08:46 +00001544
1545;;
1546;; Define the pointer type.
1547;;
Devang Patele4b27562009-08-28 23:24:31 +00001548!4 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001549 i32 524303, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001550 metadata !1, ;; Context
1551 metadata !"", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001552 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001553 i32 0, ;; Line number
1554 i64 64, ;; Size in bits
1555 i64 64, ;; Align in bits
1556 i64 0, ;; Offset in bits
1557 i32 0, ;; Flags
1558 metadata !5 ;; Derived From type
1559}
Jim Laskeycec12a52006-03-14 18:08:46 +00001560;;
1561;; Define the const type.
1562;;
Devang Patele4b27562009-08-28 23:24:31 +00001563!5 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001564 i32 524326, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001565 metadata !1, ;; Context
1566 metadata !"", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001567 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001568 i32 0, ;; Line number
1569 i64 32, ;; Size in bits
1570 i64 32, ;; Align in bits
1571 i64 0, ;; Offset in bits
1572 i32 0, ;; Flags
1573 metadata !6 ;; Derived From type
1574}
Jim Laskeycec12a52006-03-14 18:08:46 +00001575;;
1576;; Define the int type.
1577;;
Devang Patele4b27562009-08-28 23:24:31 +00001578!6 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001579 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001580 metadata !1, ;; Context
1581 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001582 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001583 i32 0, ;; Line number
1584 i64 32, ;; Size in bits
1585 i64 32, ;; Align in bits
1586 i64 0, ;; Offset in bits
1587 i32 0, ;; Flags
1588 5 ;; Encoding
1589}
Jim Laskeycec12a52006-03-14 18:08:46 +00001590</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001591</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001592
1593</div>
1594
1595<!-- ======================================================================= -->
1596<div class="doc_subsection">
1597 <a name="ccxx_composite_types">C/C++ struct/union types</a>
1598</div>
1599
1600<div class="doc_text">
1601
Misha Brukman96e00812008-12-16 02:54:22 +00001602<p>Given the following as an example of C/C++ struct type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001603
Bill Wendling48839d92009-05-17 05:52:39 +00001604<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001605<pre>
1606struct Color {
1607 unsigned Red;
1608 unsigned Green;
1609 unsigned Blue;
1610};
1611</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001612</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001613
Misha Brukman96e00812008-12-16 02:54:22 +00001614<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001615
Bill Wendling48839d92009-05-17 05:52:39 +00001616<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001617<pre>
1618;;
1619;; Define basic type for unsigned int.
1620;;
Devang Patele4b27562009-08-28 23:24:31 +00001621!5 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001622 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001623 metadata !1, ;; Context
1624 metadata !"unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001625 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001626 i32 0, ;; Line number
1627 i64 32, ;; Size in Bits
1628 i64 32, ;; Align in Bits
1629 i64 0, ;; Offset in Bits
1630 i32 0, ;; Flags
1631 i32 7 ;; Encoding
1632}
Jim Laskeycec12a52006-03-14 18:08:46 +00001633;;
1634;; Define composite type for struct Color.
1635;;
Devang Patele4b27562009-08-28 23:24:31 +00001636!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001637 i32 524307, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001638 metadata !1, ;; Context
1639 metadata !"Color", ;; Name
1640 metadata !1, ;; Compile unit
1641 i32 1, ;; Line number
1642 i64 96, ;; Size in bits
1643 i64 32, ;; Align in bits
1644 i64 0, ;; Offset in bits
1645 i32 0, ;; Flags
1646 null, ;; Derived From
1647 metadata !3, ;; Elements
1648 i32 0 ;; Runtime Language
1649}
Jim Laskeycec12a52006-03-14 18:08:46 +00001650
1651;;
1652;; Define the Red field.
1653;;
Devang Patele4b27562009-08-28 23:24:31 +00001654!4 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001655 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001656 metadata !1, ;; Context
1657 metadata !"Red", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001658 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001659 i32 2, ;; Line number
1660 i64 32, ;; Size in bits
1661 i64 32, ;; Align in bits
1662 i64 0, ;; Offset in bits
1663 i32 0, ;; Flags
1664 metadata !5 ;; Derived From type
1665}
Jim Laskeycec12a52006-03-14 18:08:46 +00001666
1667;;
1668;; Define the Green field.
1669;;
Devang Patele4b27562009-08-28 23:24:31 +00001670!6 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001671 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001672 metadata !1, ;; Context
1673 metadata !"Green", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001674 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001675 i32 3, ;; Line number
1676 i64 32, ;; Size in bits
1677 i64 32, ;; Align in bits
1678 i64 32, ;; Offset in bits
1679 i32 0, ;; Flags
1680 metadata !5 ;; Derived From type
1681}
Jim Laskeycec12a52006-03-14 18:08:46 +00001682
1683;;
1684;; Define the Blue field.
1685;;
Devang Patele4b27562009-08-28 23:24:31 +00001686!7 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001687 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001688 metadata !1, ;; Context
1689 metadata !"Blue", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001690 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001691 i32 4, ;; Line number
1692 i64 32, ;; Size in bits
1693 i64 32, ;; Align in bits
1694 i64 64, ;; Offset in bits
1695 i32 0, ;; Flags
1696 metadata !5 ;; Derived From type
1697}
Jim Laskeycec12a52006-03-14 18:08:46 +00001698
1699;;
1700;; Define the array of fields used by the composite type Color.
1701;;
Devang Patele4b27562009-08-28 23:24:31 +00001702!3 = metadata !{metadata !4, metadata !6, metadata !7}
Jim Laskeycec12a52006-03-14 18:08:46 +00001703</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001704</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001705
1706</div>
1707
1708<!-- ======================================================================= -->
1709<div class="doc_subsection">
1710 <a name="ccxx_enumeration_types">C/C++ enumeration types</a>
1711</div>
1712
1713<div class="doc_text">
1714
Misha Brukman96e00812008-12-16 02:54:22 +00001715<p>Given the following as an example of C/C++ enumeration type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001716
Bill Wendling48839d92009-05-17 05:52:39 +00001717<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001718<pre>
1719enum Trees {
1720 Spruce = 100,
1721 Oak = 200,
1722 Maple = 300
1723};
1724</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001725</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001726
Misha Brukman96e00812008-12-16 02:54:22 +00001727<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001728
Bill Wendling48839d92009-05-17 05:52:39 +00001729<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001730<pre>
1731;;
1732;; Define composite type for enum Trees
1733;;
Devang Patele4b27562009-08-28 23:24:31 +00001734!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001735 i32 524292, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001736 metadata !1, ;; Context
1737 metadata !"Trees", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001738 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001739 i32 1, ;; Line number
1740 i64 32, ;; Size in bits
1741 i64 32, ;; Align in bits
1742 i64 0, ;; Offset in bits
1743 i32 0, ;; Flags
1744 null, ;; Derived From type
1745 metadata !3, ;; Elements
1746 i32 0 ;; Runtime language
1747}
Devang Patel2a610c72009-08-25 05:24:07 +00001748
Devang Patel82459882009-08-26 05:01:18 +00001749;;
1750;; Define the array of enumerators used by composite type Trees.
1751;;
Devang Patele4b27562009-08-28 23:24:31 +00001752!3 = metadata !{metadata !4, metadata !5, metadata !6}
1753
1754;;
1755;; Define Spruce enumerator.
1756;;
Devang Patel4b945502010-03-09 00:44:10 +00001757!4 = metadata !{i32 524328, metadata !"Spruce", i64 100}
Devang Patele4b27562009-08-28 23:24:31 +00001758
1759;;
1760;; Define Oak enumerator.
1761;;
Devang Patel4b945502010-03-09 00:44:10 +00001762!5 = metadata !{i32 524328, metadata !"Oak", i64 200}
Devang Patele4b27562009-08-28 23:24:31 +00001763
1764;;
1765;; Define Maple enumerator.
1766;;
Devang Patel4b945502010-03-09 00:44:10 +00001767!6 = metadata !{i32 524328, metadata !"Maple", i64 300}
Devang Patele4b27562009-08-28 23:24:31 +00001768
Jim Laskeycec12a52006-03-14 18:08:46 +00001769</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001770</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001771
1772</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001773
1774<!-- *********************************************************************** -->
Misha Brukman82873732004-05-12 19:21:57 +00001775
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001776<hr>
Misha Brukman82873732004-05-12 19:21:57 +00001777<address>
1778 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001779 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman82873732004-05-12 19:21:57 +00001780 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001781 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman82873732004-05-12 19:21:57 +00001782
1783 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001784 <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001785 Last modified: $Date$
Misha Brukman82873732004-05-12 19:21:57 +00001786</address>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001787
1788</body>
1789</html>