blob: c786a7d0a815293d391727dcc47abb74ae3975ab [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
Chris Lattner89940752011-01-18 06:12:10 +000081 for C/C++ looks like.</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
Devang Patelda6eed32011-03-29 17:27:08 +0000410provide details such as name, type and where the variable is defined. All
411global variables are collected by named metadata <tt>!llvm.dbg.gv</tt>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000412
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)
Devang Patel80ecc152010-06-04 22:49:55 +0000437 i32 ;; Virtuality, e.g. dwarf::DW_VIRTUALITY__virtual
438 i32 ;; Index into a virtual function
439 metadata, ;; indicates which base type contains the vtable pointer for the
440 ;; derived class
441 i1 ;; isArtificial
442 i1 ;; isOptimized
443 Function *;; Pointer to LLVM function
Bill Wendling48839d92009-05-17 05:52:39 +0000444}
Jim Laskeycec12a52006-03-14 18:08:46 +0000445</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000446</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000447
448<p>These descriptors provide debug information about functions, methods and
Bill Wendling48839d92009-05-17 05:52:39 +0000449 subprograms. They provide details such as name, return types and the source
Devang Patelda6eed32011-03-29 17:27:08 +0000450 location where the subprogram is defined.
451 All subprogram descriptors are collected by a named metadata
452 <tt>!llvm.dbg.sp</tt>.
453</p>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000454
455</div>
Bill Wendling48839d92009-05-17 05:52:39 +0000456
Jim Laskey3d11bee2006-03-15 19:10:52 +0000457<!-- ======================================================================= -->
458<div class="doc_subsubsection">
459 <a name="format_blocks">Block descriptors</a>
460</div>
461
462<div class="doc_text">
463
Bill Wendling48839d92009-05-17 05:52:39 +0000464<div class="doc_code">
Jim Laskey3d11bee2006-03-15 19:10:52 +0000465<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000466!3 = metadata !{
Devang Patelc79dda22010-10-04 16:51:59 +0000467 i32, ;; Tag = 11 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_lexical_block)
Devang Patel7f271fc2010-10-01 22:45:00 +0000468 metadata,;; Reference to context descriptor
469 i32, ;; Line number
Devang Patel90d81f12011-03-08 16:25:29 +0000470 i32, ;; Column number
471 metadata,;; Reference to source file
472 i32 ;; Unique ID to identify blocks from a template function
Bill Wendling48839d92009-05-17 05:52:39 +0000473}
Jim Laskey3d11bee2006-03-15 19:10:52 +0000474</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000475</div>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000476
477<p>These descriptors provide debug information about nested blocks within a
Devang Patel7f271fc2010-10-01 22:45:00 +0000478 subprogram. The line number and column numbers are used to dinstinguish
479 two lexical blocks at same depth. </p>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000480
Jim Laskeycec12a52006-03-14 18:08:46 +0000481</div>
482
483<!-- ======================================================================= -->
484<div class="doc_subsubsection">
485 <a name="format_basic_type">Basic type descriptors</a>
486</div>
487
488<div class="doc_text">
489
Bill Wendling48839d92009-05-17 05:52:39 +0000490<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000491<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000492!4 = metadata !{
493 i32, ;; Tag = 36 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
494 ;; (DW_TAG_base_type)
495 metadata, ;; Reference to context (typically a compile unit)
496 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000497 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000498 i32, ;; Line number where defined (may be 0)
499 i64, ;; Size in bits
500 i64, ;; Alignment in bits
501 i64, ;; Offset in bits
502 i32, ;; Flags
503 i32 ;; DWARF type encoding
Bill Wendling48839d92009-05-17 05:52:39 +0000504}
Jim Laskeycec12a52006-03-14 18:08:46 +0000505</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000506</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000507
508<p>These descriptors define primitive types used in the code. Example int, bool
Bill Wendling48839d92009-05-17 05:52:39 +0000509 and float. The context provides the scope of the type, which is usually the
510 top level. Since basic types are not usually user defined the compile unit
511 and line number can be left as NULL and 0. The size, alignment and offset
512 are expressed in bits and can be 64 bit values. The alignment is used to
513 round the offset when embedded in a
514 <a href="#format_composite_type">composite type</a> (example to keep float
515 doubles on 64 bit boundaries.) The offset is the bit offset if embedded in
516 a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000517
518<p>The type encoding provides the details of the type. The values are typically
Bill Wendling48839d92009-05-17 05:52:39 +0000519 one of the following:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000520
Bill Wendling48839d92009-05-17 05:52:39 +0000521<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000522<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000523DW_ATE_address = 1
524DW_ATE_boolean = 2
525DW_ATE_float = 4
526DW_ATE_signed = 5
527DW_ATE_signed_char = 6
528DW_ATE_unsigned = 7
529DW_ATE_unsigned_char = 8
Jim Laskeycec12a52006-03-14 18:08:46 +0000530</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000531</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000532
533</div>
534
535<!-- ======================================================================= -->
536<div class="doc_subsubsection">
537 <a name="format_derived_type">Derived type descriptors</a>
538</div>
539
540<div class="doc_text">
541
Bill Wendling48839d92009-05-17 05:52:39 +0000542<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000543<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000544!5 = metadata !{
545 i32, ;; Tag (see below)
546 metadata, ;; Reference to context
547 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000548 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000549 i32, ;; Line number where defined (may be 0)
Devang Patel0ffd10b2010-10-01 19:19:30 +0000550 i64, ;; Size in bits
551 i64, ;; Alignment in bits
552 i64, ;; Offset in bits
Devang Patele4b27562009-08-28 23:24:31 +0000553 metadata ;; Reference to type derived from
Bill Wendling48839d92009-05-17 05:52:39 +0000554}
Jim Laskeycec12a52006-03-14 18:08:46 +0000555</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000556</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000557
558<p>These descriptors are used to define types derived from other types. The
559value of the tag varies depending on the meaning. The following are possible
Misha Brukman96e00812008-12-16 02:54:22 +0000560tag values:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000561
Bill Wendling48839d92009-05-17 05:52:39 +0000562<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000563<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000564DW_TAG_formal_parameter = 5
565DW_TAG_member = 13
566DW_TAG_pointer_type = 15
567DW_TAG_reference_type = 16
568DW_TAG_typedef = 22
569DW_TAG_const_type = 38
570DW_TAG_volatile_type = 53
571DW_TAG_restrict_type = 55
Jim Laskeycec12a52006-03-14 18:08:46 +0000572</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000573</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000574
Bill Wendling48839d92009-05-17 05:52:39 +0000575<p><tt>DW_TAG_member</tt> is used to define a member of
576 a <a href="#format_composite_type">composite type</a>
577 or <a href="#format_subprograms">subprogram</a>. The type of the member is
578 the <a href="#format_derived_type">derived
579 type</a>. <tt>DW_TAG_formal_parameter</tt> is used to define a member which
580 is a formal argument of a subprogram.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000581
Bill Wendling48839d92009-05-17 05:52:39 +0000582<p><tt>DW_TAG_typedef</tt> is used to provide a name for the derived type.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000583
Bill Wendling48839d92009-05-17 05:52:39 +0000584<p><tt>DW_TAG_pointer_type</tt>,<tt>DW_TAG_reference_type</tt>,
585 <tt>DW_TAG_const_type</tt>, <tt>DW_TAG_volatile_type</tt>
586 and <tt>DW_TAG_restrict_type</tt> are used to qualify
587 the <a href="#format_derived_type">derived type</a>. </p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000588
589<p><a href="#format_derived_type">Derived type</a> location can be determined
Bill Wendling48839d92009-05-17 05:52:39 +0000590 from the compile unit and line number. The size, alignment and offset are
591 expressed in bits and can be 64 bit values. The alignment is used to round
592 the offset when embedded in a <a href="#format_composite_type">composite
593 type</a> (example to keep float doubles on 64 bit boundaries.) The offset is
594 the bit offset if embedded in a <a href="#format_composite_type">composite
595 type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000596
Devang Patel37280782011-02-03 00:22:17 +0000597<p>Note that the <tt>void *</tt> type is expressed as a type derived from NULL.
598</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000599
600</div>
601
602<!-- ======================================================================= -->
603<div class="doc_subsubsection">
604 <a name="format_composite_type">Composite type descriptors</a>
605</div>
606
607<div class="doc_text">
608
Bill Wendling48839d92009-05-17 05:52:39 +0000609<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000610<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000611!6 = metadata !{
612 i32, ;; Tag (see below)
613 metadata, ;; Reference to context
614 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000615 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000616 i32, ;; Line number where defined (may be 0)
617 i64, ;; Size in bits
618 i64, ;; Alignment in bits
619 i64, ;; Offset in bits
620 i32, ;; Flags
621 metadata, ;; Reference to type derived from
622 metadata, ;; Reference to array of member descriptors
623 i32 ;; Runtime languages
Bill Wendling48839d92009-05-17 05:52:39 +0000624}
Jim Laskeycec12a52006-03-14 18:08:46 +0000625</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000626</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000627
628<p>These descriptors are used to define types that are composed of 0 or more
629elements. The value of the tag varies depending on the meaning. The following
Misha Brukman96e00812008-12-16 02:54:22 +0000630are possible tag values:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000631
Bill Wendling48839d92009-05-17 05:52:39 +0000632<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000633<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000634DW_TAG_array_type = 1
635DW_TAG_enumeration_type = 4
636DW_TAG_structure_type = 19
637DW_TAG_union_type = 23
638DW_TAG_vector_type = 259
Bruno Cardoso Lopesd80ddc02009-05-29 17:08:57 +0000639DW_TAG_subroutine_type = 21
640DW_TAG_inheritance = 28
Jim Laskeycec12a52006-03-14 18:08:46 +0000641</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000642</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000643
Jim Laskeyf8a01a92006-06-15 20:51:43 +0000644<p>The vector flag indicates that an array type is a native packed vector.</p>
645
Jim Laskey7089f452006-06-16 13:14:03 +0000646<p>The members of array types (tag = <tt>DW_TAG_array_type</tt>) or vector types
Bill Wendling48839d92009-05-17 05:52:39 +0000647 (tag = <tt>DW_TAG_vector_type</tt>) are <a href="#format_subrange">subrange
648 descriptors</a>, each representing the range of subscripts at that level of
649 indexing.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000650
651<p>The members of enumeration types (tag = <tt>DW_TAG_enumeration_type</tt>) are
Bill Wendling48839d92009-05-17 05:52:39 +0000652 <a href="#format_enumeration">enumerator descriptors</a>, each representing
Devang Patelda6eed32011-03-29 17:27:08 +0000653 the definition of enumeration value for the set. All enumeration type
654 descriptors are collected by named metadata <tt>!llvm.dbg.enum</tt>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000655
656<p>The members of structure (tag = <tt>DW_TAG_structure_type</tt>) or union (tag
Bill Wendling48839d92009-05-17 05:52:39 +0000657 = <tt>DW_TAG_union_type</tt>) types are any one of
658 the <a href="#format_basic_type">basic</a>,
659 <a href="#format_derived_type">derived</a>
660 or <a href="#format_composite_type">composite</a> type descriptors, each
661 representing a field member of the structure or union.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000662
Jim Laskey4a9df242006-08-21 21:21:06 +0000663<p>For C++ classes (tag = <tt>DW_TAG_structure_type</tt>), member descriptors
Bill Wendling48839d92009-05-17 05:52:39 +0000664 provide information about base classes, static members and member
665 functions. If a member is a <a href="#format_derived_type">derived type
666 descriptor</a> and has a tag of <tt>DW_TAG_inheritance</tt>, then the type
667 represents a base class. If the member of is
668 a <a href="#format_global_variables">global variable descriptor</a> then it
669 represents a static member. And, if the member is
670 a <a href="#format_subprograms">subprogram descriptor</a> then it represents
671 a member function. For static members and member
672 functions, <tt>getName()</tt> returns the members link or the C++ mangled
673 name. <tt>getDisplayName()</tt> the simplied version of the name.</p>
Jim Laskey4a9df242006-08-21 21:21:06 +0000674
Bill Wendling48839d92009-05-17 05:52:39 +0000675<p>The first member of subroutine (tag = <tt>DW_TAG_subroutine_type</tt>) type
676 elements is the return type for the subroutine. The remaining elements are
677 the formal arguments to the subroutine.</p>
Jim Laskey094ee722006-06-20 21:13:20 +0000678
Jim Laskeycec12a52006-03-14 18:08:46 +0000679<p><a href="#format_composite_type">Composite type</a> location can be
Bill Wendling48839d92009-05-17 05:52:39 +0000680 determined from the compile unit and line number. The size, alignment and
681 offset are expressed in bits and can be 64 bit values. The alignment is used
682 to round the offset when embedded in
683 a <a href="#format_composite_type">composite type</a> (as an example, to keep
684 float doubles on 64 bit boundaries.) The offset is the bit offset if embedded
685 in a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000686
687</div>
688
689<!-- ======================================================================= -->
690<div class="doc_subsubsection">
691 <a name="format_subrange">Subrange descriptors</a>
692</div>
693
694<div class="doc_text">
695
Bill Wendling48839d92009-05-17 05:52:39 +0000696<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000697<pre>
Devang Patel37280782011-02-03 00:22:17 +0000698!42 = metadata !{
Bill Wendling48839d92009-05-17 05:52:39 +0000699 i32, ;; Tag = 33 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_subrange_type)
700 i64, ;; Low value
701 i64 ;; High value
702}
Jim Laskeycec12a52006-03-14 18:08:46 +0000703</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000704</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000705
706<p>These descriptors are used to define ranges of array subscripts for an array
Bill Wendling48839d92009-05-17 05:52:39 +0000707 <a href="#format_composite_type">composite type</a>. The low value defines
708 the lower bounds typically zero for C/C++. The high value is the upper
709 bounds. Values are 64 bit. High - low + 1 is the size of the array. If low
710 == high the array will be unbounded.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000711
712</div>
713
714<!-- ======================================================================= -->
715<div class="doc_subsubsection">
716 <a name="format_enumeration">Enumerator descriptors</a>
717</div>
718
719<div class="doc_text">
720
Bill Wendling48839d92009-05-17 05:52:39 +0000721<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000722<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000723!6 = metadata !{
724 i32, ;; Tag = 40 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
725 ;; (DW_TAG_enumerator)
726 metadata, ;; Name
727 i64 ;; Value
Bill Wendling48839d92009-05-17 05:52:39 +0000728}
Jim Laskeycec12a52006-03-14 18:08:46 +0000729</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000730</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000731
Bill Wendling48839d92009-05-17 05:52:39 +0000732<p>These descriptors are used to define members of an
733 enumeration <a href="#format_composite_type">composite type</a>, it
734 associates the name to the value.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000735
736</div>
737
738<!-- ======================================================================= -->
Jim Laskey383e0092006-03-23 17:54:33 +0000739<div class="doc_subsubsection">
740 <a name="format_variables">Local variables</a>
741</div>
742
743<div class="doc_text">
Bill Wendling48839d92009-05-17 05:52:39 +0000744
745<div class="doc_code">
Jim Laskey383e0092006-03-23 17:54:33 +0000746<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000747!7 = metadata !{
748 i32, ;; Tag (see below)
749 metadata, ;; Context
750 metadata, ;; Name
Devang Patel4b945502010-03-09 00:44:10 +0000751 metadata, ;; Reference to file where defined
Devang Patela83688f2011-03-08 16:29:40 +0000752 i32, ;; 24 bit - Line number where defined
753 ;; 8 bit - Argument number. 1 indicates 1st argument.
Devang Patele4b27562009-08-28 23:24:31 +0000754 metadata ;; Type descriptor
Bill Wendling48839d92009-05-17 05:52:39 +0000755}
Jim Laskey383e0092006-03-23 17:54:33 +0000756</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000757</div>
Jim Laskey383e0092006-03-23 17:54:33 +0000758
759<p>These descriptors are used to define variables local to a sub program. The
Bill Wendling48839d92009-05-17 05:52:39 +0000760 value of the tag depends on the usage of the variable:</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000761
Bill Wendling48839d92009-05-17 05:52:39 +0000762<div class="doc_code">
Jim Laskey383e0092006-03-23 17:54:33 +0000763<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000764DW_TAG_auto_variable = 256
765DW_TAG_arg_variable = 257
766DW_TAG_return_variable = 258
Jim Laskey383e0092006-03-23 17:54:33 +0000767</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000768</div>
Jim Laskey383e0092006-03-23 17:54:33 +0000769
770<p>An auto variable is any variable declared in the body of the function. An
Bill Wendling48839d92009-05-17 05:52:39 +0000771 argument variable is any variable that appears as a formal argument to the
772 function. A return variable is used to track the result of a function and
773 has no source correspondent.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000774
Jim Laskey2d395d92006-03-24 09:20:27 +0000775<p>The context is either the subprogram or block where the variable is defined.
Bill Wendling48839d92009-05-17 05:52:39 +0000776 Name the source variable name. Compile unit and line indicate where the
777 variable was defined. Type descriptor defines the declared type of the
778 variable.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000779
780</div>
781
782<!-- ======================================================================= -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000783<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000784 <a name="format_common_intrinsics">Debugger intrinsic functions</a>
785</div>
786
787<div class="doc_text">
788
789<p>LLVM uses several intrinsic functions (name prefixed with "llvm.dbg") to
Bill Wendling48839d92009-05-17 05:52:39 +0000790 provide debug information at various points in generated code.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000791
792</div>
793
794<!-- ======================================================================= -->
795<div class="doc_subsubsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000796 <a name="format_common_declare">llvm.dbg.declare</a>
797</div>
798
799<div class="doc_text">
800<pre>
Devang Patel4c7c0c62010-10-01 19:22:16 +0000801 void %<a href="#format_common_declare">llvm.dbg.declare</a>(metadata, metadata)
Jim Laskeycec12a52006-03-14 18:08:46 +0000802</pre>
803
Jim Laskey2d395d92006-03-24 09:20:27 +0000804<p>This intrinsic provides information about a local element (ex. variable.) The
Devang Patel4c7c0c62010-10-01 19:22:16 +0000805 first argument is metadata holding alloca for the variable.</tt>. The
Devang Patele136e502011-02-01 17:22:12 +0000806 second argument is metadata containing description of the variable. </p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000807</div>
808
809<!-- ======================================================================= -->
Victor Hernandez67a1a542010-01-11 22:53:48 +0000810<div class="doc_subsubsection">
811 <a name="format_common_value">llvm.dbg.value</a>
812</div>
813
814<div class="doc_text">
815<pre>
Dan Gohman3dfb3cf2010-05-28 17:07:41 +0000816 void %<a href="#format_common_value">llvm.dbg.value</a>(metadata, i64, metadata)
Victor Hernandez67a1a542010-01-11 22:53:48 +0000817</pre>
818
819<p>This intrinsic provides information when a user source variable is set to a
820 new value. The first argument is the new value (wrapped as metadata). The
821 second argument is the offset in the user source variable where the new value
Devang Patele136e502011-02-01 17:22:12 +0000822 is written. The third argument is metadata containing description of the
823 user source variable. </p>
Victor Hernandez67a1a542010-01-11 22:53:48 +0000824</div>
825
826<!-- ======================================================================= -->
Jim Laskeycec12a52006-03-14 18:08:46 +0000827<div class="doc_subsection">
Chris Lattner8ff75902004-01-06 05:31:32 +0000828 <a name="format_common_lifetime">Object lifetimes and scoping</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000829</div>
830
831<div class="doc_text">
Bill Wendlingcf493b82009-12-01 00:53:11 +0000832<p>In many languages, the local variables in functions can have their lifetimes
833 or scopes limited to a subset of a function. In the C family of languages,
Bill Wendling48839d92009-05-17 05:52:39 +0000834 for example, variables are only live (readable and writable) within the
835 source block that they are defined in. In functional languages, values are
836 only readable after they have been defined. Though this is a very obvious
Bill Wendlingcf493b82009-12-01 00:53:11 +0000837 concept, it is non-trivial to model in LLVM, because it has no notion of
Bill Wendling48839d92009-05-17 05:52:39 +0000838 scoping in this sense, and does not want to be tied to a language's scoping
839 rules.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000840
Bill Wendlingcf493b82009-12-01 00:53:11 +0000841<p>In order to handle this, the LLVM debug format uses the metadata attached to
Nick Lewycky655fd032010-03-31 07:50:17 +0000842 llvm instructions to encode line number and scoping information. Consider
843 the following C fragment, for example:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000844
Bill Wendling48839d92009-05-17 05:52:39 +0000845<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000846<pre>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008471. void foo() {
Devang Patel744950d2009-11-25 23:28:01 +00008482. int X = 21;
8493. int Y = 22;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008504. {
Devang Patel744950d2009-11-25 23:28:01 +00008515. int Z = 23;
8526. Z = X;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008537. }
Devang Patel744950d2009-11-25 23:28:01 +00008548. X = Y;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008559. }
Misha Brukman82873732004-05-12 19:21:57 +0000856</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000857</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000858
Jim Laskeycec12a52006-03-14 18:08:46 +0000859<p>Compiled to LLVM, this function would be represented like this:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000860
Bill Wendling48839d92009-05-17 05:52:39 +0000861<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000862<pre>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000863define void @foo() nounwind ssp {
Jim Laskeycec12a52006-03-14 18:08:46 +0000864entry:
Bill Wendling02216ff2009-12-01 00:59:58 +0000865 %X = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
866 %Y = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
867 %Z = alloca i32, align 4 ; &lt;i32*&gt; [#uses=3]
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000868 %0 = bitcast i32* %X to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel37280782011-02-03 00:22:17 +0000869 call void @llvm.dbg.declare(metadata !{i32 * %X}, metadata !0), !dbg !7
Devang Patel744950d2009-11-25 23:28:01 +0000870 store i32 21, i32* %X, !dbg !8
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000871 %1 = bitcast i32* %Y to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel37280782011-02-03 00:22:17 +0000872 call void @llvm.dbg.declare(metadata !{i32 * %Y}, metadata !9), !dbg !10
Devang Patel744950d2009-11-25 23:28:01 +0000873 store i32 22, i32* %Y, !dbg !11
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000874 %2 = bitcast i32* %Z to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel37280782011-02-03 00:22:17 +0000875 call void @llvm.dbg.declare(metadata !{i32 * %Z}, metadata !12), !dbg !14
Devang Patel744950d2009-11-25 23:28:01 +0000876 store i32 23, i32* %Z, !dbg !15
Bill Wendling02216ff2009-12-01 00:59:58 +0000877 %tmp = load i32* %X, !dbg !16 ; &lt;i32&gt; [#uses=1]
878 %tmp1 = load i32* %Y, !dbg !16 ; &lt;i32&gt; [#uses=1]
879 %add = add nsw i32 %tmp, %tmp1, !dbg !16 ; &lt;i32&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000880 store i32 %add, i32* %Z, !dbg !16
Bill Wendling02216ff2009-12-01 00:59:58 +0000881 %tmp2 = load i32* %Y, !dbg !17 ; &lt;i32&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000882 store i32 %tmp2, i32* %X, !dbg !17
883 ret void, !dbg !18
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000884}
Devang Patel744950d2009-11-25 23:28:01 +0000885
Devang Patel37280782011-02-03 00:22:17 +0000886declare void @llvm.dbg.declare(metadata, metadata) nounwind readnone
Devang Patel744950d2009-11-25 23:28:01 +0000887
888!0 = metadata !{i32 459008, metadata !1, metadata !"X",
889 metadata !3, i32 2, metadata !6}; [ DW_TAG_auto_variable ]
890!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
891!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo", metadata !"foo",
892 metadata !"foo", metadata !3, i32 1, metadata !4,
893 i1 false, i1 true}; [DW_TAG_subprogram ]
894!3 = metadata !{i32 458769, i32 0, i32 12, metadata !"foo.c",
895 metadata !"/private/tmp", metadata !"clang 1.1", i1 true,
896 i1 false, metadata !"", i32 0}; [DW_TAG_compile_unit ]
897!4 = metadata !{i32 458773, metadata !3, metadata !"", null, i32 0, i64 0, i64 0,
898 i64 0, i32 0, null, metadata !5, i32 0}; [DW_TAG_subroutine_type ]
899!5 = metadata !{null}
900!6 = metadata !{i32 458788, metadata !3, metadata !"int", metadata !3, i32 0,
901 i64 32, i64 32, i64 0, i32 0, i32 5}; [DW_TAG_base_type ]
902!7 = metadata !{i32 2, i32 7, metadata !1, null}
903!8 = metadata !{i32 2, i32 3, metadata !1, null}
904!9 = metadata !{i32 459008, metadata !1, metadata !"Y", metadata !3, i32 3,
905 metadata !6}; [ DW_TAG_auto_variable ]
906!10 = metadata !{i32 3, i32 7, metadata !1, null}
907!11 = metadata !{i32 3, i32 3, metadata !1, null}
908!12 = metadata !{i32 459008, metadata !13, metadata !"Z", metadata !3, i32 5,
909 metadata !6}; [ DW_TAG_auto_variable ]
910!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
911!14 = metadata !{i32 5, i32 9, metadata !13, null}
912!15 = metadata !{i32 5, i32 5, metadata !13, null}
913!16 = metadata !{i32 6, i32 5, metadata !13, null}
914!17 = metadata !{i32 8, i32 3, metadata !1, null}
915!18 = metadata !{i32 9, i32 1, metadata !2, null}
Misha Brukman82873732004-05-12 19:21:57 +0000916</pre>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000917</div>
918
Bill Wendlingcf493b82009-12-01 00:53:11 +0000919<p>This example illustrates a few important details about LLVM debugging
920 information. In particular, it shows how the <tt>llvm.dbg.declare</tt>
921 intrinsic and location information, which are attached to an instruction,
922 are applied together to allow a debugger to analyze the relationship between
923 statements, variable definitions, and the code used to implement the
924 function.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000925
Bill Wendlingcf493b82009-12-01 00:53:11 +0000926<div class="doc_code">
Bill Wendling02216ff2009-12-01 00:59:58 +0000927<pre>
Devang Patel37280782011-02-03 00:22:17 +0000928call void @llvm.dbg.declare(metadata, metadata !0), !dbg !7
Bill Wendlingcf493b82009-12-01 00:53:11 +0000929</pre>
930</div>
931
932<p>The first intrinsic
Devang Patel744950d2009-11-25 23:28:01 +0000933 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000934 encodes debugging information for the variable <tt>X</tt>. The metadata
935 <tt>!dbg !7</tt> attached to the intrinsic provides scope information for the
936 variable <tt>X</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000937
Bill Wendlingcf493b82009-12-01 00:53:11 +0000938<div class="doc_code">
939<pre>
940!7 = metadata !{i32 2, i32 7, metadata !1, null}
941!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
942!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo",
943 metadata !"foo", metadata !"foo", metadata !3, i32 1,
944 metadata !4, i1 false, i1 true}; [DW_TAG_subprogram ]
945</pre>
946</div>
947
948<p>Here <tt>!7</tt> is metadata providing location information. It has four
949 fields: line number, column number, scope, and original scope. The original
950 scope represents inline location if this instruction is inlined inside a
951 caller, and is null otherwise. In this example, scope is encoded by
Devang Patel744950d2009-11-25 23:28:01 +0000952 <tt>!1</tt>. <tt>!1</tt> represents a lexical block inside the scope
953 <tt>!2</tt>, where <tt>!2</tt> is a
Bill Wendlingcf493b82009-12-01 00:53:11 +0000954 <a href="#format_subprograms">subprogram descriptor</a>. This way the
955 location information attached to the intrinsics indicates that the
956 variable <tt>X</tt> is declared at line number 2 at a function level scope in
957 function <tt>foo</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000958
Devang Patel744950d2009-11-25 23:28:01 +0000959<p>Now lets take another example.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000960
Bill Wendlingcf493b82009-12-01 00:53:11 +0000961<div class="doc_code">
Bill Wendling02216ff2009-12-01 00:59:58 +0000962<pre>
Devang Patel37280782011-02-03 00:22:17 +0000963call void @llvm.dbg.declare(metadata, metadata !12), !dbg !14
Bill Wendlingcf493b82009-12-01 00:53:11 +0000964</pre>
965</div>
966
967<p>The second intrinsic
Devang Patel744950d2009-11-25 23:28:01 +0000968 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000969 encodes debugging information for variable <tt>Z</tt>. The metadata
970 <tt>!dbg !14</tt> attached to the intrinsic provides scope information for
971 the variable <tt>Z</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000972
Bill Wendlingcf493b82009-12-01 00:53:11 +0000973<div class="doc_code">
974<pre>
975!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
976!14 = metadata !{i32 5, i32 9, metadata !13, null}
977</pre>
978</div>
Bill Wendling48839d92009-05-17 05:52:39 +0000979
John Criswellb34500f2010-03-17 15:01:50 +0000980<p>Here <tt>!14</tt> indicates that <tt>Z</tt> is declared at line number 5 and
Bill Wendlingcf493b82009-12-01 00:53:11 +0000981 column number 9 inside of lexical scope <tt>!13</tt>. The lexical scope
982 itself resides inside of lexical scope <tt>!1</tt> described above.</p>
983
984<p>The scope information attached with each instruction provides a
985 straightforward way to find instructions covered by a scope.</p>
986
Bill Wendling48839d92009-05-17 05:52:39 +0000987</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000988
989<!-- *********************************************************************** -->
990<div class="doc_section">
Chris Lattner8ff75902004-01-06 05:31:32 +0000991 <a name="ccxx_frontend">C/C++ front-end specific debug information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000992</div>
Misha Brukman94218a72004-12-09 20:27:37 +0000993<!-- *********************************************************************** -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000994
995<div class="doc_text">
996
Misha Brukman82873732004-05-12 19:21:57 +0000997<p>The C and C++ front-ends represent information about the program in a format
Bill Wendling48839d92009-05-17 05:52:39 +0000998 that is effectively identical
999 to <a href="http://www.eagercon.com/dwarf/dwarf3std.htm">DWARF 3.0</a> in
1000 terms of information content. This allows code generators to trivially
1001 support native debuggers by generating standard dwarf information, and
1002 contains enough information for non-dwarf targets to translate it as
1003 needed.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001004
Jim Laskeycec12a52006-03-14 18:08:46 +00001005<p>This section describes the forms used to represent C and C++ programs. Other
Bill Wendling48839d92009-05-17 05:52:39 +00001006 languages could pattern themselves after this (which itself is tuned to
1007 representing programs in the same way that DWARF 3 does), or they could
1008 choose to provide completely different forms if they don't fit into the DWARF
1009 model. As support for debugging information gets added to the various LLVM
1010 source-language front-ends, the information used should be documented
1011 here.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001012
Jim Laskeycec12a52006-03-14 18:08:46 +00001013<p>The following sections provide examples of various C/C++ constructs and the
Bill Wendling48839d92009-05-17 05:52:39 +00001014 debug information that would best describe those constructs.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001015
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001016</div>
1017
1018<!-- ======================================================================= -->
1019<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +00001020 <a name="ccxx_compile_units">C/C++ source file information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001021</div>
1022
1023<div class="doc_text">
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001024
Bill Wendling48839d92009-05-17 05:52:39 +00001025<p>Given the source files <tt>MySource.cpp</tt> and <tt>MyHeader.h</tt> located
1026 in the directory <tt>/Users/mine/sources</tt>, the following code:</p>
Chris Lattner8ff75902004-01-06 05:31:32 +00001027
Bill Wendling48839d92009-05-17 05:52:39 +00001028<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001029<pre>
1030#include "MyHeader.h"
Chris Lattner8ff75902004-01-06 05:31:32 +00001031
Jim Laskeycec12a52006-03-14 18:08:46 +00001032int main(int argc, char *argv[]) {
1033 return 0;
1034}
1035</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001036</div>
Chris Lattner8ff75902004-01-06 05:31:32 +00001037
Misha Brukman96e00812008-12-16 02:54:22 +00001038<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001039
Bill Wendling48839d92009-05-17 05:52:39 +00001040<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001041<pre>
1042...
1043;;
Devang Patel4b945502010-03-09 00:44:10 +00001044;; Define the compile unit for the main source file "/Users/mine/sources/MySource.cpp".
Jim Laskeycec12a52006-03-14 18:08:46 +00001045;;
Devang Patel4b945502010-03-09 00:44:10 +00001046!2 = metadata !{
1047 i32 524305, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001048 i32 0, ;; Unused
1049 i32 4, ;; Language Id
1050 metadata !"MySource.cpp",
1051 metadata !"/Users/mine/sources",
1052 metadata !"4.2.1 (Based on Apple Inc. build 5649) (LLVM build 00)",
1053 i1 true, ;; Main Compile Unit
1054 i1 false, ;; Optimized compile unit
1055 metadata !"", ;; Compiler flags
1056 i32 0} ;; Runtime version
1057
Jim Laskeycec12a52006-03-14 18:08:46 +00001058;;
Devang Patel4b945502010-03-09 00:44:10 +00001059;; Define the file for the file "/Users/mine/sources/MySource.cpp".
Jim Laskeycec12a52006-03-14 18:08:46 +00001060;;
Devang Patele4b27562009-08-28 23:24:31 +00001061!1 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001062 i32 524329, ;; Tag
1063 metadata !"MySource.cpp",
Devang Patele4b27562009-08-28 23:24:31 +00001064 metadata !"/Users/mine/sources",
Devang Patel9fea9c22010-07-13 16:53:20 +00001065 metadata !2 ;; Compile unit
Devang Patel4b945502010-03-09 00:44:10 +00001066}
1067
1068;;
1069;; Define the file for the file "/Users/mine/sources/Myheader.h"
1070;;
1071!3 = metadata !{
1072 i32 524329, ;; Tag
1073 metadata !"Myheader.h"
1074 metadata !"/Users/mine/sources",
Devang Patel9fea9c22010-07-13 16:53:20 +00001075 metadata !2 ;; Compile unit
Devang Patel4b945502010-03-09 00:44:10 +00001076}
Jim Laskeycec12a52006-03-14 18:08:46 +00001077
Jim Laskeycec12a52006-03-14 18:08:46 +00001078...
1079</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001080</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001081
Devang Pateld98ec5f2010-03-26 19:08:36 +00001082<p>llvm::Instruction provides easy access to metadata attached with an
1083instruction. One can extract line number information encoded in LLVM IR
1084using <tt>Instruction::getMetadata()</tt> and
1085<tt>DILocation::getLineNumber()</tt>.
1086<pre>
1087 if (MDNode *N = I->getMetadata("dbg")) { // Here I is an LLVM instruction
1088 DILocation Loc(N); // DILocation is in DebugInfo.h
1089 unsigned Line = Loc.getLineNumber();
1090 StringRef File = Loc.getFilename();
1091 StringRef Dir = Loc.getDirectory();
1092 }
1093</pre>
Chris Lattner8ff75902004-01-06 05:31:32 +00001094</div>
1095
1096<!-- ======================================================================= -->
1097<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +00001098 <a name="ccxx_global_variable">C/C++ global variable information</a>
Chris Lattner8ff75902004-01-06 05:31:32 +00001099</div>
1100
1101<div class="doc_text">
Jim Laskeycec12a52006-03-14 18:08:46 +00001102
Misha Brukman96e00812008-12-16 02:54:22 +00001103<p>Given an integer global variable declared as follows:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001104
Bill Wendling48839d92009-05-17 05:52:39 +00001105<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001106<pre>
1107int MyGlobal = 100;
1108</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001109</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001110
Misha Brukman96e00812008-12-16 02:54:22 +00001111<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001112
Bill Wendling48839d92009-05-17 05:52:39 +00001113<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001114<pre>
1115;;
Jim Laskeycec12a52006-03-14 18:08:46 +00001116;; Define the global itself.
1117;;
1118%MyGlobal = global int 100
1119...
1120;;
Devang Patele4b27562009-08-28 23:24:31 +00001121;; List of debug info of globals
Jim Laskeycec12a52006-03-14 18:08:46 +00001122;;
Devang Patele4b27562009-08-28 23:24:31 +00001123!llvm.dbg.gv = !{!0}
Jim Laskeycec12a52006-03-14 18:08:46 +00001124
1125;;
1126;; Define the global variable descriptor. Note the reference to the global
1127;; variable anchor and the global variable itself.
1128;;
Devang Patele4b27562009-08-28 23:24:31 +00001129!0 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001130 i32 524340, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001131 i32 0, ;; Unused
1132 metadata !1, ;; Context
1133 metadata !"MyGlobal", ;; Name
1134 metadata !"MyGlobal", ;; Display Name
1135 metadata !"MyGlobal", ;; Linkage Name
Devang Patel4b945502010-03-09 00:44:10 +00001136 metadata !3, ;; Compile Unit
Devang Patele4b27562009-08-28 23:24:31 +00001137 i32 1, ;; Line Number
Devang Patel4b945502010-03-09 00:44:10 +00001138 metadata !4, ;; Type
Devang Patele4b27562009-08-28 23:24:31 +00001139 i1 false, ;; Is a local variable
1140 i1 true, ;; Is this a definition
1141 i32* @MyGlobal ;; The global variable
1142}
1143
Jim Laskeycec12a52006-03-14 18:08:46 +00001144;;
1145;; Define the basic type of 32 bit signed integer. Note that since int is an
1146;; intrinsic type the source file is NULL and line 0.
1147;;
Devang Patel4b945502010-03-09 00:44:10 +00001148!4 = metadata !{
1149 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001150 metadata !1, ;; Context
1151 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001152 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001153 i32 0, ;; Line number
1154 i64 32, ;; Size in Bits
1155 i64 32, ;; Align in Bits
1156 i64 0, ;; Offset in Bits
1157 i32 0, ;; Flags
1158 i32 5 ;; Encoding
1159}
Jim Laskeycec12a52006-03-14 18:08:46 +00001160
Jim Laskeycec12a52006-03-14 18:08:46 +00001161</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001162</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001163
Chris Lattner8ff75902004-01-06 05:31:32 +00001164</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001165
Jim Laskeycec12a52006-03-14 18:08:46 +00001166<!-- ======================================================================= -->
1167<div class="doc_subsection">
1168 <a name="ccxx_subprogram">C/C++ function information</a>
1169</div>
1170
1171<div class="doc_text">
1172
Misha Brukman96e00812008-12-16 02:54:22 +00001173<p>Given a function declared as follows:</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>
1177int main(int argc, char *argv[]) {
1178 return 0;
1179}
1180</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001181</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001182
Misha Brukman96e00812008-12-16 02:54:22 +00001183<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001184
Bill Wendling48839d92009-05-17 05:52:39 +00001185<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001186<pre>
1187;;
Jim Laskeycec12a52006-03-14 18:08:46 +00001188;; Define the anchor for subprograms. Note that the second field of the
1189;; anchor is 46, which is the same as the tag for subprograms
1190;; (46 = DW_TAG_subprogram.)
1191;;
Devang Patel4b945502010-03-09 00:44:10 +00001192!6 = metadata !{
1193 i32 524334, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001194 i32 0, ;; Unused
1195 metadata !1, ;; Context
1196 metadata !"main", ;; Name
1197 metadata !"main", ;; Display name
1198 metadata !"main", ;; Linkage name
Devang Patel4b945502010-03-09 00:44:10 +00001199 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001200 i32 1, ;; Line number
Devang Patel4b945502010-03-09 00:44:10 +00001201 metadata !4, ;; Type
Devang Patele4b27562009-08-28 23:24:31 +00001202 i1 false, ;; Is local
1203 i1 true ;; Is definition
1204}
Jim Laskeycec12a52006-03-14 18:08:46 +00001205;;
1206;; Define the subprogram itself.
1207;;
Devang Patele4b27562009-08-28 23:24:31 +00001208define i32 @main(i32 %argc, i8** %argv) {
Jim Laskeycec12a52006-03-14 18:08:46 +00001209...
1210}
1211</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001212</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001213
1214</div>
1215
1216<!-- ======================================================================= -->
1217<div class="doc_subsection">
1218 <a name="ccxx_basic_types">C/C++ basic types</a>
1219</div>
1220
1221<div class="doc_text">
1222
Misha Brukman96e00812008-12-16 02:54:22 +00001223<p>The following are the basic type descriptors for C/C++ core types:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001224
1225</div>
1226
1227<!-- ======================================================================= -->
1228<div class="doc_subsubsection">
1229 <a name="ccxx_basic_type_bool">bool</a>
1230</div>
1231
1232<div class="doc_text">
1233
Bill Wendling48839d92009-05-17 05:52:39 +00001234<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001235<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001236!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001237 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001238 metadata !1, ;; Context
1239 metadata !"bool", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001240 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001241 i32 0, ;; Line number
1242 i64 8, ;; Size in Bits
1243 i64 8, ;; Align in Bits
1244 i64 0, ;; Offset in Bits
1245 i32 0, ;; Flags
1246 i32 2 ;; Encoding
1247}
Jim Laskeycec12a52006-03-14 18:08:46 +00001248</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001249</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001250
1251</div>
1252
1253<!-- ======================================================================= -->
1254<div class="doc_subsubsection">
1255 <a name="ccxx_basic_char">char</a>
1256</div>
1257
1258<div class="doc_text">
1259
Bill Wendling48839d92009-05-17 05:52:39 +00001260<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001261<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001262!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001263 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001264 metadata !1, ;; Context
1265 metadata !"char", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001266 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001267 i32 0, ;; Line number
1268 i64 8, ;; Size in Bits
1269 i64 8, ;; Align in Bits
1270 i64 0, ;; Offset in Bits
1271 i32 0, ;; Flags
1272 i32 6 ;; Encoding
1273}
Jim Laskeycec12a52006-03-14 18:08:46 +00001274</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001275</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001276
1277</div>
1278
1279<!-- ======================================================================= -->
1280<div class="doc_subsubsection">
1281 <a name="ccxx_basic_unsigned_char">unsigned char</a>
1282</div>
1283
1284<div class="doc_text">
1285
Bill Wendling48839d92009-05-17 05:52:39 +00001286<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001287<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001288!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001289 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001290 metadata !1, ;; Context
1291 metadata !"unsigned char",
Devang Patel4b945502010-03-09 00:44:10 +00001292 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001293 i32 0, ;; Line number
1294 i64 8, ;; Size in Bits
1295 i64 8, ;; Align in Bits
1296 i64 0, ;; Offset in Bits
1297 i32 0, ;; Flags
1298 i32 8 ;; Encoding
1299}
Jim Laskeycec12a52006-03-14 18:08:46 +00001300</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001301</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001302
1303</div>
1304
1305<!-- ======================================================================= -->
1306<div class="doc_subsubsection">
1307 <a name="ccxx_basic_short">short</a>
1308</div>
1309
1310<div class="doc_text">
1311
Bill Wendling48839d92009-05-17 05:52:39 +00001312<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001313<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001314!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001315 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001316 metadata !1, ;; Context
1317 metadata !"short int",
Devang Patel4b945502010-03-09 00:44:10 +00001318 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001319 i32 0, ;; Line number
1320 i64 16, ;; Size in Bits
1321 i64 16, ;; Align in Bits
1322 i64 0, ;; Offset in Bits
1323 i32 0, ;; Flags
1324 i32 5 ;; Encoding
1325}
Jim Laskeycec12a52006-03-14 18:08:46 +00001326</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001327</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001328
1329</div>
1330
1331<!-- ======================================================================= -->
1332<div class="doc_subsubsection">
1333 <a name="ccxx_basic_unsigned_short">unsigned short</a>
1334</div>
1335
1336<div class="doc_text">
1337
Bill Wendling48839d92009-05-17 05:52:39 +00001338<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001339<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001340!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001341 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001342 metadata !1, ;; Context
1343 metadata !"short unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001344 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001345 i32 0, ;; Line number
1346 i64 16, ;; Size in Bits
1347 i64 16, ;; Align in Bits
1348 i64 0, ;; Offset in Bits
1349 i32 0, ;; Flags
1350 i32 7 ;; Encoding
1351}
Jim Laskeycec12a52006-03-14 18:08:46 +00001352</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001353</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001354
1355</div>
1356
1357<!-- ======================================================================= -->
1358<div class="doc_subsubsection">
1359 <a name="ccxx_basic_int">int</a>
1360</div>
1361
1362<div class="doc_text">
1363
Bill Wendling48839d92009-05-17 05:52:39 +00001364<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001365<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001366!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001367 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001368 metadata !1, ;; Context
1369 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001370 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001371 i32 0, ;; Line number
1372 i64 32, ;; Size in Bits
1373 i64 32, ;; Align in Bits
1374 i64 0, ;; Offset in Bits
1375 i32 0, ;; Flags
1376 i32 5 ;; Encoding
1377}
Bill Wendling48839d92009-05-17 05:52:39 +00001378</pre></div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001379
1380</div>
1381
1382<!-- ======================================================================= -->
1383<div class="doc_subsubsection">
1384 <a name="ccxx_basic_unsigned_int">unsigned int</a>
1385</div>
1386
1387<div class="doc_text">
1388
Bill Wendling48839d92009-05-17 05:52:39 +00001389<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001390<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001391!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001392 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001393 metadata !1, ;; Context
1394 metadata !"unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001395 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001396 i32 0, ;; Line number
1397 i64 32, ;; Size in Bits
1398 i64 32, ;; Align in Bits
1399 i64 0, ;; Offset in Bits
1400 i32 0, ;; Flags
1401 i32 7 ;; Encoding
1402}
Jim Laskeycec12a52006-03-14 18:08:46 +00001403</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001404</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001405
1406</div>
1407
1408<!-- ======================================================================= -->
1409<div class="doc_subsubsection">
1410 <a name="ccxx_basic_long_long">long long</a>
1411</div>
1412
1413<div class="doc_text">
1414
Bill Wendling48839d92009-05-17 05:52:39 +00001415<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001416<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001417!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001418 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001419 metadata !1, ;; Context
1420 metadata !"long long int",
Devang Patel4b945502010-03-09 00:44:10 +00001421 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001422 i32 0, ;; Line number
1423 i64 64, ;; Size in Bits
1424 i64 64, ;; Align in Bits
1425 i64 0, ;; Offset in Bits
1426 i32 0, ;; Flags
1427 i32 5 ;; Encoding
1428}
Jim Laskeycec12a52006-03-14 18:08:46 +00001429</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001430</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001431
1432</div>
1433
1434<!-- ======================================================================= -->
1435<div class="doc_subsubsection">
1436 <a name="ccxx_basic_unsigned_long_long">unsigned long long</a>
1437</div>
1438
1439<div class="doc_text">
1440
Bill Wendling48839d92009-05-17 05:52:39 +00001441<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001442<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001443!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001444 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001445 metadata !1, ;; Context
1446 metadata !"long long unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001447 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001448 i32 0, ;; Line number
1449 i64 64, ;; Size in Bits
1450 i64 64, ;; Align in Bits
1451 i64 0, ;; Offset in Bits
1452 i32 0, ;; Flags
1453 i32 7 ;; Encoding
1454}
Jim Laskeycec12a52006-03-14 18:08:46 +00001455</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001456</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001457
1458</div>
1459
1460<!-- ======================================================================= -->
1461<div class="doc_subsubsection">
1462 <a name="ccxx_basic_float">float</a>
1463</div>
1464
1465<div class="doc_text">
1466
Bill Wendling48839d92009-05-17 05:52:39 +00001467<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001468<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001469!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001470 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001471 metadata !1, ;; Context
1472 metadata !"float",
Devang Patel4b945502010-03-09 00:44:10 +00001473 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001474 i32 0, ;; Line number
1475 i64 32, ;; Size in Bits
1476 i64 32, ;; Align in Bits
1477 i64 0, ;; Offset in Bits
1478 i32 0, ;; Flags
1479 i32 4 ;; Encoding
1480}
Jim Laskeycec12a52006-03-14 18:08:46 +00001481</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001482</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001483
1484</div>
1485
1486<!-- ======================================================================= -->
1487<div class="doc_subsubsection">
1488 <a name="ccxx_basic_double">double</a>
1489</div>
1490
1491<div class="doc_text">
1492
Bill Wendling48839d92009-05-17 05:52:39 +00001493<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001494<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001495!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001496 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001497 metadata !1, ;; Context
1498 metadata !"double",;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001499 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001500 i32 0, ;; Line number
1501 i64 64, ;; Size in Bits
1502 i64 64, ;; Align in Bits
1503 i64 0, ;; Offset in Bits
1504 i32 0, ;; Flags
1505 i32 4 ;; Encoding
1506}
Jim Laskeycec12a52006-03-14 18:08:46 +00001507</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001508</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001509
1510</div>
1511
1512<!-- ======================================================================= -->
1513<div class="doc_subsection">
1514 <a name="ccxx_derived_types">C/C++ derived types</a>
1515</div>
1516
1517<div class="doc_text">
1518
Misha Brukman96e00812008-12-16 02:54:22 +00001519<p>Given the following as an example of C/C++ derived type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001520
Bill Wendling48839d92009-05-17 05:52:39 +00001521<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001522<pre>
1523typedef const int *IntPtr;
1524</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001525</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001526
Misha Brukman96e00812008-12-16 02:54:22 +00001527<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001528
Bill Wendling48839d92009-05-17 05:52:39 +00001529<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001530<pre>
1531;;
1532;; Define the typedef "IntPtr".
1533;;
Devang Patele4b27562009-08-28 23:24:31 +00001534!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001535 i32 524310, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001536 metadata !1, ;; Context
1537 metadata !"IntPtr", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001538 metadata !3, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001539 i32 0, ;; Line number
1540 i64 0, ;; Size in bits
1541 i64 0, ;; Align in bits
1542 i64 0, ;; Offset in bits
1543 i32 0, ;; Flags
1544 metadata !4 ;; Derived From type
1545}
Jim Laskeycec12a52006-03-14 18:08:46 +00001546
1547;;
1548;; Define the pointer type.
1549;;
Devang Patele4b27562009-08-28 23:24:31 +00001550!4 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001551 i32 524303, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001552 metadata !1, ;; Context
1553 metadata !"", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001554 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001555 i32 0, ;; Line number
1556 i64 64, ;; Size in bits
1557 i64 64, ;; Align in bits
1558 i64 0, ;; Offset in bits
1559 i32 0, ;; Flags
1560 metadata !5 ;; Derived From type
1561}
Jim Laskeycec12a52006-03-14 18:08:46 +00001562;;
1563;; Define the const type.
1564;;
Devang Patele4b27562009-08-28 23:24:31 +00001565!5 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001566 i32 524326, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001567 metadata !1, ;; Context
1568 metadata !"", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001569 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001570 i32 0, ;; Line number
1571 i64 32, ;; Size in bits
1572 i64 32, ;; Align in bits
1573 i64 0, ;; Offset in bits
1574 i32 0, ;; Flags
1575 metadata !6 ;; Derived From type
1576}
Jim Laskeycec12a52006-03-14 18:08:46 +00001577;;
1578;; Define the int type.
1579;;
Devang Patele4b27562009-08-28 23:24:31 +00001580!6 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001581 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001582 metadata !1, ;; Context
1583 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001584 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001585 i32 0, ;; Line number
1586 i64 32, ;; Size in bits
1587 i64 32, ;; Align in bits
1588 i64 0, ;; Offset in bits
1589 i32 0, ;; Flags
1590 5 ;; Encoding
1591}
Jim Laskeycec12a52006-03-14 18:08:46 +00001592</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001593</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001594
1595</div>
1596
1597<!-- ======================================================================= -->
1598<div class="doc_subsection">
1599 <a name="ccxx_composite_types">C/C++ struct/union types</a>
1600</div>
1601
1602<div class="doc_text">
1603
Misha Brukman96e00812008-12-16 02:54:22 +00001604<p>Given the following as an example of C/C++ struct type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001605
Bill Wendling48839d92009-05-17 05:52:39 +00001606<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001607<pre>
1608struct Color {
1609 unsigned Red;
1610 unsigned Green;
1611 unsigned Blue;
1612};
1613</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001614</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001615
Misha Brukman96e00812008-12-16 02:54:22 +00001616<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001617
Bill Wendling48839d92009-05-17 05:52:39 +00001618<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001619<pre>
1620;;
1621;; Define basic type for unsigned int.
1622;;
Devang Patele4b27562009-08-28 23:24:31 +00001623!5 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001624 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001625 metadata !1, ;; Context
1626 metadata !"unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001627 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001628 i32 0, ;; Line number
1629 i64 32, ;; Size in Bits
1630 i64 32, ;; Align in Bits
1631 i64 0, ;; Offset in Bits
1632 i32 0, ;; Flags
1633 i32 7 ;; Encoding
1634}
Jim Laskeycec12a52006-03-14 18:08:46 +00001635;;
1636;; Define composite type for struct Color.
1637;;
Devang Patele4b27562009-08-28 23:24:31 +00001638!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001639 i32 524307, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001640 metadata !1, ;; Context
1641 metadata !"Color", ;; Name
1642 metadata !1, ;; Compile unit
1643 i32 1, ;; Line number
1644 i64 96, ;; Size in bits
1645 i64 32, ;; Align in bits
1646 i64 0, ;; Offset in bits
1647 i32 0, ;; Flags
1648 null, ;; Derived From
1649 metadata !3, ;; Elements
1650 i32 0 ;; Runtime Language
1651}
Jim Laskeycec12a52006-03-14 18:08:46 +00001652
1653;;
1654;; Define the Red field.
1655;;
Devang Patele4b27562009-08-28 23:24:31 +00001656!4 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001657 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001658 metadata !1, ;; Context
1659 metadata !"Red", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001660 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001661 i32 2, ;; Line number
1662 i64 32, ;; Size in bits
1663 i64 32, ;; Align in bits
1664 i64 0, ;; Offset in bits
1665 i32 0, ;; Flags
1666 metadata !5 ;; Derived From type
1667}
Jim Laskeycec12a52006-03-14 18:08:46 +00001668
1669;;
1670;; Define the Green field.
1671;;
Devang Patele4b27562009-08-28 23:24:31 +00001672!6 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001673 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001674 metadata !1, ;; Context
1675 metadata !"Green", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001676 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001677 i32 3, ;; Line number
1678 i64 32, ;; Size in bits
1679 i64 32, ;; Align in bits
1680 i64 32, ;; Offset in bits
1681 i32 0, ;; Flags
1682 metadata !5 ;; Derived From type
1683}
Jim Laskeycec12a52006-03-14 18:08:46 +00001684
1685;;
1686;; Define the Blue field.
1687;;
Devang Patele4b27562009-08-28 23:24:31 +00001688!7 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001689 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001690 metadata !1, ;; Context
1691 metadata !"Blue", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001692 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001693 i32 4, ;; Line number
1694 i64 32, ;; Size in bits
1695 i64 32, ;; Align in bits
1696 i64 64, ;; Offset in bits
1697 i32 0, ;; Flags
1698 metadata !5 ;; Derived From type
1699}
Jim Laskeycec12a52006-03-14 18:08:46 +00001700
1701;;
1702;; Define the array of fields used by the composite type Color.
1703;;
Devang Patele4b27562009-08-28 23:24:31 +00001704!3 = metadata !{metadata !4, metadata !6, metadata !7}
Jim Laskeycec12a52006-03-14 18:08:46 +00001705</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001706</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001707
1708</div>
1709
1710<!-- ======================================================================= -->
1711<div class="doc_subsection">
1712 <a name="ccxx_enumeration_types">C/C++ enumeration types</a>
1713</div>
1714
1715<div class="doc_text">
1716
Misha Brukman96e00812008-12-16 02:54:22 +00001717<p>Given the following as an example of C/C++ enumeration type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001718
Bill Wendling48839d92009-05-17 05:52:39 +00001719<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001720<pre>
1721enum Trees {
1722 Spruce = 100,
1723 Oak = 200,
1724 Maple = 300
1725};
1726</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001727</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001728
Misha Brukman96e00812008-12-16 02:54:22 +00001729<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001730
Bill Wendling48839d92009-05-17 05:52:39 +00001731<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001732<pre>
1733;;
1734;; Define composite type for enum Trees
1735;;
Devang Patele4b27562009-08-28 23:24:31 +00001736!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001737 i32 524292, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001738 metadata !1, ;; Context
1739 metadata !"Trees", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001740 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001741 i32 1, ;; Line number
1742 i64 32, ;; Size in bits
1743 i64 32, ;; Align in bits
1744 i64 0, ;; Offset in bits
1745 i32 0, ;; Flags
1746 null, ;; Derived From type
1747 metadata !3, ;; Elements
1748 i32 0 ;; Runtime language
1749}
Devang Patel2a610c72009-08-25 05:24:07 +00001750
Devang Patel82459882009-08-26 05:01:18 +00001751;;
1752;; Define the array of enumerators used by composite type Trees.
1753;;
Devang Patele4b27562009-08-28 23:24:31 +00001754!3 = metadata !{metadata !4, metadata !5, metadata !6}
1755
1756;;
1757;; Define Spruce enumerator.
1758;;
Devang Patel4b945502010-03-09 00:44:10 +00001759!4 = metadata !{i32 524328, metadata !"Spruce", i64 100}
Devang Patele4b27562009-08-28 23:24:31 +00001760
1761;;
1762;; Define Oak enumerator.
1763;;
Devang Patel4b945502010-03-09 00:44:10 +00001764!5 = metadata !{i32 524328, metadata !"Oak", i64 200}
Devang Patele4b27562009-08-28 23:24:31 +00001765
1766;;
1767;; Define Maple enumerator.
1768;;
Devang Patel4b945502010-03-09 00:44:10 +00001769!6 = metadata !{i32 524328, metadata !"Maple", i64 300}
Devang Patele4b27562009-08-28 23:24:31 +00001770
Jim Laskeycec12a52006-03-14 18:08:46 +00001771</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001772</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001773
1774</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001775
1776<!-- *********************************************************************** -->
Misha Brukman82873732004-05-12 19:21:57 +00001777
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001778<hr>
Misha Brukman82873732004-05-12 19:21:57 +00001779<address>
1780 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001781 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman82873732004-05-12 19:21:57 +00001782 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001783 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman82873732004-05-12 19:21:57 +00001784
1785 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001786 <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001787 Last modified: $Date$
Misha Brukman82873732004-05-12 19:21:57 +00001788</address>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001789
1790</body>
1791</html>