blob: f92a1656a901433a48825a62580ee77792e65103 [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
147<p>Currently, debug information is consumed by the DwarfWriter 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
Bill Wendling48839d92009-05-17 05:52:39 +0000292 are restricted to only the simple data types <tt>int</tt>, <tt>uint</tt>,
Devang Patele4b27562009-08-28 23:24:31 +0000293 <tt>bool</tt>, <tt>float</tt>, <tt>double</tt>, <tt>mdstring</tt> and
294 <tt>mdnode</tt>. </p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000295
Bill Wendling48839d92009-05-17 05:52:39 +0000296<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000297<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000298!1 = metadata !{
Bill Wendling48839d92009-05-17 05:52:39 +0000299 uint, ;; A tag
300 ...
301}
Misha Brukman82873732004-05-12 19:21:57 +0000302</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000303</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000304
Jim Laskey7089f452006-06-16 13:14:03 +0000305<p><a name="LLVMDebugVersion">The first field of a descriptor is always an
Bill Wendling48839d92009-05-17 05:52:39 +0000306 <tt>uint</tt> containing a tag value identifying the content of the
307 descriptor. The remaining fields are specific to the descriptor. The values
308 of tags are loosely bound to the tag values of DWARF information entries.
309 However, that does not restrict the use of the information supplied to DWARF
310 targets. To facilitate versioning of debug information, the tag is augmented
Devang Patel4b945502010-03-09 00:44:10 +0000311 with the current debug version (LLVMDebugVersion = 8 << 16 or 0x80000 or
312 524288.)</a></p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000313
Jim Laskey7089f452006-06-16 13:14:03 +0000314<p>The details of the various descriptors follow.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000315
316</div>
317
318<!-- ======================================================================= -->
319<div class="doc_subsubsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000320 <a name="format_compile_units">Compile unit descriptors</a>
321</div>
322
323<div class="doc_text">
324
Bill Wendling48839d92009-05-17 05:52:39 +0000325<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000326<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000327!0 = metadata !{
328 i32, ;; Tag = 17 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
329 ;; (DW_TAG_compile_unit)
330 i32, ;; Unused field.
331 i32, ;; DWARF language identifier (ex. DW_LANG_C89)
332 metadata, ;; Source file name
333 metadata, ;; Source file directory (includes trailing slash)
334 metadata ;; Producer (ex. "4.0.1 LLVM (LLVM research group)")
335 i1, ;; True if this is a main compile unit.
336 i1, ;; True if this is optimized.
337 metadata, ;; Flags
338 i32 ;; Runtime version
Bill Wendling48839d92009-05-17 05:52:39 +0000339}
Jim Laskeycec12a52006-03-14 18:08:46 +0000340</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000341</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000342
Bill Wendling48839d92009-05-17 05:52:39 +0000343<p>These descriptors contain a source language ID for the file (we use the DWARF
344 3.0 ID numbers, such as <tt>DW_LANG_C89</tt>, <tt>DW_LANG_C_plus_plus</tt>,
345 <tt>DW_LANG_Cobol74</tt>, etc), three strings describing the filename,
346 working directory of the compiler, and an identifier string for the compiler
347 that produced it.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000348
Bill Wendling48839d92009-05-17 05:52:39 +0000349<p>Compile unit descriptors provide the root context for objects declared in a
Devang Patel4b945502010-03-09 00:44:10 +0000350 specific compilation unit. File descriptors are defined using this context.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000351
Devang Patel4b945502010-03-09 00:44:10 +0000352</div>
353
354<!-- ======================================================================= -->
355<div class="doc_subsubsection">
356 <a name="format_files">File descriptors</a>
357</div>
358
359<div class="doc_text">
360
361<div class="doc_code">
362<pre>
363!0 = metadata !{
364 i32, ;; Tag = 41 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
365 ;; (DW_TAG_file_type)
366 metadata, ;; Source file name
367 metadata, ;; Source file directory (includes trailing slash)
368 metadata ;; Reference to compile unit where defined
369}
370</pre>
371</div>
372
John Criswellb34500f2010-03-17 15:01:50 +0000373<p>These descriptors contain information for a file. Global variables and top
Devang Patel4b945502010-03-09 00:44:10 +0000374 level functions would be defined using this context.k File descriptors also
375 provide context for source line correspondence. </p>
376
377<p>Each input file is encoded as a separate file descriptor in LLVM debugging
378 information output. Each file descriptor would be defined using a
379 compile unit. </p>
Bill Wendling48839d92009-05-17 05:52:39 +0000380
Jim Laskeycec12a52006-03-14 18:08:46 +0000381</div>
382
383<!-- ======================================================================= -->
384<div class="doc_subsubsection">
385 <a name="format_global_variables">Global variable descriptors</a>
386</div>
387
388<div class="doc_text">
389
Bill Wendling48839d92009-05-17 05:52:39 +0000390<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000391<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000392!1 = metadata !{
393 i32, ;; Tag = 52 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
394 ;; (DW_TAG_variable)
395 i32, ;; Unused field.
396 metadata, ;; Reference to context descriptor
397 metadata, ;; Name
398 metadata, ;; Display name (fully qualified C++ name)
399 metadata, ;; MIPS linkage name (for C++)
Devang Patel4b945502010-03-09 00:44:10 +0000400 metadata, ;; Reference to file where defined
Devang Patele4b27562009-08-28 23:24:31 +0000401 i32, ;; Line number where defined
402 metadata, ;; Reference to type descriptor
403 i1, ;; True if the global is local to compile unit (static)
404 i1, ;; True if the global is defined in the compile unit (not extern)
405 { }* ;; Reference to the global variable
Bill Wendling48839d92009-05-17 05:52:39 +0000406}
Jim Laskeycec12a52006-03-14 18:08:46 +0000407</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000408</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000409
410<p>These descriptors provide debug information about globals variables. The
411provide details such as name, type and where the variable is defined.</p>
412
413</div>
414
415<!-- ======================================================================= -->
416<div class="doc_subsubsection">
417 <a name="format_subprograms">Subprogram descriptors</a>
418</div>
419
420<div class="doc_text">
421
Bill Wendling48839d92009-05-17 05:52:39 +0000422<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000423<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000424!2 = metadata !{
425 i32, ;; Tag = 46 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
426 ;; (DW_TAG_subprogram)
427 i32, ;; Unused field.
428 metadata, ;; Reference to context descriptor
429 metadata, ;; Name
430 metadata, ;; Display name (fully qualified C++ name)
431 metadata, ;; MIPS linkage name (for C++)
Devang Patel4b945502010-03-09 00:44:10 +0000432 metadata, ;; Reference to file where defined
Devang Patele4b27562009-08-28 23:24:31 +0000433 i32, ;; Line number where defined
434 metadata, ;; Reference to type descriptor
435 i1, ;; True if the global is local to compile unit (static)
436 i1 ;; True if the global is defined in the compile unit (not extern)
Bill Wendling48839d92009-05-17 05:52:39 +0000437}
Jim Laskeycec12a52006-03-14 18:08:46 +0000438</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000439</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000440
441<p>These descriptors provide debug information about functions, methods and
Bill Wendling48839d92009-05-17 05:52:39 +0000442 subprograms. They provide details such as name, return types and the source
443 location where the subprogram is defined.</p>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000444
445</div>
Bill Wendling48839d92009-05-17 05:52:39 +0000446
Jim Laskey3d11bee2006-03-15 19:10:52 +0000447<!-- ======================================================================= -->
448<div class="doc_subsubsection">
449 <a name="format_blocks">Block descriptors</a>
450</div>
451
452<div class="doc_text">
453
Bill Wendling48839d92009-05-17 05:52:39 +0000454<div class="doc_code">
Jim Laskey3d11bee2006-03-15 19:10:52 +0000455<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000456!3 = metadata !{
457 i32, ;; Tag = 13 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_lexical_block)
458 metadata ;; Reference to context descriptor
Bill Wendling48839d92009-05-17 05:52:39 +0000459}
Jim Laskey3d11bee2006-03-15 19:10:52 +0000460</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000461</div>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000462
463<p>These descriptors provide debug information about nested blocks within a
Bill Wendling48839d92009-05-17 05:52:39 +0000464 subprogram. The array of member descriptors is used to define local
465 variables and deeper nested blocks.</p>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000466
Jim Laskeycec12a52006-03-14 18:08:46 +0000467</div>
468
469<!-- ======================================================================= -->
470<div class="doc_subsubsection">
471 <a name="format_basic_type">Basic type descriptors</a>
472</div>
473
474<div class="doc_text">
475
Bill Wendling48839d92009-05-17 05:52:39 +0000476<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000477<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000478!4 = metadata !{
479 i32, ;; Tag = 36 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
480 ;; (DW_TAG_base_type)
481 metadata, ;; Reference to context (typically a compile unit)
482 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000483 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000484 i32, ;; Line number where defined (may be 0)
485 i64, ;; Size in bits
486 i64, ;; Alignment in bits
487 i64, ;; Offset in bits
488 i32, ;; Flags
489 i32 ;; DWARF type encoding
Bill Wendling48839d92009-05-17 05:52:39 +0000490}
Jim Laskeycec12a52006-03-14 18:08:46 +0000491</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000492</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000493
494<p>These descriptors define primitive types used in the code. Example int, bool
Bill Wendling48839d92009-05-17 05:52:39 +0000495 and float. The context provides the scope of the type, which is usually the
496 top level. Since basic types are not usually user defined the compile unit
497 and line number can be left as NULL and 0. The size, alignment and offset
498 are expressed in bits and can be 64 bit values. The alignment is used to
499 round the offset when embedded in a
500 <a href="#format_composite_type">composite type</a> (example to keep float
501 doubles on 64 bit boundaries.) The offset is the bit offset if embedded in
502 a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000503
504<p>The type encoding provides the details of the type. The values are typically
Bill Wendling48839d92009-05-17 05:52:39 +0000505 one of the following:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000506
Bill Wendling48839d92009-05-17 05:52:39 +0000507<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000508<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000509DW_ATE_address = 1
510DW_ATE_boolean = 2
511DW_ATE_float = 4
512DW_ATE_signed = 5
513DW_ATE_signed_char = 6
514DW_ATE_unsigned = 7
515DW_ATE_unsigned_char = 8
Jim Laskeycec12a52006-03-14 18:08:46 +0000516</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000517</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000518
519</div>
520
521<!-- ======================================================================= -->
522<div class="doc_subsubsection">
523 <a name="format_derived_type">Derived type descriptors</a>
524</div>
525
526<div class="doc_text">
527
Bill Wendling48839d92009-05-17 05:52:39 +0000528<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000529<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000530!5 = metadata !{
531 i32, ;; Tag (see below)
532 metadata, ;; Reference to context
533 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000534 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000535 i32, ;; Line number where defined (may be 0)
536 i32, ;; Size in bits
537 i32, ;; Alignment in bits
538 i32, ;; Offset in bits
539 metadata ;; Reference to type derived from
Bill Wendling48839d92009-05-17 05:52:39 +0000540}
Jim Laskeycec12a52006-03-14 18:08:46 +0000541</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000542</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000543
544<p>These descriptors are used to define types derived from other types. The
545value of the tag varies depending on the meaning. The following are possible
Misha Brukman96e00812008-12-16 02:54:22 +0000546tag values:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000547
Bill Wendling48839d92009-05-17 05:52:39 +0000548<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000549<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000550DW_TAG_formal_parameter = 5
551DW_TAG_member = 13
552DW_TAG_pointer_type = 15
553DW_TAG_reference_type = 16
554DW_TAG_typedef = 22
555DW_TAG_const_type = 38
556DW_TAG_volatile_type = 53
557DW_TAG_restrict_type = 55
Jim Laskeycec12a52006-03-14 18:08:46 +0000558</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000559</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000560
Bill Wendling48839d92009-05-17 05:52:39 +0000561<p><tt>DW_TAG_member</tt> is used to define a member of
562 a <a href="#format_composite_type">composite type</a>
563 or <a href="#format_subprograms">subprogram</a>. The type of the member is
564 the <a href="#format_derived_type">derived
565 type</a>. <tt>DW_TAG_formal_parameter</tt> is used to define a member which
566 is a formal argument of a subprogram.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000567
Bill Wendling48839d92009-05-17 05:52:39 +0000568<p><tt>DW_TAG_typedef</tt> is used to provide a name for the derived type.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000569
Bill Wendling48839d92009-05-17 05:52:39 +0000570<p><tt>DW_TAG_pointer_type</tt>,<tt>DW_TAG_reference_type</tt>,
571 <tt>DW_TAG_const_type</tt>, <tt>DW_TAG_volatile_type</tt>
572 and <tt>DW_TAG_restrict_type</tt> are used to qualify
573 the <a href="#format_derived_type">derived type</a>. </p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000574
575<p><a href="#format_derived_type">Derived type</a> location can be determined
Bill Wendling48839d92009-05-17 05:52:39 +0000576 from the compile unit and line number. The size, alignment and offset are
577 expressed in bits and can be 64 bit values. The alignment is used to round
578 the offset when embedded in a <a href="#format_composite_type">composite
579 type</a> (example to keep float doubles on 64 bit boundaries.) The offset is
580 the bit offset if embedded in a <a href="#format_composite_type">composite
581 type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000582
583<p>Note that the <tt>void *</tt> type is expressed as a
Bill Wendling48839d92009-05-17 05:52:39 +0000584 <tt>llvm.dbg.derivedtype.type</tt> with tag of <tt>DW_TAG_pointer_type</tt>
585 and <tt>NULL</tt> derived type.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000586
587</div>
588
589<!-- ======================================================================= -->
590<div class="doc_subsubsection">
591 <a name="format_composite_type">Composite type descriptors</a>
592</div>
593
594<div class="doc_text">
595
Bill Wendling48839d92009-05-17 05:52:39 +0000596<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000597<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000598!6 = metadata !{
599 i32, ;; Tag (see below)
600 metadata, ;; Reference to context
601 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000602 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000603 i32, ;; Line number where defined (may be 0)
604 i64, ;; Size in bits
605 i64, ;; Alignment in bits
606 i64, ;; Offset in bits
607 i32, ;; Flags
608 metadata, ;; Reference to type derived from
609 metadata, ;; Reference to array of member descriptors
610 i32 ;; Runtime languages
Bill Wendling48839d92009-05-17 05:52:39 +0000611}
Jim Laskeycec12a52006-03-14 18:08:46 +0000612</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000613</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000614
615<p>These descriptors are used to define types that are composed of 0 or more
616elements. The value of the tag varies depending on the meaning. The following
Misha Brukman96e00812008-12-16 02:54:22 +0000617are possible tag values:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000618
Bill Wendling48839d92009-05-17 05:52:39 +0000619<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000620<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000621DW_TAG_array_type = 1
622DW_TAG_enumeration_type = 4
623DW_TAG_structure_type = 19
624DW_TAG_union_type = 23
625DW_TAG_vector_type = 259
Bruno Cardoso Lopesd80ddc02009-05-29 17:08:57 +0000626DW_TAG_subroutine_type = 21
627DW_TAG_inheritance = 28
Jim Laskeycec12a52006-03-14 18:08:46 +0000628</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000629</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000630
Jim Laskeyf8a01a92006-06-15 20:51:43 +0000631<p>The vector flag indicates that an array type is a native packed vector.</p>
632
Jim Laskey7089f452006-06-16 13:14:03 +0000633<p>The members of array types (tag = <tt>DW_TAG_array_type</tt>) or vector types
Bill Wendling48839d92009-05-17 05:52:39 +0000634 (tag = <tt>DW_TAG_vector_type</tt>) are <a href="#format_subrange">subrange
635 descriptors</a>, each representing the range of subscripts at that level of
636 indexing.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000637
638<p>The members of enumeration types (tag = <tt>DW_TAG_enumeration_type</tt>) are
Bill Wendling48839d92009-05-17 05:52:39 +0000639 <a href="#format_enumeration">enumerator descriptors</a>, each representing
640 the definition of enumeration value for the set.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000641
642<p>The members of structure (tag = <tt>DW_TAG_structure_type</tt>) or union (tag
Bill Wendling48839d92009-05-17 05:52:39 +0000643 = <tt>DW_TAG_union_type</tt>) types are any one of
644 the <a href="#format_basic_type">basic</a>,
645 <a href="#format_derived_type">derived</a>
646 or <a href="#format_composite_type">composite</a> type descriptors, each
647 representing a field member of the structure or union.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000648
Jim Laskey4a9df242006-08-21 21:21:06 +0000649<p>For C++ classes (tag = <tt>DW_TAG_structure_type</tt>), member descriptors
Bill Wendling48839d92009-05-17 05:52:39 +0000650 provide information about base classes, static members and member
651 functions. If a member is a <a href="#format_derived_type">derived type
652 descriptor</a> and has a tag of <tt>DW_TAG_inheritance</tt>, then the type
653 represents a base class. If the member of is
654 a <a href="#format_global_variables">global variable descriptor</a> then it
655 represents a static member. And, if the member is
656 a <a href="#format_subprograms">subprogram descriptor</a> then it represents
657 a member function. For static members and member
658 functions, <tt>getName()</tt> returns the members link or the C++ mangled
659 name. <tt>getDisplayName()</tt> the simplied version of the name.</p>
Jim Laskey4a9df242006-08-21 21:21:06 +0000660
Bill Wendling48839d92009-05-17 05:52:39 +0000661<p>The first member of subroutine (tag = <tt>DW_TAG_subroutine_type</tt>) type
662 elements is the return type for the subroutine. The remaining elements are
663 the formal arguments to the subroutine.</p>
Jim Laskey094ee722006-06-20 21:13:20 +0000664
Jim Laskeycec12a52006-03-14 18:08:46 +0000665<p><a href="#format_composite_type">Composite type</a> location can be
Bill Wendling48839d92009-05-17 05:52:39 +0000666 determined from the compile unit and line number. The size, alignment and
667 offset are expressed in bits and can be 64 bit values. The alignment is used
668 to round the offset when embedded in
669 a <a href="#format_composite_type">composite type</a> (as an example, to keep
670 float doubles on 64 bit boundaries.) The offset is the bit offset if embedded
671 in a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000672
673</div>
674
675<!-- ======================================================================= -->
676<div class="doc_subsubsection">
677 <a name="format_subrange">Subrange descriptors</a>
678</div>
679
680<div class="doc_text">
681
Bill Wendling48839d92009-05-17 05:52:39 +0000682<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000683<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000684%<a href="#format_subrange">llvm.dbg.subrange.type</a> = type {
685 i32, ;; Tag = 33 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_subrange_type)
686 i64, ;; Low value
687 i64 ;; High value
688}
Jim Laskeycec12a52006-03-14 18:08:46 +0000689</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000690</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000691
692<p>These descriptors are used to define ranges of array subscripts for an array
Bill Wendling48839d92009-05-17 05:52:39 +0000693 <a href="#format_composite_type">composite type</a>. The low value defines
694 the lower bounds typically zero for C/C++. The high value is the upper
695 bounds. Values are 64 bit. High - low + 1 is the size of the array. If low
696 == high the array will be unbounded.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000697
698</div>
699
700<!-- ======================================================================= -->
701<div class="doc_subsubsection">
702 <a name="format_enumeration">Enumerator descriptors</a>
703</div>
704
705<div class="doc_text">
706
Bill Wendling48839d92009-05-17 05:52:39 +0000707<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000708<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000709!6 = metadata !{
710 i32, ;; Tag = 40 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
711 ;; (DW_TAG_enumerator)
712 metadata, ;; Name
713 i64 ;; Value
Bill Wendling48839d92009-05-17 05:52:39 +0000714}
Jim Laskeycec12a52006-03-14 18:08:46 +0000715</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000716</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000717
Bill Wendling48839d92009-05-17 05:52:39 +0000718<p>These descriptors are used to define members of an
719 enumeration <a href="#format_composite_type">composite type</a>, it
720 associates the name to the value.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000721
722</div>
723
724<!-- ======================================================================= -->
Jim Laskey383e0092006-03-23 17:54:33 +0000725<div class="doc_subsubsection">
726 <a name="format_variables">Local variables</a>
727</div>
728
729<div class="doc_text">
Bill Wendling48839d92009-05-17 05:52:39 +0000730
731<div class="doc_code">
Jim Laskey383e0092006-03-23 17:54:33 +0000732<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000733!7 = metadata !{
734 i32, ;; Tag (see below)
735 metadata, ;; Context
736 metadata, ;; Name
Devang Patel4b945502010-03-09 00:44:10 +0000737 metadata, ;; Reference to file where defined
Devang Patele4b27562009-08-28 23:24:31 +0000738 i32, ;; Line number where defined
739 metadata ;; Type descriptor
Bill Wendling48839d92009-05-17 05:52:39 +0000740}
Jim Laskey383e0092006-03-23 17:54:33 +0000741</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000742</div>
Jim Laskey383e0092006-03-23 17:54:33 +0000743
744<p>These descriptors are used to define variables local to a sub program. The
Bill Wendling48839d92009-05-17 05:52:39 +0000745 value of the tag depends on the usage of the variable:</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000746
Bill Wendling48839d92009-05-17 05:52:39 +0000747<div class="doc_code">
Jim Laskey383e0092006-03-23 17:54:33 +0000748<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000749DW_TAG_auto_variable = 256
750DW_TAG_arg_variable = 257
751DW_TAG_return_variable = 258
Jim Laskey383e0092006-03-23 17:54:33 +0000752</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000753</div>
Jim Laskey383e0092006-03-23 17:54:33 +0000754
755<p>An auto variable is any variable declared in the body of the function. An
Bill Wendling48839d92009-05-17 05:52:39 +0000756 argument variable is any variable that appears as a formal argument to the
757 function. A return variable is used to track the result of a function and
758 has no source correspondent.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000759
Jim Laskey2d395d92006-03-24 09:20:27 +0000760<p>The context is either the subprogram or block where the variable is defined.
Bill Wendling48839d92009-05-17 05:52:39 +0000761 Name the source variable name. Compile unit and line indicate where the
762 variable was defined. Type descriptor defines the declared type of the
763 variable.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000764
765</div>
766
767<!-- ======================================================================= -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000768<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000769 <a name="format_common_intrinsics">Debugger intrinsic functions</a>
770</div>
771
772<div class="doc_text">
773
774<p>LLVM uses several intrinsic functions (name prefixed with "llvm.dbg") to
Bill Wendling48839d92009-05-17 05:52:39 +0000775 provide debug information at various points in generated code.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000776
777</div>
778
779<!-- ======================================================================= -->
780<div class="doc_subsubsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000781 <a name="format_common_declare">llvm.dbg.declare</a>
782</div>
783
784<div class="doc_text">
785<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000786 void %<a href="#format_common_declare">llvm.dbg.declare</a>( { } *, metadata )
Jim Laskeycec12a52006-03-14 18:08:46 +0000787</pre>
788
Jim Laskey2d395d92006-03-24 09:20:27 +0000789<p>This intrinsic provides information about a local element (ex. variable.) The
Bill Wendling48839d92009-05-17 05:52:39 +0000790 first argument is the alloca for the variable, cast to a <tt>{ }*</tt>. The
791 second argument is
792 the <tt>%<a href="#format_variables">llvm.dbg.variable</a></tt> containing
Devang Patele4b27562009-08-28 23:24:31 +0000793 the description of the variable. </p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000794
795</div>
796
797<!-- ======================================================================= -->
Victor Hernandez67a1a542010-01-11 22:53:48 +0000798<div class="doc_subsubsection">
799 <a name="format_common_value">llvm.dbg.value</a>
800</div>
801
802<div class="doc_text">
803<pre>
804 void %<a href="#format_common_value">llvm.dbg.value</a>( metadata, i64, metadata )
805</pre>
806
807<p>This intrinsic provides information when a user source variable is set to a
808 new value. The first argument is the new value (wrapped as metadata). The
809 second argument is the offset in the user source variable where the new value
810 is written. The third argument is
811 the <tt>%<a href="#format_variables">llvm.dbg.variable</a></tt> containing
812 the description of the user source variable. </p>
813
814</div>
815
816<!-- ======================================================================= -->
Jim Laskeycec12a52006-03-14 18:08:46 +0000817<div class="doc_subsection">
Chris Lattner8ff75902004-01-06 05:31:32 +0000818 <a name="format_common_lifetime">Object lifetimes and scoping</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000819</div>
820
821<div class="doc_text">
Bill Wendlingcf493b82009-12-01 00:53:11 +0000822<p>In many languages, the local variables in functions can have their lifetimes
823 or scopes limited to a subset of a function. In the C family of languages,
Bill Wendling48839d92009-05-17 05:52:39 +0000824 for example, variables are only live (readable and writable) within the
825 source block that they are defined in. In functional languages, values are
826 only readable after they have been defined. Though this is a very obvious
Bill Wendlingcf493b82009-12-01 00:53:11 +0000827 concept, it is non-trivial to model in LLVM, because it has no notion of
Bill Wendling48839d92009-05-17 05:52:39 +0000828 scoping in this sense, and does not want to be tied to a language's scoping
829 rules.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000830
Bill Wendlingcf493b82009-12-01 00:53:11 +0000831<p>In order to handle this, the LLVM debug format uses the metadata attached to
832 llvm instructions to encode line nuber and scoping information. Consider the
833 following C fragment, for example:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000834
Bill Wendling48839d92009-05-17 05:52:39 +0000835<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000836<pre>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008371. void foo() {
Devang Patel744950d2009-11-25 23:28:01 +00008382. int X = 21;
8393. int Y = 22;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008404. {
Devang Patel744950d2009-11-25 23:28:01 +00008415. int Z = 23;
8426. Z = X;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008437. }
Devang Patel744950d2009-11-25 23:28:01 +00008448. X = Y;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008459. }
Misha Brukman82873732004-05-12 19:21:57 +0000846</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000847</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000848
Jim Laskeycec12a52006-03-14 18:08:46 +0000849<p>Compiled to LLVM, this function would be represented like this:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000850
Bill Wendling48839d92009-05-17 05:52:39 +0000851<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000852<pre>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000853define void @foo() nounwind ssp {
Jim Laskeycec12a52006-03-14 18:08:46 +0000854entry:
Bill Wendling02216ff2009-12-01 00:59:58 +0000855 %X = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
856 %Y = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
857 %Z = alloca i32, align 4 ; &lt;i32*&gt; [#uses=3]
858 %0 = bitcast i32* %X to { }* ; &lt;{ }*&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000859 call void @llvm.dbg.declare({ }* %0, metadata !0), !dbg !7
860 store i32 21, i32* %X, !dbg !8
Bill Wendling02216ff2009-12-01 00:59:58 +0000861 %1 = bitcast i32* %Y to { }* ; &lt;{ }*&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000862 call void @llvm.dbg.declare({ }* %1, metadata !9), !dbg !10
863 store i32 22, i32* %Y, !dbg !11
Bill Wendling02216ff2009-12-01 00:59:58 +0000864 %2 = bitcast i32* %Z to { }* ; &lt;{ }*&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000865 call void @llvm.dbg.declare({ }* %2, metadata !12), !dbg !14
866 store i32 23, i32* %Z, !dbg !15
Bill Wendling02216ff2009-12-01 00:59:58 +0000867 %tmp = load i32* %X, !dbg !16 ; &lt;i32&gt; [#uses=1]
868 %tmp1 = load i32* %Y, !dbg !16 ; &lt;i32&gt; [#uses=1]
869 %add = add nsw i32 %tmp, %tmp1, !dbg !16 ; &lt;i32&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000870 store i32 %add, i32* %Z, !dbg !16
Bill Wendling02216ff2009-12-01 00:59:58 +0000871 %tmp2 = load i32* %Y, !dbg !17 ; &lt;i32&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000872 store i32 %tmp2, i32* %X, !dbg !17
873 ret void, !dbg !18
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000874}
Devang Patel744950d2009-11-25 23:28:01 +0000875
876declare void @llvm.dbg.declare({ }*, metadata) nounwind readnone
877
878!0 = metadata !{i32 459008, metadata !1, metadata !"X",
879 metadata !3, i32 2, metadata !6}; [ DW_TAG_auto_variable ]
880!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
881!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo", metadata !"foo",
882 metadata !"foo", metadata !3, i32 1, metadata !4,
883 i1 false, i1 true}; [DW_TAG_subprogram ]
884!3 = metadata !{i32 458769, i32 0, i32 12, metadata !"foo.c",
885 metadata !"/private/tmp", metadata !"clang 1.1", i1 true,
886 i1 false, metadata !"", i32 0}; [DW_TAG_compile_unit ]
887!4 = metadata !{i32 458773, metadata !3, metadata !"", null, i32 0, i64 0, i64 0,
888 i64 0, i32 0, null, metadata !5, i32 0}; [DW_TAG_subroutine_type ]
889!5 = metadata !{null}
890!6 = metadata !{i32 458788, metadata !3, metadata !"int", metadata !3, i32 0,
891 i64 32, i64 32, i64 0, i32 0, i32 5}; [DW_TAG_base_type ]
892!7 = metadata !{i32 2, i32 7, metadata !1, null}
893!8 = metadata !{i32 2, i32 3, metadata !1, null}
894!9 = metadata !{i32 459008, metadata !1, metadata !"Y", metadata !3, i32 3,
895 metadata !6}; [ DW_TAG_auto_variable ]
896!10 = metadata !{i32 3, i32 7, metadata !1, null}
897!11 = metadata !{i32 3, i32 3, metadata !1, null}
898!12 = metadata !{i32 459008, metadata !13, metadata !"Z", metadata !3, i32 5,
899 metadata !6}; [ DW_TAG_auto_variable ]
900!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
901!14 = metadata !{i32 5, i32 9, metadata !13, null}
902!15 = metadata !{i32 5, i32 5, metadata !13, null}
903!16 = metadata !{i32 6, i32 5, metadata !13, null}
904!17 = metadata !{i32 8, i32 3, metadata !1, null}
905!18 = metadata !{i32 9, i32 1, metadata !2, null}
Misha Brukman82873732004-05-12 19:21:57 +0000906</pre>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000907</div>
908
Bill Wendlingcf493b82009-12-01 00:53:11 +0000909<p>This example illustrates a few important details about LLVM debugging
910 information. In particular, it shows how the <tt>llvm.dbg.declare</tt>
911 intrinsic and location information, which are attached to an instruction,
912 are applied together to allow a debugger to analyze the relationship between
913 statements, variable definitions, and the code used to implement the
914 function.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000915
Bill Wendlingcf493b82009-12-01 00:53:11 +0000916<div class="doc_code">
Bill Wendling02216ff2009-12-01 00:59:58 +0000917<pre>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000918call void @llvm.dbg.declare({ }* %0, metadata !0), !dbg !7
919</pre>
920</div>
921
922<p>The first intrinsic
Devang Patel744950d2009-11-25 23:28:01 +0000923 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000924 encodes debugging information for the variable <tt>X</tt>. The metadata
925 <tt>!dbg !7</tt> attached to the intrinsic provides scope information for the
926 variable <tt>X</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000927
Bill Wendlingcf493b82009-12-01 00:53:11 +0000928<div class="doc_code">
929<pre>
930!7 = metadata !{i32 2, i32 7, metadata !1, null}
931!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
932!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo",
933 metadata !"foo", metadata !"foo", metadata !3, i32 1,
934 metadata !4, i1 false, i1 true}; [DW_TAG_subprogram ]
935</pre>
936</div>
937
938<p>Here <tt>!7</tt> is metadata providing location information. It has four
939 fields: line number, column number, scope, and original scope. The original
940 scope represents inline location if this instruction is inlined inside a
941 caller, and is null otherwise. In this example, scope is encoded by
Devang Patel744950d2009-11-25 23:28:01 +0000942 <tt>!1</tt>. <tt>!1</tt> represents a lexical block inside the scope
943 <tt>!2</tt>, where <tt>!2</tt> is a
Bill Wendlingcf493b82009-12-01 00:53:11 +0000944 <a href="#format_subprograms">subprogram descriptor</a>. This way the
945 location information attached to the intrinsics indicates that the
946 variable <tt>X</tt> is declared at line number 2 at a function level scope in
947 function <tt>foo</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000948
Devang Patel744950d2009-11-25 23:28:01 +0000949<p>Now lets take another example.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000950
Bill Wendlingcf493b82009-12-01 00:53:11 +0000951<div class="doc_code">
Bill Wendling02216ff2009-12-01 00:59:58 +0000952<pre>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000953call void @llvm.dbg.declare({ }* %2, metadata !12), !dbg !14
954</pre>
955</div>
956
957<p>The second intrinsic
Devang Patel744950d2009-11-25 23:28:01 +0000958 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000959 encodes debugging information for variable <tt>Z</tt>. The metadata
960 <tt>!dbg !14</tt> attached to the intrinsic provides scope information for
961 the variable <tt>Z</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000962
Bill Wendlingcf493b82009-12-01 00:53:11 +0000963<div class="doc_code">
964<pre>
965!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
966!14 = metadata !{i32 5, i32 9, metadata !13, null}
967</pre>
968</div>
Bill Wendling48839d92009-05-17 05:52:39 +0000969
John Criswellb34500f2010-03-17 15:01:50 +0000970<p>Here <tt>!14</tt> indicates that <tt>Z</tt> is declared at line number 5 and
Bill Wendlingcf493b82009-12-01 00:53:11 +0000971 column number 9 inside of lexical scope <tt>!13</tt>. The lexical scope
972 itself resides inside of lexical scope <tt>!1</tt> described above.</p>
973
974<p>The scope information attached with each instruction provides a
975 straightforward way to find instructions covered by a scope.</p>
976
Bill Wendling48839d92009-05-17 05:52:39 +0000977</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000978
979<!-- *********************************************************************** -->
980<div class="doc_section">
Chris Lattner8ff75902004-01-06 05:31:32 +0000981 <a name="ccxx_frontend">C/C++ front-end specific debug information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000982</div>
Misha Brukman94218a72004-12-09 20:27:37 +0000983<!-- *********************************************************************** -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000984
985<div class="doc_text">
986
Misha Brukman82873732004-05-12 19:21:57 +0000987<p>The C and C++ front-ends represent information about the program in a format
Bill Wendling48839d92009-05-17 05:52:39 +0000988 that is effectively identical
989 to <a href="http://www.eagercon.com/dwarf/dwarf3std.htm">DWARF 3.0</a> in
990 terms of information content. This allows code generators to trivially
991 support native debuggers by generating standard dwarf information, and
992 contains enough information for non-dwarf targets to translate it as
993 needed.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000994
Jim Laskeycec12a52006-03-14 18:08:46 +0000995<p>This section describes the forms used to represent C and C++ programs. Other
Bill Wendling48839d92009-05-17 05:52:39 +0000996 languages could pattern themselves after this (which itself is tuned to
997 representing programs in the same way that DWARF 3 does), or they could
998 choose to provide completely different forms if they don't fit into the DWARF
999 model. As support for debugging information gets added to the various LLVM
1000 source-language front-ends, the information used should be documented
1001 here.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001002
Jim Laskeycec12a52006-03-14 18:08:46 +00001003<p>The following sections provide examples of various C/C++ constructs and the
Bill Wendling48839d92009-05-17 05:52:39 +00001004 debug information that would best describe those constructs.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001005
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001006</div>
1007
1008<!-- ======================================================================= -->
1009<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +00001010 <a name="ccxx_compile_units">C/C++ source file information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001011</div>
1012
1013<div class="doc_text">
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001014
Bill Wendling48839d92009-05-17 05:52:39 +00001015<p>Given the source files <tt>MySource.cpp</tt> and <tt>MyHeader.h</tt> located
1016 in the directory <tt>/Users/mine/sources</tt>, the following code:</p>
Chris Lattner8ff75902004-01-06 05:31:32 +00001017
Bill Wendling48839d92009-05-17 05:52:39 +00001018<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001019<pre>
1020#include "MyHeader.h"
Chris Lattner8ff75902004-01-06 05:31:32 +00001021
Jim Laskeycec12a52006-03-14 18:08:46 +00001022int main(int argc, char *argv[]) {
1023 return 0;
1024}
1025</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001026</div>
Chris Lattner8ff75902004-01-06 05:31:32 +00001027
Misha Brukman96e00812008-12-16 02:54:22 +00001028<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001029
Bill Wendling48839d92009-05-17 05:52:39 +00001030<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001031<pre>
1032...
1033;;
Devang Patel4b945502010-03-09 00:44:10 +00001034;; Define the compile unit for the main source file "/Users/mine/sources/MySource.cpp".
Jim Laskeycec12a52006-03-14 18:08:46 +00001035;;
Devang Patel4b945502010-03-09 00:44:10 +00001036!2 = metadata !{
1037 i32 524305, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001038 i32 0, ;; Unused
1039 i32 4, ;; Language Id
1040 metadata !"MySource.cpp",
1041 metadata !"/Users/mine/sources",
1042 metadata !"4.2.1 (Based on Apple Inc. build 5649) (LLVM build 00)",
1043 i1 true, ;; Main Compile Unit
1044 i1 false, ;; Optimized compile unit
1045 metadata !"", ;; Compiler flags
1046 i32 0} ;; Runtime version
1047
Jim Laskeycec12a52006-03-14 18:08:46 +00001048;;
Devang Patel4b945502010-03-09 00:44:10 +00001049;; Define the file for the file "/Users/mine/sources/MySource.cpp".
Jim Laskeycec12a52006-03-14 18:08:46 +00001050;;
Devang Patele4b27562009-08-28 23:24:31 +00001051!1 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001052 i32 524329, ;; Tag
1053 metadata !"MySource.cpp",
Devang Patele4b27562009-08-28 23:24:31 +00001054 metadata !"/Users/mine/sources",
Devang Patel4b945502010-03-09 00:44:10 +00001055 metadata !3 ;; Compile unit
1056}
1057
1058;;
1059;; Define the file for the file "/Users/mine/sources/Myheader.h"
1060;;
1061!3 = metadata !{
1062 i32 524329, ;; Tag
1063 metadata !"Myheader.h"
1064 metadata !"/Users/mine/sources",
1065 metadata !3 ;; Compile unit
1066}
Jim Laskeycec12a52006-03-14 18:08:46 +00001067
Jim Laskeycec12a52006-03-14 18:08:46 +00001068...
1069</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001070</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001071
Devang Pateld98ec5f2010-03-26 19:08:36 +00001072<p>llvm::Instruction provides easy access to metadata attached with an
1073instruction. One can extract line number information encoded in LLVM IR
1074using <tt>Instruction::getMetadata()</tt> and
1075<tt>DILocation::getLineNumber()</tt>.
1076<pre>
1077 if (MDNode *N = I->getMetadata("dbg")) { // Here I is an LLVM instruction
1078 DILocation Loc(N); // DILocation is in DebugInfo.h
1079 unsigned Line = Loc.getLineNumber();
1080 StringRef File = Loc.getFilename();
1081 StringRef Dir = Loc.getDirectory();
1082 }
1083</pre>
Chris Lattner8ff75902004-01-06 05:31:32 +00001084</div>
1085
1086<!-- ======================================================================= -->
1087<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +00001088 <a name="ccxx_global_variable">C/C++ global variable information</a>
Chris Lattner8ff75902004-01-06 05:31:32 +00001089</div>
1090
1091<div class="doc_text">
Jim Laskeycec12a52006-03-14 18:08:46 +00001092
Misha Brukman96e00812008-12-16 02:54:22 +00001093<p>Given an integer global variable declared as follows:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001094
Bill Wendling48839d92009-05-17 05:52:39 +00001095<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001096<pre>
1097int MyGlobal = 100;
1098</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001099</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001100
Misha Brukman96e00812008-12-16 02:54:22 +00001101<p>a C/C++ front-end would generate the following descriptors:</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>
1105;;
Jim Laskeycec12a52006-03-14 18:08:46 +00001106;; Define the global itself.
1107;;
1108%MyGlobal = global int 100
1109...
1110;;
Devang Patele4b27562009-08-28 23:24:31 +00001111;; List of debug info of globals
Jim Laskeycec12a52006-03-14 18:08:46 +00001112;;
Devang Patele4b27562009-08-28 23:24:31 +00001113!llvm.dbg.gv = !{!0}
Jim Laskeycec12a52006-03-14 18:08:46 +00001114
1115;;
1116;; Define the global variable descriptor. Note the reference to the global
1117;; variable anchor and the global variable itself.
1118;;
Devang Patele4b27562009-08-28 23:24:31 +00001119!0 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001120 i32 524340, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001121 i32 0, ;; Unused
1122 metadata !1, ;; Context
1123 metadata !"MyGlobal", ;; Name
1124 metadata !"MyGlobal", ;; Display Name
1125 metadata !"MyGlobal", ;; Linkage Name
Devang Patel4b945502010-03-09 00:44:10 +00001126 metadata !3, ;; Compile Unit
Devang Patele4b27562009-08-28 23:24:31 +00001127 i32 1, ;; Line Number
Devang Patel4b945502010-03-09 00:44:10 +00001128 metadata !4, ;; Type
Devang Patele4b27562009-08-28 23:24:31 +00001129 i1 false, ;; Is a local variable
1130 i1 true, ;; Is this a definition
1131 i32* @MyGlobal ;; The global variable
1132}
1133
Jim Laskeycec12a52006-03-14 18:08:46 +00001134;;
1135;; Define the basic type of 32 bit signed integer. Note that since int is an
1136;; intrinsic type the source file is NULL and line 0.
1137;;
Devang Patel4b945502010-03-09 00:44:10 +00001138!4 = metadata !{
1139 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001140 metadata !1, ;; Context
1141 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001142 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001143 i32 0, ;; Line number
1144 i64 32, ;; Size in Bits
1145 i64 32, ;; Align in Bits
1146 i64 0, ;; Offset in Bits
1147 i32 0, ;; Flags
1148 i32 5 ;; Encoding
1149}
Jim Laskeycec12a52006-03-14 18:08:46 +00001150
Jim Laskeycec12a52006-03-14 18:08:46 +00001151</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001152</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001153
Chris Lattner8ff75902004-01-06 05:31:32 +00001154</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001155
Jim Laskeycec12a52006-03-14 18:08:46 +00001156<!-- ======================================================================= -->
1157<div class="doc_subsection">
1158 <a name="ccxx_subprogram">C/C++ function information</a>
1159</div>
1160
1161<div class="doc_text">
1162
Misha Brukman96e00812008-12-16 02:54:22 +00001163<p>Given a function declared as follows:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001164
Bill Wendling48839d92009-05-17 05:52:39 +00001165<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001166<pre>
1167int main(int argc, char *argv[]) {
1168 return 0;
1169}
1170</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001171</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001172
Misha Brukman96e00812008-12-16 02:54:22 +00001173<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001174
Bill Wendling48839d92009-05-17 05:52:39 +00001175<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001176<pre>
1177;;
Jim Laskeycec12a52006-03-14 18:08:46 +00001178;; Define the anchor for subprograms. Note that the second field of the
1179;; anchor is 46, which is the same as the tag for subprograms
1180;; (46 = DW_TAG_subprogram.)
1181;;
Devang Patel4b945502010-03-09 00:44:10 +00001182!6 = metadata !{
1183 i32 524334, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001184 i32 0, ;; Unused
1185 metadata !1, ;; Context
1186 metadata !"main", ;; Name
1187 metadata !"main", ;; Display name
1188 metadata !"main", ;; Linkage name
Devang Patel4b945502010-03-09 00:44:10 +00001189 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001190 i32 1, ;; Line number
Devang Patel4b945502010-03-09 00:44:10 +00001191 metadata !4, ;; Type
Devang Patele4b27562009-08-28 23:24:31 +00001192 i1 false, ;; Is local
1193 i1 true ;; Is definition
1194}
Jim Laskeycec12a52006-03-14 18:08:46 +00001195;;
1196;; Define the subprogram itself.
1197;;
Devang Patele4b27562009-08-28 23:24:31 +00001198define i32 @main(i32 %argc, i8** %argv) {
Jim Laskeycec12a52006-03-14 18:08:46 +00001199...
1200}
1201</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001202</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001203
1204</div>
1205
1206<!-- ======================================================================= -->
1207<div class="doc_subsection">
1208 <a name="ccxx_basic_types">C/C++ basic types</a>
1209</div>
1210
1211<div class="doc_text">
1212
Misha Brukman96e00812008-12-16 02:54:22 +00001213<p>The following are the basic type descriptors for C/C++ core types:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001214
1215</div>
1216
1217<!-- ======================================================================= -->
1218<div class="doc_subsubsection">
1219 <a name="ccxx_basic_type_bool">bool</a>
1220</div>
1221
1222<div class="doc_text">
1223
Bill Wendling48839d92009-05-17 05:52:39 +00001224<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001225<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001226!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001227 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001228 metadata !1, ;; Context
1229 metadata !"bool", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001230 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001231 i32 0, ;; Line number
1232 i64 8, ;; Size in Bits
1233 i64 8, ;; Align in Bits
1234 i64 0, ;; Offset in Bits
1235 i32 0, ;; Flags
1236 i32 2 ;; Encoding
1237}
Jim Laskeycec12a52006-03-14 18:08:46 +00001238</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001239</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001240
1241</div>
1242
1243<!-- ======================================================================= -->
1244<div class="doc_subsubsection">
1245 <a name="ccxx_basic_char">char</a>
1246</div>
1247
1248<div class="doc_text">
1249
Bill Wendling48839d92009-05-17 05:52:39 +00001250<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001251<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001252!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001253 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001254 metadata !1, ;; Context
1255 metadata !"char", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001256 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001257 i32 0, ;; Line number
1258 i64 8, ;; Size in Bits
1259 i64 8, ;; Align in Bits
1260 i64 0, ;; Offset in Bits
1261 i32 0, ;; Flags
1262 i32 6 ;; Encoding
1263}
Jim Laskeycec12a52006-03-14 18:08:46 +00001264</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001265</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001266
1267</div>
1268
1269<!-- ======================================================================= -->
1270<div class="doc_subsubsection">
1271 <a name="ccxx_basic_unsigned_char">unsigned char</a>
1272</div>
1273
1274<div class="doc_text">
1275
Bill Wendling48839d92009-05-17 05:52:39 +00001276<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001277<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001278!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001279 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001280 metadata !1, ;; Context
1281 metadata !"unsigned char",
Devang Patel4b945502010-03-09 00:44:10 +00001282 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001283 i32 0, ;; Line number
1284 i64 8, ;; Size in Bits
1285 i64 8, ;; Align in Bits
1286 i64 0, ;; Offset in Bits
1287 i32 0, ;; Flags
1288 i32 8 ;; Encoding
1289}
Jim Laskeycec12a52006-03-14 18:08:46 +00001290</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001291</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001292
1293</div>
1294
1295<!-- ======================================================================= -->
1296<div class="doc_subsubsection">
1297 <a name="ccxx_basic_short">short</a>
1298</div>
1299
1300<div class="doc_text">
1301
Bill Wendling48839d92009-05-17 05:52:39 +00001302<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001303<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001304!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001305 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001306 metadata !1, ;; Context
1307 metadata !"short int",
Devang Patel4b945502010-03-09 00:44:10 +00001308 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001309 i32 0, ;; Line number
1310 i64 16, ;; Size in Bits
1311 i64 16, ;; Align in Bits
1312 i64 0, ;; Offset in Bits
1313 i32 0, ;; Flags
1314 i32 5 ;; Encoding
1315}
Jim Laskeycec12a52006-03-14 18:08:46 +00001316</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001317</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001318
1319</div>
1320
1321<!-- ======================================================================= -->
1322<div class="doc_subsubsection">
1323 <a name="ccxx_basic_unsigned_short">unsigned short</a>
1324</div>
1325
1326<div class="doc_text">
1327
Bill Wendling48839d92009-05-17 05:52:39 +00001328<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001329<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001330!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001331 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001332 metadata !1, ;; Context
1333 metadata !"short unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001334 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001335 i32 0, ;; Line number
1336 i64 16, ;; Size in Bits
1337 i64 16, ;; Align in Bits
1338 i64 0, ;; Offset in Bits
1339 i32 0, ;; Flags
1340 i32 7 ;; Encoding
1341}
Jim Laskeycec12a52006-03-14 18:08:46 +00001342</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001343</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001344
1345</div>
1346
1347<!-- ======================================================================= -->
1348<div class="doc_subsubsection">
1349 <a name="ccxx_basic_int">int</a>
1350</div>
1351
1352<div class="doc_text">
1353
Bill Wendling48839d92009-05-17 05:52:39 +00001354<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001355<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001356!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001357 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001358 metadata !1, ;; Context
1359 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001360 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001361 i32 0, ;; Line number
1362 i64 32, ;; Size in Bits
1363 i64 32, ;; Align in Bits
1364 i64 0, ;; Offset in Bits
1365 i32 0, ;; Flags
1366 i32 5 ;; Encoding
1367}
Bill Wendling48839d92009-05-17 05:52:39 +00001368</pre></div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001369
1370</div>
1371
1372<!-- ======================================================================= -->
1373<div class="doc_subsubsection">
1374 <a name="ccxx_basic_unsigned_int">unsigned int</a>
1375</div>
1376
1377<div class="doc_text">
1378
Bill Wendling48839d92009-05-17 05:52:39 +00001379<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001380<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001381!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001382 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001383 metadata !1, ;; Context
1384 metadata !"unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001385 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001386 i32 0, ;; Line number
1387 i64 32, ;; Size in Bits
1388 i64 32, ;; Align in Bits
1389 i64 0, ;; Offset in Bits
1390 i32 0, ;; Flags
1391 i32 7 ;; Encoding
1392}
Jim Laskeycec12a52006-03-14 18:08:46 +00001393</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001394</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001395
1396</div>
1397
1398<!-- ======================================================================= -->
1399<div class="doc_subsubsection">
1400 <a name="ccxx_basic_long_long">long long</a>
1401</div>
1402
1403<div class="doc_text">
1404
Bill Wendling48839d92009-05-17 05:52:39 +00001405<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001406<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001407!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001408 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001409 metadata !1, ;; Context
1410 metadata !"long long int",
Devang Patel4b945502010-03-09 00:44:10 +00001411 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001412 i32 0, ;; Line number
1413 i64 64, ;; Size in Bits
1414 i64 64, ;; Align in Bits
1415 i64 0, ;; Offset in Bits
1416 i32 0, ;; Flags
1417 i32 5 ;; Encoding
1418}
Jim Laskeycec12a52006-03-14 18:08:46 +00001419</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001420</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001421
1422</div>
1423
1424<!-- ======================================================================= -->
1425<div class="doc_subsubsection">
1426 <a name="ccxx_basic_unsigned_long_long">unsigned long long</a>
1427</div>
1428
1429<div class="doc_text">
1430
Bill Wendling48839d92009-05-17 05:52:39 +00001431<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001432<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001433!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001434 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001435 metadata !1, ;; Context
1436 metadata !"long long unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001437 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001438 i32 0, ;; Line number
1439 i64 64, ;; Size in Bits
1440 i64 64, ;; Align in Bits
1441 i64 0, ;; Offset in Bits
1442 i32 0, ;; Flags
1443 i32 7 ;; Encoding
1444}
Jim Laskeycec12a52006-03-14 18:08:46 +00001445</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001446</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001447
1448</div>
1449
1450<!-- ======================================================================= -->
1451<div class="doc_subsubsection">
1452 <a name="ccxx_basic_float">float</a>
1453</div>
1454
1455<div class="doc_text">
1456
Bill Wendling48839d92009-05-17 05:52:39 +00001457<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001458<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001459!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001460 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001461 metadata !1, ;; Context
1462 metadata !"float",
Devang Patel4b945502010-03-09 00:44:10 +00001463 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001464 i32 0, ;; Line number
1465 i64 32, ;; Size in Bits
1466 i64 32, ;; Align in Bits
1467 i64 0, ;; Offset in Bits
1468 i32 0, ;; Flags
1469 i32 4 ;; Encoding
1470}
Jim Laskeycec12a52006-03-14 18:08:46 +00001471</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001472</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001473
1474</div>
1475
1476<!-- ======================================================================= -->
1477<div class="doc_subsubsection">
1478 <a name="ccxx_basic_double">double</a>
1479</div>
1480
1481<div class="doc_text">
1482
Bill Wendling48839d92009-05-17 05:52:39 +00001483<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001484<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001485!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001486 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001487 metadata !1, ;; Context
1488 metadata !"double",;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001489 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001490 i32 0, ;; Line number
1491 i64 64, ;; Size in Bits
1492 i64 64, ;; Align in Bits
1493 i64 0, ;; Offset in Bits
1494 i32 0, ;; Flags
1495 i32 4 ;; Encoding
1496}
Jim Laskeycec12a52006-03-14 18:08:46 +00001497</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001498</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001499
1500</div>
1501
1502<!-- ======================================================================= -->
1503<div class="doc_subsection">
1504 <a name="ccxx_derived_types">C/C++ derived types</a>
1505</div>
1506
1507<div class="doc_text">
1508
Misha Brukman96e00812008-12-16 02:54:22 +00001509<p>Given the following as an example of C/C++ derived type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001510
Bill Wendling48839d92009-05-17 05:52:39 +00001511<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001512<pre>
1513typedef const int *IntPtr;
1514</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001515</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001516
Misha Brukman96e00812008-12-16 02:54:22 +00001517<p>a C/C++ front-end would generate the following descriptors:</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>
1521;;
1522;; Define the typedef "IntPtr".
1523;;
Devang Patele4b27562009-08-28 23:24:31 +00001524!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001525 i32 524310, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001526 metadata !1, ;; Context
1527 metadata !"IntPtr", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001528 metadata !3, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001529 i32 0, ;; Line number
1530 i64 0, ;; Size in bits
1531 i64 0, ;; Align in bits
1532 i64 0, ;; Offset in bits
1533 i32 0, ;; Flags
1534 metadata !4 ;; Derived From type
1535}
Jim Laskeycec12a52006-03-14 18:08:46 +00001536
1537;;
1538;; Define the pointer type.
1539;;
Devang Patele4b27562009-08-28 23:24:31 +00001540!4 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001541 i32 524303, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001542 metadata !1, ;; Context
1543 metadata !"", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001544 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001545 i32 0, ;; Line number
1546 i64 64, ;; Size in bits
1547 i64 64, ;; Align in bits
1548 i64 0, ;; Offset in bits
1549 i32 0, ;; Flags
1550 metadata !5 ;; Derived From type
1551}
Jim Laskeycec12a52006-03-14 18:08:46 +00001552;;
1553;; Define the const type.
1554;;
Devang Patele4b27562009-08-28 23:24:31 +00001555!5 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001556 i32 524326, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001557 metadata !1, ;; Context
1558 metadata !"", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001559 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001560 i32 0, ;; Line number
1561 i64 32, ;; Size in bits
1562 i64 32, ;; Align in bits
1563 i64 0, ;; Offset in bits
1564 i32 0, ;; Flags
1565 metadata !6 ;; Derived From type
1566}
Jim Laskeycec12a52006-03-14 18:08:46 +00001567;;
1568;; Define the int type.
1569;;
Devang Patele4b27562009-08-28 23:24:31 +00001570!6 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001571 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001572 metadata !1, ;; Context
1573 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001574 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001575 i32 0, ;; Line number
1576 i64 32, ;; Size in bits
1577 i64 32, ;; Align in bits
1578 i64 0, ;; Offset in bits
1579 i32 0, ;; Flags
1580 5 ;; Encoding
1581}
Jim Laskeycec12a52006-03-14 18:08:46 +00001582</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001583</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001584
1585</div>
1586
1587<!-- ======================================================================= -->
1588<div class="doc_subsection">
1589 <a name="ccxx_composite_types">C/C++ struct/union types</a>
1590</div>
1591
1592<div class="doc_text">
1593
Misha Brukman96e00812008-12-16 02:54:22 +00001594<p>Given the following as an example of C/C++ struct type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001595
Bill Wendling48839d92009-05-17 05:52:39 +00001596<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001597<pre>
1598struct Color {
1599 unsigned Red;
1600 unsigned Green;
1601 unsigned Blue;
1602};
1603</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001604</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001605
Misha Brukman96e00812008-12-16 02:54:22 +00001606<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001607
Bill Wendling48839d92009-05-17 05:52:39 +00001608<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001609<pre>
1610;;
1611;; Define basic type for unsigned int.
1612;;
Devang Patele4b27562009-08-28 23:24:31 +00001613!5 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001614 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001615 metadata !1, ;; Context
1616 metadata !"unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001617 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001618 i32 0, ;; Line number
1619 i64 32, ;; Size in Bits
1620 i64 32, ;; Align in Bits
1621 i64 0, ;; Offset in Bits
1622 i32 0, ;; Flags
1623 i32 7 ;; Encoding
1624}
Jim Laskeycec12a52006-03-14 18:08:46 +00001625;;
1626;; Define composite type for struct Color.
1627;;
Devang Patele4b27562009-08-28 23:24:31 +00001628!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001629 i32 524307, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001630 metadata !1, ;; Context
1631 metadata !"Color", ;; Name
1632 metadata !1, ;; Compile unit
1633 i32 1, ;; Line number
1634 i64 96, ;; Size in bits
1635 i64 32, ;; Align in bits
1636 i64 0, ;; Offset in bits
1637 i32 0, ;; Flags
1638 null, ;; Derived From
1639 metadata !3, ;; Elements
1640 i32 0 ;; Runtime Language
1641}
Jim Laskeycec12a52006-03-14 18:08:46 +00001642
1643;;
1644;; Define the Red field.
1645;;
Devang Patele4b27562009-08-28 23:24:31 +00001646!4 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001647 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001648 metadata !1, ;; Context
1649 metadata !"Red", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001650 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001651 i32 2, ;; Line number
1652 i64 32, ;; Size in bits
1653 i64 32, ;; Align in bits
1654 i64 0, ;; Offset in bits
1655 i32 0, ;; Flags
1656 metadata !5 ;; Derived From type
1657}
Jim Laskeycec12a52006-03-14 18:08:46 +00001658
1659;;
1660;; Define the Green field.
1661;;
Devang Patele4b27562009-08-28 23:24:31 +00001662!6 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001663 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001664 metadata !1, ;; Context
1665 metadata !"Green", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001666 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001667 i32 3, ;; Line number
1668 i64 32, ;; Size in bits
1669 i64 32, ;; Align in bits
1670 i64 32, ;; Offset in bits
1671 i32 0, ;; Flags
1672 metadata !5 ;; Derived From type
1673}
Jim Laskeycec12a52006-03-14 18:08:46 +00001674
1675;;
1676;; Define the Blue field.
1677;;
Devang Patele4b27562009-08-28 23:24:31 +00001678!7 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001679 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001680 metadata !1, ;; Context
1681 metadata !"Blue", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001682 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001683 i32 4, ;; Line number
1684 i64 32, ;; Size in bits
1685 i64 32, ;; Align in bits
1686 i64 64, ;; Offset in bits
1687 i32 0, ;; Flags
1688 metadata !5 ;; Derived From type
1689}
Jim Laskeycec12a52006-03-14 18:08:46 +00001690
1691;;
1692;; Define the array of fields used by the composite type Color.
1693;;
Devang Patele4b27562009-08-28 23:24:31 +00001694!3 = metadata !{metadata !4, metadata !6, metadata !7}
Jim Laskeycec12a52006-03-14 18:08:46 +00001695</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001696</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001697
1698</div>
1699
1700<!-- ======================================================================= -->
1701<div class="doc_subsection">
1702 <a name="ccxx_enumeration_types">C/C++ enumeration types</a>
1703</div>
1704
1705<div class="doc_text">
1706
Misha Brukman96e00812008-12-16 02:54:22 +00001707<p>Given the following as an example of C/C++ enumeration type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001708
Bill Wendling48839d92009-05-17 05:52:39 +00001709<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001710<pre>
1711enum Trees {
1712 Spruce = 100,
1713 Oak = 200,
1714 Maple = 300
1715};
1716</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001717</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001718
Misha Brukman96e00812008-12-16 02:54:22 +00001719<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001720
Bill Wendling48839d92009-05-17 05:52:39 +00001721<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001722<pre>
1723;;
1724;; Define composite type for enum Trees
1725;;
Devang Patele4b27562009-08-28 23:24:31 +00001726!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001727 i32 524292, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001728 metadata !1, ;; Context
1729 metadata !"Trees", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001730 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001731 i32 1, ;; Line number
1732 i64 32, ;; Size in bits
1733 i64 32, ;; Align in bits
1734 i64 0, ;; Offset in bits
1735 i32 0, ;; Flags
1736 null, ;; Derived From type
1737 metadata !3, ;; Elements
1738 i32 0 ;; Runtime language
1739}
Devang Patel2a610c72009-08-25 05:24:07 +00001740
Devang Patel82459882009-08-26 05:01:18 +00001741;;
1742;; Define the array of enumerators used by composite type Trees.
1743;;
Devang Patele4b27562009-08-28 23:24:31 +00001744!3 = metadata !{metadata !4, metadata !5, metadata !6}
1745
1746;;
1747;; Define Spruce enumerator.
1748;;
Devang Patel4b945502010-03-09 00:44:10 +00001749!4 = metadata !{i32 524328, metadata !"Spruce", i64 100}
Devang Patele4b27562009-08-28 23:24:31 +00001750
1751;;
1752;; Define Oak enumerator.
1753;;
Devang Patel4b945502010-03-09 00:44:10 +00001754!5 = metadata !{i32 524328, metadata !"Oak", i64 200}
Devang Patele4b27562009-08-28 23:24:31 +00001755
1756;;
1757;; Define Maple enumerator.
1758;;
Devang Patel4b945502010-03-09 00:44:10 +00001759!6 = metadata !{i32 524328, metadata !"Maple", i64 300}
Devang Patele4b27562009-08-28 23:24:31 +00001760
Jim Laskeycec12a52006-03-14 18:08:46 +00001761</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001762</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001763
1764</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001765
1766<!-- *********************************************************************** -->
Misha Brukman82873732004-05-12 19:21:57 +00001767
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001768<hr>
Misha Brukman82873732004-05-12 19:21:57 +00001769<address>
1770 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001771 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman82873732004-05-12 19:21:57 +00001772 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001773 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman82873732004-05-12 19:21:57 +00001774
1775 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001776 <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001777 Last modified: $Date$
Misha Brukman82873732004-05-12 19:21:57 +00001778</address>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001779
1780</body>
1781</html>