blob: 789b8ca64905520624f0ef3f42b27897d0a0d8a8 [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
410provide details such as name, type and where the variable is defined.</p>
411
412</div>
413
414<!-- ======================================================================= -->
415<div class="doc_subsubsection">
416 <a name="format_subprograms">Subprogram descriptors</a>
417</div>
418
419<div class="doc_text">
420
Bill Wendling48839d92009-05-17 05:52:39 +0000421<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000422<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000423!2 = metadata !{
424 i32, ;; Tag = 46 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
425 ;; (DW_TAG_subprogram)
426 i32, ;; Unused field.
427 metadata, ;; Reference to context descriptor
428 metadata, ;; Name
429 metadata, ;; Display name (fully qualified C++ name)
430 metadata, ;; MIPS linkage name (for C++)
Devang Patel4b945502010-03-09 00:44:10 +0000431 metadata, ;; Reference to file where defined
Devang Patele4b27562009-08-28 23:24:31 +0000432 i32, ;; Line number where defined
433 metadata, ;; Reference to type descriptor
434 i1, ;; True if the global is local to compile unit (static)
435 i1 ;; True if the global is defined in the compile unit (not extern)
Devang Patel80ecc152010-06-04 22:49:55 +0000436 i32 ;; Virtuality, e.g. dwarf::DW_VIRTUALITY__virtual
437 i32 ;; Index into a virtual function
438 metadata, ;; indicates which base type contains the vtable pointer for the
439 ;; derived class
440 i1 ;; isArtificial
441 i1 ;; isOptimized
442 Function *;; Pointer to LLVM function
Bill Wendling48839d92009-05-17 05:52:39 +0000443}
Jim Laskeycec12a52006-03-14 18:08:46 +0000444</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000445</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000446
447<p>These descriptors provide debug information about functions, methods and
Bill Wendling48839d92009-05-17 05:52:39 +0000448 subprograms. They provide details such as name, return types and the source
449 location where the subprogram is defined.</p>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000450
451</div>
Bill Wendling48839d92009-05-17 05:52:39 +0000452
Jim Laskey3d11bee2006-03-15 19:10:52 +0000453<!-- ======================================================================= -->
454<div class="doc_subsubsection">
455 <a name="format_blocks">Block descriptors</a>
456</div>
457
458<div class="doc_text">
459
Bill Wendling48839d92009-05-17 05:52:39 +0000460<div class="doc_code">
Jim Laskey3d11bee2006-03-15 19:10:52 +0000461<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000462!3 = metadata !{
Devang Patelc79dda22010-10-04 16:51:59 +0000463 i32, ;; Tag = 11 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_lexical_block)
Devang Patel7f271fc2010-10-01 22:45:00 +0000464 metadata,;; Reference to context descriptor
465 i32, ;; Line number
Devang Patel90d81f12011-03-08 16:25:29 +0000466 i32, ;; Column number
467 metadata,;; Reference to source file
468 i32 ;; Unique ID to identify blocks from a template function
Bill Wendling48839d92009-05-17 05:52:39 +0000469}
Jim Laskey3d11bee2006-03-15 19:10:52 +0000470</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000471</div>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000472
473<p>These descriptors provide debug information about nested blocks within a
Devang Patel7f271fc2010-10-01 22:45:00 +0000474 subprogram. The line number and column numbers are used to dinstinguish
475 two lexical blocks at same depth. </p>
Jim Laskey3d11bee2006-03-15 19:10:52 +0000476
Jim Laskeycec12a52006-03-14 18:08:46 +0000477</div>
478
479<!-- ======================================================================= -->
480<div class="doc_subsubsection">
481 <a name="format_basic_type">Basic type descriptors</a>
482</div>
483
484<div class="doc_text">
485
Bill Wendling48839d92009-05-17 05:52:39 +0000486<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000487<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000488!4 = metadata !{
489 i32, ;; Tag = 36 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
490 ;; (DW_TAG_base_type)
491 metadata, ;; Reference to context (typically a compile unit)
492 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000493 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000494 i32, ;; Line number where defined (may be 0)
495 i64, ;; Size in bits
496 i64, ;; Alignment in bits
497 i64, ;; Offset in bits
498 i32, ;; Flags
499 i32 ;; DWARF type encoding
Bill Wendling48839d92009-05-17 05:52:39 +0000500}
Jim Laskeycec12a52006-03-14 18:08:46 +0000501</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000502</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000503
504<p>These descriptors define primitive types used in the code. Example int, bool
Bill Wendling48839d92009-05-17 05:52:39 +0000505 and float. The context provides the scope of the type, which is usually the
506 top level. Since basic types are not usually user defined the compile unit
507 and line number can be left as NULL and 0. The size, alignment and offset
508 are expressed in bits and can be 64 bit values. The alignment is used to
509 round the offset when embedded in a
510 <a href="#format_composite_type">composite type</a> (example to keep float
511 doubles on 64 bit boundaries.) The offset is the bit offset if embedded in
512 a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000513
514<p>The type encoding provides the details of the type. The values are typically
Bill Wendling48839d92009-05-17 05:52:39 +0000515 one of the following:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000516
Bill Wendling48839d92009-05-17 05:52:39 +0000517<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000518<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000519DW_ATE_address = 1
520DW_ATE_boolean = 2
521DW_ATE_float = 4
522DW_ATE_signed = 5
523DW_ATE_signed_char = 6
524DW_ATE_unsigned = 7
525DW_ATE_unsigned_char = 8
Jim Laskeycec12a52006-03-14 18:08:46 +0000526</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000527</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000528
529</div>
530
531<!-- ======================================================================= -->
532<div class="doc_subsubsection">
533 <a name="format_derived_type">Derived type descriptors</a>
534</div>
535
536<div class="doc_text">
537
Bill Wendling48839d92009-05-17 05:52:39 +0000538<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000539<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000540!5 = metadata !{
541 i32, ;; Tag (see below)
542 metadata, ;; Reference to context
543 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000544 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000545 i32, ;; Line number where defined (may be 0)
Devang Patel0ffd10b2010-10-01 19:19:30 +0000546 i64, ;; Size in bits
547 i64, ;; Alignment in bits
548 i64, ;; Offset in bits
Devang Patele4b27562009-08-28 23:24:31 +0000549 metadata ;; Reference to type derived from
Bill Wendling48839d92009-05-17 05:52:39 +0000550}
Jim Laskeycec12a52006-03-14 18:08:46 +0000551</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000552</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000553
554<p>These descriptors are used to define types derived from other types. The
555value of the tag varies depending on the meaning. The following are possible
Misha Brukman96e00812008-12-16 02:54:22 +0000556tag values:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000557
Bill Wendling48839d92009-05-17 05:52:39 +0000558<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000559<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000560DW_TAG_formal_parameter = 5
561DW_TAG_member = 13
562DW_TAG_pointer_type = 15
563DW_TAG_reference_type = 16
564DW_TAG_typedef = 22
565DW_TAG_const_type = 38
566DW_TAG_volatile_type = 53
567DW_TAG_restrict_type = 55
Jim Laskeycec12a52006-03-14 18:08:46 +0000568</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000569</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000570
Bill Wendling48839d92009-05-17 05:52:39 +0000571<p><tt>DW_TAG_member</tt> is used to define a member of
572 a <a href="#format_composite_type">composite type</a>
573 or <a href="#format_subprograms">subprogram</a>. The type of the member is
574 the <a href="#format_derived_type">derived
575 type</a>. <tt>DW_TAG_formal_parameter</tt> is used to define a member which
576 is a formal argument of a subprogram.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000577
Bill Wendling48839d92009-05-17 05:52:39 +0000578<p><tt>DW_TAG_typedef</tt> is used to provide a name for the derived type.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000579
Bill Wendling48839d92009-05-17 05:52:39 +0000580<p><tt>DW_TAG_pointer_type</tt>,<tt>DW_TAG_reference_type</tt>,
581 <tt>DW_TAG_const_type</tt>, <tt>DW_TAG_volatile_type</tt>
582 and <tt>DW_TAG_restrict_type</tt> are used to qualify
583 the <a href="#format_derived_type">derived type</a>. </p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000584
585<p><a href="#format_derived_type">Derived type</a> location can be determined
Bill Wendling48839d92009-05-17 05:52:39 +0000586 from the compile unit and line number. The size, alignment and offset are
587 expressed in bits and can be 64 bit values. The alignment is used to round
588 the offset when embedded in a <a href="#format_composite_type">composite
589 type</a> (example to keep float doubles on 64 bit boundaries.) The offset is
590 the bit offset if embedded in a <a href="#format_composite_type">composite
591 type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000592
Devang Patel37280782011-02-03 00:22:17 +0000593<p>Note that the <tt>void *</tt> type is expressed as a type derived from NULL.
594</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000595
596</div>
597
598<!-- ======================================================================= -->
599<div class="doc_subsubsection">
600 <a name="format_composite_type">Composite type descriptors</a>
601</div>
602
603<div class="doc_text">
604
Bill Wendling48839d92009-05-17 05:52:39 +0000605<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000606<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000607!6 = metadata !{
608 i32, ;; Tag (see below)
609 metadata, ;; Reference to context
610 metadata, ;; Name (may be "" for anonymous types)
Devang Patel4b945502010-03-09 00:44:10 +0000611 metadata, ;; Reference to file where defined (may be NULL)
Devang Patele4b27562009-08-28 23:24:31 +0000612 i32, ;; Line number where defined (may be 0)
613 i64, ;; Size in bits
614 i64, ;; Alignment in bits
615 i64, ;; Offset in bits
616 i32, ;; Flags
617 metadata, ;; Reference to type derived from
618 metadata, ;; Reference to array of member descriptors
619 i32 ;; Runtime languages
Bill Wendling48839d92009-05-17 05:52:39 +0000620}
Jim Laskeycec12a52006-03-14 18:08:46 +0000621</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000622</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000623
624<p>These descriptors are used to define types that are composed of 0 or more
625elements. The value of the tag varies depending on the meaning. The following
Misha Brukman96e00812008-12-16 02:54:22 +0000626are possible tag values:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000627
Bill Wendling48839d92009-05-17 05:52:39 +0000628<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000629<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000630DW_TAG_array_type = 1
631DW_TAG_enumeration_type = 4
632DW_TAG_structure_type = 19
633DW_TAG_union_type = 23
634DW_TAG_vector_type = 259
Bruno Cardoso Lopesd80ddc02009-05-29 17:08:57 +0000635DW_TAG_subroutine_type = 21
636DW_TAG_inheritance = 28
Jim Laskeycec12a52006-03-14 18:08:46 +0000637</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000638</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000639
Jim Laskeyf8a01a92006-06-15 20:51:43 +0000640<p>The vector flag indicates that an array type is a native packed vector.</p>
641
Jim Laskey7089f452006-06-16 13:14:03 +0000642<p>The members of array types (tag = <tt>DW_TAG_array_type</tt>) or vector types
Bill Wendling48839d92009-05-17 05:52:39 +0000643 (tag = <tt>DW_TAG_vector_type</tt>) are <a href="#format_subrange">subrange
644 descriptors</a>, each representing the range of subscripts at that level of
645 indexing.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000646
647<p>The members of enumeration types (tag = <tt>DW_TAG_enumeration_type</tt>) are
Bill Wendling48839d92009-05-17 05:52:39 +0000648 <a href="#format_enumeration">enumerator descriptors</a>, each representing
649 the definition of enumeration value for the set.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000650
651<p>The members of structure (tag = <tt>DW_TAG_structure_type</tt>) or union (tag
Bill Wendling48839d92009-05-17 05:52:39 +0000652 = <tt>DW_TAG_union_type</tt>) types are any one of
653 the <a href="#format_basic_type">basic</a>,
654 <a href="#format_derived_type">derived</a>
655 or <a href="#format_composite_type">composite</a> type descriptors, each
656 representing a field member of the structure or union.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000657
Jim Laskey4a9df242006-08-21 21:21:06 +0000658<p>For C++ classes (tag = <tt>DW_TAG_structure_type</tt>), member descriptors
Bill Wendling48839d92009-05-17 05:52:39 +0000659 provide information about base classes, static members and member
660 functions. If a member is a <a href="#format_derived_type">derived type
661 descriptor</a> and has a tag of <tt>DW_TAG_inheritance</tt>, then the type
662 represents a base class. If the member of is
663 a <a href="#format_global_variables">global variable descriptor</a> then it
664 represents a static member. And, if the member is
665 a <a href="#format_subprograms">subprogram descriptor</a> then it represents
666 a member function. For static members and member
667 functions, <tt>getName()</tt> returns the members link or the C++ mangled
668 name. <tt>getDisplayName()</tt> the simplied version of the name.</p>
Jim Laskey4a9df242006-08-21 21:21:06 +0000669
Bill Wendling48839d92009-05-17 05:52:39 +0000670<p>The first member of subroutine (tag = <tt>DW_TAG_subroutine_type</tt>) type
671 elements is the return type for the subroutine. The remaining elements are
672 the formal arguments to the subroutine.</p>
Jim Laskey094ee722006-06-20 21:13:20 +0000673
Jim Laskeycec12a52006-03-14 18:08:46 +0000674<p><a href="#format_composite_type">Composite type</a> location can be
Bill Wendling48839d92009-05-17 05:52:39 +0000675 determined from the compile unit and line number. The size, alignment and
676 offset are expressed in bits and can be 64 bit values. The alignment is used
677 to round the offset when embedded in
678 a <a href="#format_composite_type">composite type</a> (as an example, to keep
679 float doubles on 64 bit boundaries.) The offset is the bit offset if embedded
680 in a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000681
682</div>
683
684<!-- ======================================================================= -->
685<div class="doc_subsubsection">
686 <a name="format_subrange">Subrange descriptors</a>
687</div>
688
689<div class="doc_text">
690
Bill Wendling48839d92009-05-17 05:52:39 +0000691<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000692<pre>
Devang Patel37280782011-02-03 00:22:17 +0000693!42 = metadata !{
Bill Wendling48839d92009-05-17 05:52:39 +0000694 i32, ;; Tag = 33 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_subrange_type)
695 i64, ;; Low value
696 i64 ;; High value
697}
Jim Laskeycec12a52006-03-14 18:08:46 +0000698</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000699</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000700
701<p>These descriptors are used to define ranges of array subscripts for an array
Bill Wendling48839d92009-05-17 05:52:39 +0000702 <a href="#format_composite_type">composite type</a>. The low value defines
703 the lower bounds typically zero for C/C++. The high value is the upper
704 bounds. Values are 64 bit. High - low + 1 is the size of the array. If low
705 == high the array will be unbounded.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000706
707</div>
708
709<!-- ======================================================================= -->
710<div class="doc_subsubsection">
711 <a name="format_enumeration">Enumerator descriptors</a>
712</div>
713
714<div class="doc_text">
715
Bill Wendling48839d92009-05-17 05:52:39 +0000716<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +0000717<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000718!6 = metadata !{
719 i32, ;; Tag = 40 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
720 ;; (DW_TAG_enumerator)
721 metadata, ;; Name
722 i64 ;; Value
Bill Wendling48839d92009-05-17 05:52:39 +0000723}
Jim Laskeycec12a52006-03-14 18:08:46 +0000724</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000725</div>
Jim Laskeycec12a52006-03-14 18:08:46 +0000726
Bill Wendling48839d92009-05-17 05:52:39 +0000727<p>These descriptors are used to define members of an
728 enumeration <a href="#format_composite_type">composite type</a>, it
729 associates the name to the value.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000730
731</div>
732
733<!-- ======================================================================= -->
Jim Laskey383e0092006-03-23 17:54:33 +0000734<div class="doc_subsubsection">
735 <a name="format_variables">Local variables</a>
736</div>
737
738<div class="doc_text">
Bill Wendling48839d92009-05-17 05:52:39 +0000739
740<div class="doc_code">
Jim Laskey383e0092006-03-23 17:54:33 +0000741<pre>
Devang Patele4b27562009-08-28 23:24:31 +0000742!7 = metadata !{
743 i32, ;; Tag (see below)
744 metadata, ;; Context
745 metadata, ;; Name
Devang Patel4b945502010-03-09 00:44:10 +0000746 metadata, ;; Reference to file where defined
Devang Patele4b27562009-08-28 23:24:31 +0000747 i32, ;; Line number where defined
748 metadata ;; Type descriptor
Bill Wendling48839d92009-05-17 05:52:39 +0000749}
Jim Laskey383e0092006-03-23 17:54:33 +0000750</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000751</div>
Jim Laskey383e0092006-03-23 17:54:33 +0000752
753<p>These descriptors are used to define variables local to a sub program. The
Bill Wendling48839d92009-05-17 05:52:39 +0000754 value of the tag depends on the usage of the variable:</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000755
Bill Wendling48839d92009-05-17 05:52:39 +0000756<div class="doc_code">
Jim Laskey383e0092006-03-23 17:54:33 +0000757<pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000758DW_TAG_auto_variable = 256
759DW_TAG_arg_variable = 257
760DW_TAG_return_variable = 258
Jim Laskey383e0092006-03-23 17:54:33 +0000761</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000762</div>
Jim Laskey383e0092006-03-23 17:54:33 +0000763
764<p>An auto variable is any variable declared in the body of the function. An
Bill Wendling48839d92009-05-17 05:52:39 +0000765 argument variable is any variable that appears as a formal argument to the
766 function. A return variable is used to track the result of a function and
767 has no source correspondent.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000768
Jim Laskey2d395d92006-03-24 09:20:27 +0000769<p>The context is either the subprogram or block where the variable is defined.
Bill Wendling48839d92009-05-17 05:52:39 +0000770 Name the source variable name. Compile unit and line indicate where the
771 variable was defined. Type descriptor defines the declared type of the
772 variable.</p>
Jim Laskey383e0092006-03-23 17:54:33 +0000773
774</div>
775
776<!-- ======================================================================= -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000777<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000778 <a name="format_common_intrinsics">Debugger intrinsic functions</a>
779</div>
780
781<div class="doc_text">
782
783<p>LLVM uses several intrinsic functions (name prefixed with "llvm.dbg") to
Bill Wendling48839d92009-05-17 05:52:39 +0000784 provide debug information at various points in generated code.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000785
786</div>
787
788<!-- ======================================================================= -->
789<div class="doc_subsubsection">
Jim Laskeycec12a52006-03-14 18:08:46 +0000790 <a name="format_common_declare">llvm.dbg.declare</a>
791</div>
792
793<div class="doc_text">
794<pre>
Devang Patel4c7c0c62010-10-01 19:22:16 +0000795 void %<a href="#format_common_declare">llvm.dbg.declare</a>(metadata, metadata)
Jim Laskeycec12a52006-03-14 18:08:46 +0000796</pre>
797
Jim Laskey2d395d92006-03-24 09:20:27 +0000798<p>This intrinsic provides information about a local element (ex. variable.) The
Devang Patel4c7c0c62010-10-01 19:22:16 +0000799 first argument is metadata holding alloca for the variable.</tt>. The
Devang Patele136e502011-02-01 17:22:12 +0000800 second argument is metadata containing description of the variable. </p>
Jim Laskeycec12a52006-03-14 18:08:46 +0000801</div>
802
803<!-- ======================================================================= -->
Victor Hernandez67a1a542010-01-11 22:53:48 +0000804<div class="doc_subsubsection">
805 <a name="format_common_value">llvm.dbg.value</a>
806</div>
807
808<div class="doc_text">
809<pre>
Dan Gohman3dfb3cf2010-05-28 17:07:41 +0000810 void %<a href="#format_common_value">llvm.dbg.value</a>(metadata, i64, metadata)
Victor Hernandez67a1a542010-01-11 22:53:48 +0000811</pre>
812
813<p>This intrinsic provides information when a user source variable is set to a
814 new value. The first argument is the new value (wrapped as metadata). The
815 second argument is the offset in the user source variable where the new value
Devang Patele136e502011-02-01 17:22:12 +0000816 is written. The third argument is metadata containing description of the
817 user source variable. </p>
Victor Hernandez67a1a542010-01-11 22:53:48 +0000818</div>
819
820<!-- ======================================================================= -->
Jim Laskeycec12a52006-03-14 18:08:46 +0000821<div class="doc_subsection">
Chris Lattner8ff75902004-01-06 05:31:32 +0000822 <a name="format_common_lifetime">Object lifetimes and scoping</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000823</div>
824
825<div class="doc_text">
Bill Wendlingcf493b82009-12-01 00:53:11 +0000826<p>In many languages, the local variables in functions can have their lifetimes
827 or scopes limited to a subset of a function. In the C family of languages,
Bill Wendling48839d92009-05-17 05:52:39 +0000828 for example, variables are only live (readable and writable) within the
829 source block that they are defined in. In functional languages, values are
830 only readable after they have been defined. Though this is a very obvious
Bill Wendlingcf493b82009-12-01 00:53:11 +0000831 concept, it is non-trivial to model in LLVM, because it has no notion of
Bill Wendling48839d92009-05-17 05:52:39 +0000832 scoping in this sense, and does not want to be tied to a language's scoping
833 rules.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000834
Bill Wendlingcf493b82009-12-01 00:53:11 +0000835<p>In order to handle this, the LLVM debug format uses the metadata attached to
Nick Lewycky655fd032010-03-31 07:50:17 +0000836 llvm instructions to encode line number and scoping information. Consider
837 the following C fragment, for example:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000838
Bill Wendling48839d92009-05-17 05:52:39 +0000839<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000840<pre>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008411. void foo() {
Devang Patel744950d2009-11-25 23:28:01 +00008422. int X = 21;
8433. int Y = 22;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008444. {
Devang Patel744950d2009-11-25 23:28:01 +00008455. int Z = 23;
8466. Z = X;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008477. }
Devang Patel744950d2009-11-25 23:28:01 +00008488. X = Y;
Chris Lattnerbdfb3392004-01-05 05:06:33 +00008499. }
Misha Brukman82873732004-05-12 19:21:57 +0000850</pre>
Bill Wendling48839d92009-05-17 05:52:39 +0000851</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000852
Jim Laskeycec12a52006-03-14 18:08:46 +0000853<p>Compiled to LLVM, this function would be represented like this:</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000854
Bill Wendling48839d92009-05-17 05:52:39 +0000855<div class="doc_code">
Misha Brukman82873732004-05-12 19:21:57 +0000856<pre>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000857define void @foo() nounwind ssp {
Jim Laskeycec12a52006-03-14 18:08:46 +0000858entry:
Bill Wendling02216ff2009-12-01 00:59:58 +0000859 %X = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
860 %Y = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
861 %Z = alloca i32, align 4 ; &lt;i32*&gt; [#uses=3]
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000862 %0 = bitcast i32* %X to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel37280782011-02-03 00:22:17 +0000863 call void @llvm.dbg.declare(metadata !{i32 * %X}, metadata !0), !dbg !7
Devang Patel744950d2009-11-25 23:28:01 +0000864 store i32 21, i32* %X, !dbg !8
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000865 %1 = bitcast i32* %Y to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel37280782011-02-03 00:22:17 +0000866 call void @llvm.dbg.declare(metadata !{i32 * %Y}, metadata !9), !dbg !10
Devang Patel744950d2009-11-25 23:28:01 +0000867 store i32 22, i32* %Y, !dbg !11
Dan Gohmanfe47aae2010-05-28 17:13:49 +0000868 %2 = bitcast i32* %Z to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel37280782011-02-03 00:22:17 +0000869 call void @llvm.dbg.declare(metadata !{i32 * %Z}, metadata !12), !dbg !14
Devang Patel744950d2009-11-25 23:28:01 +0000870 store i32 23, i32* %Z, !dbg !15
Bill Wendling02216ff2009-12-01 00:59:58 +0000871 %tmp = load i32* %X, !dbg !16 ; &lt;i32&gt; [#uses=1]
872 %tmp1 = load i32* %Y, !dbg !16 ; &lt;i32&gt; [#uses=1]
873 %add = add nsw i32 %tmp, %tmp1, !dbg !16 ; &lt;i32&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000874 store i32 %add, i32* %Z, !dbg !16
Bill Wendling02216ff2009-12-01 00:59:58 +0000875 %tmp2 = load i32* %Y, !dbg !17 ; &lt;i32&gt; [#uses=1]
Devang Patel744950d2009-11-25 23:28:01 +0000876 store i32 %tmp2, i32* %X, !dbg !17
877 ret void, !dbg !18
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000878}
Devang Patel744950d2009-11-25 23:28:01 +0000879
Devang Patel37280782011-02-03 00:22:17 +0000880declare void @llvm.dbg.declare(metadata, metadata) nounwind readnone
Devang Patel744950d2009-11-25 23:28:01 +0000881
882!0 = metadata !{i32 459008, metadata !1, metadata !"X",
883 metadata !3, i32 2, metadata !6}; [ DW_TAG_auto_variable ]
884!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
885!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo", metadata !"foo",
886 metadata !"foo", metadata !3, i32 1, metadata !4,
887 i1 false, i1 true}; [DW_TAG_subprogram ]
888!3 = metadata !{i32 458769, i32 0, i32 12, metadata !"foo.c",
889 metadata !"/private/tmp", metadata !"clang 1.1", i1 true,
890 i1 false, metadata !"", i32 0}; [DW_TAG_compile_unit ]
891!4 = metadata !{i32 458773, metadata !3, metadata !"", null, i32 0, i64 0, i64 0,
892 i64 0, i32 0, null, metadata !5, i32 0}; [DW_TAG_subroutine_type ]
893!5 = metadata !{null}
894!6 = metadata !{i32 458788, metadata !3, metadata !"int", metadata !3, i32 0,
895 i64 32, i64 32, i64 0, i32 0, i32 5}; [DW_TAG_base_type ]
896!7 = metadata !{i32 2, i32 7, metadata !1, null}
897!8 = metadata !{i32 2, i32 3, metadata !1, null}
898!9 = metadata !{i32 459008, metadata !1, metadata !"Y", metadata !3, i32 3,
899 metadata !6}; [ DW_TAG_auto_variable ]
900!10 = metadata !{i32 3, i32 7, metadata !1, null}
901!11 = metadata !{i32 3, i32 3, metadata !1, null}
902!12 = metadata !{i32 459008, metadata !13, metadata !"Z", metadata !3, i32 5,
903 metadata !6}; [ DW_TAG_auto_variable ]
904!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
905!14 = metadata !{i32 5, i32 9, metadata !13, null}
906!15 = metadata !{i32 5, i32 5, metadata !13, null}
907!16 = metadata !{i32 6, i32 5, metadata !13, null}
908!17 = metadata !{i32 8, i32 3, metadata !1, null}
909!18 = metadata !{i32 9, i32 1, metadata !2, null}
Misha Brukman82873732004-05-12 19:21:57 +0000910</pre>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000911</div>
912
Bill Wendlingcf493b82009-12-01 00:53:11 +0000913<p>This example illustrates a few important details about LLVM debugging
914 information. In particular, it shows how the <tt>llvm.dbg.declare</tt>
915 intrinsic and location information, which are attached to an instruction,
916 are applied together to allow a debugger to analyze the relationship between
917 statements, variable definitions, and the code used to implement the
918 function.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000919
Bill Wendlingcf493b82009-12-01 00:53:11 +0000920<div class="doc_code">
Bill Wendling02216ff2009-12-01 00:59:58 +0000921<pre>
Devang Patel37280782011-02-03 00:22:17 +0000922call void @llvm.dbg.declare(metadata, metadata !0), !dbg !7
Bill Wendlingcf493b82009-12-01 00:53:11 +0000923</pre>
924</div>
925
926<p>The first intrinsic
Devang Patel744950d2009-11-25 23:28:01 +0000927 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000928 encodes debugging information for the variable <tt>X</tt>. The metadata
929 <tt>!dbg !7</tt> attached to the intrinsic provides scope information for the
930 variable <tt>X</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000931
Bill Wendlingcf493b82009-12-01 00:53:11 +0000932<div class="doc_code">
933<pre>
934!7 = metadata !{i32 2, i32 7, metadata !1, null}
935!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
936!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo",
937 metadata !"foo", metadata !"foo", metadata !3, i32 1,
938 metadata !4, i1 false, i1 true}; [DW_TAG_subprogram ]
939</pre>
940</div>
941
942<p>Here <tt>!7</tt> is metadata providing location information. It has four
943 fields: line number, column number, scope, and original scope. The original
944 scope represents inline location if this instruction is inlined inside a
945 caller, and is null otherwise. In this example, scope is encoded by
Devang Patel744950d2009-11-25 23:28:01 +0000946 <tt>!1</tt>. <tt>!1</tt> represents a lexical block inside the scope
947 <tt>!2</tt>, where <tt>!2</tt> is a
Bill Wendlingcf493b82009-12-01 00:53:11 +0000948 <a href="#format_subprograms">subprogram descriptor</a>. This way the
949 location information attached to the intrinsics indicates that the
950 variable <tt>X</tt> is declared at line number 2 at a function level scope in
951 function <tt>foo</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000952
Devang Patel744950d2009-11-25 23:28:01 +0000953<p>Now lets take another example.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000954
Bill Wendlingcf493b82009-12-01 00:53:11 +0000955<div class="doc_code">
Bill Wendling02216ff2009-12-01 00:59:58 +0000956<pre>
Devang Patel37280782011-02-03 00:22:17 +0000957call void @llvm.dbg.declare(metadata, metadata !12), !dbg !14
Bill Wendlingcf493b82009-12-01 00:53:11 +0000958</pre>
959</div>
960
961<p>The second intrinsic
Devang Patel744950d2009-11-25 23:28:01 +0000962 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendlingcf493b82009-12-01 00:53:11 +0000963 encodes debugging information for variable <tt>Z</tt>. The metadata
964 <tt>!dbg !14</tt> attached to the intrinsic provides scope information for
965 the variable <tt>Z</tt>.</p>
Bill Wendling48839d92009-05-17 05:52:39 +0000966
Bill Wendlingcf493b82009-12-01 00:53:11 +0000967<div class="doc_code">
968<pre>
969!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
970!14 = metadata !{i32 5, i32 9, metadata !13, null}
971</pre>
972</div>
Bill Wendling48839d92009-05-17 05:52:39 +0000973
John Criswellb34500f2010-03-17 15:01:50 +0000974<p>Here <tt>!14</tt> indicates that <tt>Z</tt> is declared at line number 5 and
Bill Wendlingcf493b82009-12-01 00:53:11 +0000975 column number 9 inside of lexical scope <tt>!13</tt>. The lexical scope
976 itself resides inside of lexical scope <tt>!1</tt> described above.</p>
977
978<p>The scope information attached with each instruction provides a
979 straightforward way to find instructions covered by a scope.</p>
980
Bill Wendling48839d92009-05-17 05:52:39 +0000981</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000982
983<!-- *********************************************************************** -->
984<div class="doc_section">
Chris Lattner8ff75902004-01-06 05:31:32 +0000985 <a name="ccxx_frontend">C/C++ front-end specific debug information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000986</div>
Misha Brukman94218a72004-12-09 20:27:37 +0000987<!-- *********************************************************************** -->
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000988
989<div class="doc_text">
990
Misha Brukman82873732004-05-12 19:21:57 +0000991<p>The C and C++ front-ends represent information about the program in a format
Bill Wendling48839d92009-05-17 05:52:39 +0000992 that is effectively identical
993 to <a href="http://www.eagercon.com/dwarf/dwarf3std.htm">DWARF 3.0</a> in
994 terms of information content. This allows code generators to trivially
995 support native debuggers by generating standard dwarf information, and
996 contains enough information for non-dwarf targets to translate it as
997 needed.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +0000998
Jim Laskeycec12a52006-03-14 18:08:46 +0000999<p>This section describes the forms used to represent C and C++ programs. Other
Bill Wendling48839d92009-05-17 05:52:39 +00001000 languages could pattern themselves after this (which itself is tuned to
1001 representing programs in the same way that DWARF 3 does), or they could
1002 choose to provide completely different forms if they don't fit into the DWARF
1003 model. As support for debugging information gets added to the various LLVM
1004 source-language front-ends, the information used should be documented
1005 here.</p>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001006
Jim Laskeycec12a52006-03-14 18:08:46 +00001007<p>The following sections provide examples of various C/C++ constructs and the
Bill Wendling48839d92009-05-17 05:52:39 +00001008 debug information that would best describe those constructs.</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001009
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001010</div>
1011
1012<!-- ======================================================================= -->
1013<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +00001014 <a name="ccxx_compile_units">C/C++ source file information</a>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001015</div>
1016
1017<div class="doc_text">
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001018
Bill Wendling48839d92009-05-17 05:52:39 +00001019<p>Given the source files <tt>MySource.cpp</tt> and <tt>MyHeader.h</tt> located
1020 in the directory <tt>/Users/mine/sources</tt>, the following code:</p>
Chris Lattner8ff75902004-01-06 05:31:32 +00001021
Bill Wendling48839d92009-05-17 05:52:39 +00001022<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001023<pre>
1024#include "MyHeader.h"
Chris Lattner8ff75902004-01-06 05:31:32 +00001025
Jim Laskeycec12a52006-03-14 18:08:46 +00001026int main(int argc, char *argv[]) {
1027 return 0;
1028}
1029</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001030</div>
Chris Lattner8ff75902004-01-06 05:31:32 +00001031
Misha Brukman96e00812008-12-16 02:54:22 +00001032<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001033
Bill Wendling48839d92009-05-17 05:52:39 +00001034<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001035<pre>
1036...
1037;;
Devang Patel4b945502010-03-09 00:44:10 +00001038;; Define the compile unit for the main source file "/Users/mine/sources/MySource.cpp".
Jim Laskeycec12a52006-03-14 18:08:46 +00001039;;
Devang Patel4b945502010-03-09 00:44:10 +00001040!2 = metadata !{
1041 i32 524305, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001042 i32 0, ;; Unused
1043 i32 4, ;; Language Id
1044 metadata !"MySource.cpp",
1045 metadata !"/Users/mine/sources",
1046 metadata !"4.2.1 (Based on Apple Inc. build 5649) (LLVM build 00)",
1047 i1 true, ;; Main Compile Unit
1048 i1 false, ;; Optimized compile unit
1049 metadata !"", ;; Compiler flags
1050 i32 0} ;; Runtime version
1051
Jim Laskeycec12a52006-03-14 18:08:46 +00001052;;
Devang Patel4b945502010-03-09 00:44:10 +00001053;; Define the file for the file "/Users/mine/sources/MySource.cpp".
Jim Laskeycec12a52006-03-14 18:08:46 +00001054;;
Devang Patele4b27562009-08-28 23:24:31 +00001055!1 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001056 i32 524329, ;; Tag
1057 metadata !"MySource.cpp",
Devang Patele4b27562009-08-28 23:24:31 +00001058 metadata !"/Users/mine/sources",
Devang Patel9fea9c22010-07-13 16:53:20 +00001059 metadata !2 ;; Compile unit
Devang Patel4b945502010-03-09 00:44:10 +00001060}
1061
1062;;
1063;; Define the file for the file "/Users/mine/sources/Myheader.h"
1064;;
1065!3 = metadata !{
1066 i32 524329, ;; Tag
1067 metadata !"Myheader.h"
1068 metadata !"/Users/mine/sources",
Devang Patel9fea9c22010-07-13 16:53:20 +00001069 metadata !2 ;; Compile unit
Devang Patel4b945502010-03-09 00:44:10 +00001070}
Jim Laskeycec12a52006-03-14 18:08:46 +00001071
Jim Laskeycec12a52006-03-14 18:08:46 +00001072...
1073</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001074</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001075
Devang Pateld98ec5f2010-03-26 19:08:36 +00001076<p>llvm::Instruction provides easy access to metadata attached with an
1077instruction. One can extract line number information encoded in LLVM IR
1078using <tt>Instruction::getMetadata()</tt> and
1079<tt>DILocation::getLineNumber()</tt>.
1080<pre>
1081 if (MDNode *N = I->getMetadata("dbg")) { // Here I is an LLVM instruction
1082 DILocation Loc(N); // DILocation is in DebugInfo.h
1083 unsigned Line = Loc.getLineNumber();
1084 StringRef File = Loc.getFilename();
1085 StringRef Dir = Loc.getDirectory();
1086 }
1087</pre>
Chris Lattner8ff75902004-01-06 05:31:32 +00001088</div>
1089
1090<!-- ======================================================================= -->
1091<div class="doc_subsection">
Jim Laskeycec12a52006-03-14 18:08:46 +00001092 <a name="ccxx_global_variable">C/C++ global variable information</a>
Chris Lattner8ff75902004-01-06 05:31:32 +00001093</div>
1094
1095<div class="doc_text">
Jim Laskeycec12a52006-03-14 18:08:46 +00001096
Misha Brukman96e00812008-12-16 02:54:22 +00001097<p>Given an integer global variable declared as follows:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001098
Bill Wendling48839d92009-05-17 05:52:39 +00001099<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001100<pre>
1101int MyGlobal = 100;
1102</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001103</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001104
Misha Brukman96e00812008-12-16 02:54:22 +00001105<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001106
Bill Wendling48839d92009-05-17 05:52:39 +00001107<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001108<pre>
1109;;
Jim Laskeycec12a52006-03-14 18:08:46 +00001110;; Define the global itself.
1111;;
1112%MyGlobal = global int 100
1113...
1114;;
Devang Patele4b27562009-08-28 23:24:31 +00001115;; List of debug info of globals
Jim Laskeycec12a52006-03-14 18:08:46 +00001116;;
Devang Patele4b27562009-08-28 23:24:31 +00001117!llvm.dbg.gv = !{!0}
Jim Laskeycec12a52006-03-14 18:08:46 +00001118
1119;;
1120;; Define the global variable descriptor. Note the reference to the global
1121;; variable anchor and the global variable itself.
1122;;
Devang Patele4b27562009-08-28 23:24:31 +00001123!0 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001124 i32 524340, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001125 i32 0, ;; Unused
1126 metadata !1, ;; Context
1127 metadata !"MyGlobal", ;; Name
1128 metadata !"MyGlobal", ;; Display Name
1129 metadata !"MyGlobal", ;; Linkage Name
Devang Patel4b945502010-03-09 00:44:10 +00001130 metadata !3, ;; Compile Unit
Devang Patele4b27562009-08-28 23:24:31 +00001131 i32 1, ;; Line Number
Devang Patel4b945502010-03-09 00:44:10 +00001132 metadata !4, ;; Type
Devang Patele4b27562009-08-28 23:24:31 +00001133 i1 false, ;; Is a local variable
1134 i1 true, ;; Is this a definition
1135 i32* @MyGlobal ;; The global variable
1136}
1137
Jim Laskeycec12a52006-03-14 18:08:46 +00001138;;
1139;; Define the basic type of 32 bit signed integer. Note that since int is an
1140;; intrinsic type the source file is NULL and line 0.
1141;;
Devang Patel4b945502010-03-09 00:44:10 +00001142!4 = metadata !{
1143 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001144 metadata !1, ;; Context
1145 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001146 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001147 i32 0, ;; Line number
1148 i64 32, ;; Size in Bits
1149 i64 32, ;; Align in Bits
1150 i64 0, ;; Offset in Bits
1151 i32 0, ;; Flags
1152 i32 5 ;; Encoding
1153}
Jim Laskeycec12a52006-03-14 18:08:46 +00001154
Jim Laskeycec12a52006-03-14 18:08:46 +00001155</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001156</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001157
Chris Lattner8ff75902004-01-06 05:31:32 +00001158</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001159
Jim Laskeycec12a52006-03-14 18:08:46 +00001160<!-- ======================================================================= -->
1161<div class="doc_subsection">
1162 <a name="ccxx_subprogram">C/C++ function information</a>
1163</div>
1164
1165<div class="doc_text">
1166
Misha Brukman96e00812008-12-16 02:54:22 +00001167<p>Given a function declared as follows:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001168
Bill Wendling48839d92009-05-17 05:52:39 +00001169<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001170<pre>
1171int main(int argc, char *argv[]) {
1172 return 0;
1173}
1174</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001175</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001176
Misha Brukman96e00812008-12-16 02:54:22 +00001177<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001178
Bill Wendling48839d92009-05-17 05:52:39 +00001179<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001180<pre>
1181;;
Jim Laskeycec12a52006-03-14 18:08:46 +00001182;; Define the anchor for subprograms. Note that the second field of the
1183;; anchor is 46, which is the same as the tag for subprograms
1184;; (46 = DW_TAG_subprogram.)
1185;;
Devang Patel4b945502010-03-09 00:44:10 +00001186!6 = metadata !{
1187 i32 524334, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001188 i32 0, ;; Unused
1189 metadata !1, ;; Context
1190 metadata !"main", ;; Name
1191 metadata !"main", ;; Display name
1192 metadata !"main", ;; Linkage name
Devang Patel4b945502010-03-09 00:44:10 +00001193 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001194 i32 1, ;; Line number
Devang Patel4b945502010-03-09 00:44:10 +00001195 metadata !4, ;; Type
Devang Patele4b27562009-08-28 23:24:31 +00001196 i1 false, ;; Is local
1197 i1 true ;; Is definition
1198}
Jim Laskeycec12a52006-03-14 18:08:46 +00001199;;
1200;; Define the subprogram itself.
1201;;
Devang Patele4b27562009-08-28 23:24:31 +00001202define i32 @main(i32 %argc, i8** %argv) {
Jim Laskeycec12a52006-03-14 18:08:46 +00001203...
1204}
1205</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001206</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001207
1208</div>
1209
1210<!-- ======================================================================= -->
1211<div class="doc_subsection">
1212 <a name="ccxx_basic_types">C/C++ basic types</a>
1213</div>
1214
1215<div class="doc_text">
1216
Misha Brukman96e00812008-12-16 02:54:22 +00001217<p>The following are the basic type descriptors for C/C++ core types:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001218
1219</div>
1220
1221<!-- ======================================================================= -->
1222<div class="doc_subsubsection">
1223 <a name="ccxx_basic_type_bool">bool</a>
1224</div>
1225
1226<div class="doc_text">
1227
Bill Wendling48839d92009-05-17 05:52:39 +00001228<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001229<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001230!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001231 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001232 metadata !1, ;; Context
1233 metadata !"bool", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001234 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001235 i32 0, ;; Line number
1236 i64 8, ;; Size in Bits
1237 i64 8, ;; Align in Bits
1238 i64 0, ;; Offset in Bits
1239 i32 0, ;; Flags
1240 i32 2 ;; Encoding
1241}
Jim Laskeycec12a52006-03-14 18:08:46 +00001242</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001243</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001244
1245</div>
1246
1247<!-- ======================================================================= -->
1248<div class="doc_subsubsection">
1249 <a name="ccxx_basic_char">char</a>
1250</div>
1251
1252<div class="doc_text">
1253
Bill Wendling48839d92009-05-17 05:52:39 +00001254<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001255<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001256!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001257 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001258 metadata !1, ;; Context
1259 metadata !"char", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001260 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001261 i32 0, ;; Line number
1262 i64 8, ;; Size in Bits
1263 i64 8, ;; Align in Bits
1264 i64 0, ;; Offset in Bits
1265 i32 0, ;; Flags
1266 i32 6 ;; Encoding
1267}
Jim Laskeycec12a52006-03-14 18:08:46 +00001268</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001269</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001270
1271</div>
1272
1273<!-- ======================================================================= -->
1274<div class="doc_subsubsection">
1275 <a name="ccxx_basic_unsigned_char">unsigned char</a>
1276</div>
1277
1278<div class="doc_text">
1279
Bill Wendling48839d92009-05-17 05:52:39 +00001280<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001281<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001282!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001283 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001284 metadata !1, ;; Context
1285 metadata !"unsigned char",
Devang Patel4b945502010-03-09 00:44:10 +00001286 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001287 i32 0, ;; Line number
1288 i64 8, ;; Size in Bits
1289 i64 8, ;; Align in Bits
1290 i64 0, ;; Offset in Bits
1291 i32 0, ;; Flags
1292 i32 8 ;; Encoding
1293}
Jim Laskeycec12a52006-03-14 18:08:46 +00001294</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001295</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001296
1297</div>
1298
1299<!-- ======================================================================= -->
1300<div class="doc_subsubsection">
1301 <a name="ccxx_basic_short">short</a>
1302</div>
1303
1304<div class="doc_text">
1305
Bill Wendling48839d92009-05-17 05:52:39 +00001306<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001307<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001308!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001309 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001310 metadata !1, ;; Context
1311 metadata !"short int",
Devang Patel4b945502010-03-09 00:44:10 +00001312 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001313 i32 0, ;; Line number
1314 i64 16, ;; Size in Bits
1315 i64 16, ;; Align in Bits
1316 i64 0, ;; Offset in Bits
1317 i32 0, ;; Flags
1318 i32 5 ;; Encoding
1319}
Jim Laskeycec12a52006-03-14 18:08:46 +00001320</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001321</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001322
1323</div>
1324
1325<!-- ======================================================================= -->
1326<div class="doc_subsubsection">
1327 <a name="ccxx_basic_unsigned_short">unsigned short</a>
1328</div>
1329
1330<div class="doc_text">
1331
Bill Wendling48839d92009-05-17 05:52:39 +00001332<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001333<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001334!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001335 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001336 metadata !1, ;; Context
1337 metadata !"short unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001338 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001339 i32 0, ;; Line number
1340 i64 16, ;; Size in Bits
1341 i64 16, ;; Align in Bits
1342 i64 0, ;; Offset in Bits
1343 i32 0, ;; Flags
1344 i32 7 ;; Encoding
1345}
Jim Laskeycec12a52006-03-14 18:08:46 +00001346</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001347</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001348
1349</div>
1350
1351<!-- ======================================================================= -->
1352<div class="doc_subsubsection">
1353 <a name="ccxx_basic_int">int</a>
1354</div>
1355
1356<div class="doc_text">
1357
Bill Wendling48839d92009-05-17 05:52:39 +00001358<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001359<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001360!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001361 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001362 metadata !1, ;; Context
1363 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001364 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001365 i32 0, ;; Line number
1366 i64 32, ;; Size in Bits
1367 i64 32, ;; Align in Bits
1368 i64 0, ;; Offset in Bits
1369 i32 0, ;; Flags
1370 i32 5 ;; Encoding
1371}
Bill Wendling48839d92009-05-17 05:52:39 +00001372</pre></div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001373
1374</div>
1375
1376<!-- ======================================================================= -->
1377<div class="doc_subsubsection">
1378 <a name="ccxx_basic_unsigned_int">unsigned int</a>
1379</div>
1380
1381<div class="doc_text">
1382
Bill Wendling48839d92009-05-17 05:52:39 +00001383<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001384<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001385!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001386 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001387 metadata !1, ;; Context
1388 metadata !"unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001389 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001390 i32 0, ;; Line number
1391 i64 32, ;; Size in Bits
1392 i64 32, ;; Align in Bits
1393 i64 0, ;; Offset in Bits
1394 i32 0, ;; Flags
1395 i32 7 ;; Encoding
1396}
Jim Laskeycec12a52006-03-14 18:08:46 +00001397</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001398</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001399
1400</div>
1401
1402<!-- ======================================================================= -->
1403<div class="doc_subsubsection">
1404 <a name="ccxx_basic_long_long">long long</a>
1405</div>
1406
1407<div class="doc_text">
1408
Bill Wendling48839d92009-05-17 05:52:39 +00001409<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001410<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001411!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001412 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001413 metadata !1, ;; Context
1414 metadata !"long long int",
Devang Patel4b945502010-03-09 00:44:10 +00001415 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001416 i32 0, ;; Line number
1417 i64 64, ;; Size in Bits
1418 i64 64, ;; Align in Bits
1419 i64 0, ;; Offset in Bits
1420 i32 0, ;; Flags
1421 i32 5 ;; Encoding
1422}
Jim Laskeycec12a52006-03-14 18:08:46 +00001423</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001424</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001425
1426</div>
1427
1428<!-- ======================================================================= -->
1429<div class="doc_subsubsection">
1430 <a name="ccxx_basic_unsigned_long_long">unsigned long long</a>
1431</div>
1432
1433<div class="doc_text">
1434
Bill Wendling48839d92009-05-17 05:52:39 +00001435<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001436<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001437!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001438 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001439 metadata !1, ;; Context
1440 metadata !"long long unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001441 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001442 i32 0, ;; Line number
1443 i64 64, ;; Size in Bits
1444 i64 64, ;; Align in Bits
1445 i64 0, ;; Offset in Bits
1446 i32 0, ;; Flags
1447 i32 7 ;; Encoding
1448}
Jim Laskeycec12a52006-03-14 18:08:46 +00001449</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001450</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001451
1452</div>
1453
1454<!-- ======================================================================= -->
1455<div class="doc_subsubsection">
1456 <a name="ccxx_basic_float">float</a>
1457</div>
1458
1459<div class="doc_text">
1460
Bill Wendling48839d92009-05-17 05:52:39 +00001461<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001462<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001463!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001464 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001465 metadata !1, ;; Context
1466 metadata !"float",
Devang Patel4b945502010-03-09 00:44:10 +00001467 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001468 i32 0, ;; Line number
1469 i64 32, ;; Size in Bits
1470 i64 32, ;; Align in Bits
1471 i64 0, ;; Offset in Bits
1472 i32 0, ;; Flags
1473 i32 4 ;; Encoding
1474}
Jim Laskeycec12a52006-03-14 18:08:46 +00001475</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001476</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001477
1478</div>
1479
1480<!-- ======================================================================= -->
1481<div class="doc_subsubsection">
1482 <a name="ccxx_basic_double">double</a>
1483</div>
1484
1485<div class="doc_text">
1486
Bill Wendling48839d92009-05-17 05:52:39 +00001487<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001488<pre>
Devang Patele4b27562009-08-28 23:24:31 +00001489!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001490 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001491 metadata !1, ;; Context
1492 metadata !"double",;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001493 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001494 i32 0, ;; Line number
1495 i64 64, ;; Size in Bits
1496 i64 64, ;; Align in Bits
1497 i64 0, ;; Offset in Bits
1498 i32 0, ;; Flags
1499 i32 4 ;; Encoding
1500}
Jim Laskeycec12a52006-03-14 18:08:46 +00001501</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001502</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001503
1504</div>
1505
1506<!-- ======================================================================= -->
1507<div class="doc_subsection">
1508 <a name="ccxx_derived_types">C/C++ derived types</a>
1509</div>
1510
1511<div class="doc_text">
1512
Misha Brukman96e00812008-12-16 02:54:22 +00001513<p>Given the following as an example of C/C++ derived type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001514
Bill Wendling48839d92009-05-17 05:52:39 +00001515<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001516<pre>
1517typedef const int *IntPtr;
1518</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001519</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001520
Misha Brukman96e00812008-12-16 02:54:22 +00001521<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001522
Bill Wendling48839d92009-05-17 05:52:39 +00001523<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001524<pre>
1525;;
1526;; Define the typedef "IntPtr".
1527;;
Devang Patele4b27562009-08-28 23:24:31 +00001528!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001529 i32 524310, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001530 metadata !1, ;; Context
1531 metadata !"IntPtr", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001532 metadata !3, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001533 i32 0, ;; Line number
1534 i64 0, ;; Size in bits
1535 i64 0, ;; Align in bits
1536 i64 0, ;; Offset in bits
1537 i32 0, ;; Flags
1538 metadata !4 ;; Derived From type
1539}
Jim Laskeycec12a52006-03-14 18:08:46 +00001540
1541;;
1542;; Define the pointer type.
1543;;
Devang Patele4b27562009-08-28 23:24:31 +00001544!4 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001545 i32 524303, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001546 metadata !1, ;; Context
1547 metadata !"", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001548 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001549 i32 0, ;; Line number
1550 i64 64, ;; Size in bits
1551 i64 64, ;; Align in bits
1552 i64 0, ;; Offset in bits
1553 i32 0, ;; Flags
1554 metadata !5 ;; Derived From type
1555}
Jim Laskeycec12a52006-03-14 18:08:46 +00001556;;
1557;; Define the const type.
1558;;
Devang Patele4b27562009-08-28 23:24:31 +00001559!5 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001560 i32 524326, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001561 metadata !1, ;; Context
1562 metadata !"", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001563 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001564 i32 0, ;; Line number
1565 i64 32, ;; Size in bits
1566 i64 32, ;; Align in bits
1567 i64 0, ;; Offset in bits
1568 i32 0, ;; Flags
1569 metadata !6 ;; Derived From type
1570}
Jim Laskeycec12a52006-03-14 18:08:46 +00001571;;
1572;; Define the int type.
1573;;
Devang Patele4b27562009-08-28 23:24:31 +00001574!6 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001575 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001576 metadata !1, ;; Context
1577 metadata !"int", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001578 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001579 i32 0, ;; Line number
1580 i64 32, ;; Size in bits
1581 i64 32, ;; Align in bits
1582 i64 0, ;; Offset in bits
1583 i32 0, ;; Flags
1584 5 ;; Encoding
1585}
Jim Laskeycec12a52006-03-14 18:08:46 +00001586</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001587</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001588
1589</div>
1590
1591<!-- ======================================================================= -->
1592<div class="doc_subsection">
1593 <a name="ccxx_composite_types">C/C++ struct/union types</a>
1594</div>
1595
1596<div class="doc_text">
1597
Misha Brukman96e00812008-12-16 02:54:22 +00001598<p>Given the following as an example of C/C++ struct type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001599
Bill Wendling48839d92009-05-17 05:52:39 +00001600<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001601<pre>
1602struct Color {
1603 unsigned Red;
1604 unsigned Green;
1605 unsigned Blue;
1606};
1607</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001608</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001609
Misha Brukman96e00812008-12-16 02:54:22 +00001610<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001611
Bill Wendling48839d92009-05-17 05:52:39 +00001612<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001613<pre>
1614;;
1615;; Define basic type for unsigned int.
1616;;
Devang Patele4b27562009-08-28 23:24:31 +00001617!5 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001618 i32 524324, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001619 metadata !1, ;; Context
1620 metadata !"unsigned int",
Devang Patel4b945502010-03-09 00:44:10 +00001621 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001622 i32 0, ;; Line number
1623 i64 32, ;; Size in Bits
1624 i64 32, ;; Align in Bits
1625 i64 0, ;; Offset in Bits
1626 i32 0, ;; Flags
1627 i32 7 ;; Encoding
1628}
Jim Laskeycec12a52006-03-14 18:08:46 +00001629;;
1630;; Define composite type for struct Color.
1631;;
Devang Patele4b27562009-08-28 23:24:31 +00001632!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001633 i32 524307, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001634 metadata !1, ;; Context
1635 metadata !"Color", ;; Name
1636 metadata !1, ;; Compile unit
1637 i32 1, ;; Line number
1638 i64 96, ;; Size in bits
1639 i64 32, ;; Align in bits
1640 i64 0, ;; Offset in bits
1641 i32 0, ;; Flags
1642 null, ;; Derived From
1643 metadata !3, ;; Elements
1644 i32 0 ;; Runtime Language
1645}
Jim Laskeycec12a52006-03-14 18:08:46 +00001646
1647;;
1648;; Define the Red field.
1649;;
Devang Patele4b27562009-08-28 23:24:31 +00001650!4 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001651 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001652 metadata !1, ;; Context
1653 metadata !"Red", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001654 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001655 i32 2, ;; Line number
1656 i64 32, ;; Size in bits
1657 i64 32, ;; Align in bits
1658 i64 0, ;; Offset in bits
1659 i32 0, ;; Flags
1660 metadata !5 ;; Derived From type
1661}
Jim Laskeycec12a52006-03-14 18:08:46 +00001662
1663;;
1664;; Define the Green field.
1665;;
Devang Patele4b27562009-08-28 23:24:31 +00001666!6 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001667 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001668 metadata !1, ;; Context
1669 metadata !"Green", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001670 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001671 i32 3, ;; Line number
1672 i64 32, ;; Size in bits
1673 i64 32, ;; Align in bits
1674 i64 32, ;; Offset in bits
1675 i32 0, ;; Flags
1676 metadata !5 ;; Derived From type
1677}
Jim Laskeycec12a52006-03-14 18:08:46 +00001678
1679;;
1680;; Define the Blue field.
1681;;
Devang Patele4b27562009-08-28 23:24:31 +00001682!7 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001683 i32 524301, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001684 metadata !1, ;; Context
1685 metadata !"Blue", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001686 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001687 i32 4, ;; Line number
1688 i64 32, ;; Size in bits
1689 i64 32, ;; Align in bits
1690 i64 64, ;; Offset in bits
1691 i32 0, ;; Flags
1692 metadata !5 ;; Derived From type
1693}
Jim Laskeycec12a52006-03-14 18:08:46 +00001694
1695;;
1696;; Define the array of fields used by the composite type Color.
1697;;
Devang Patele4b27562009-08-28 23:24:31 +00001698!3 = metadata !{metadata !4, metadata !6, metadata !7}
Jim Laskeycec12a52006-03-14 18:08:46 +00001699</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001700</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001701
1702</div>
1703
1704<!-- ======================================================================= -->
1705<div class="doc_subsection">
1706 <a name="ccxx_enumeration_types">C/C++ enumeration types</a>
1707</div>
1708
1709<div class="doc_text">
1710
Misha Brukman96e00812008-12-16 02:54:22 +00001711<p>Given the following as an example of C/C++ enumeration type:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001712
Bill Wendling48839d92009-05-17 05:52:39 +00001713<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001714<pre>
1715enum Trees {
1716 Spruce = 100,
1717 Oak = 200,
1718 Maple = 300
1719};
1720</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001721</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001722
Misha Brukman96e00812008-12-16 02:54:22 +00001723<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskeycec12a52006-03-14 18:08:46 +00001724
Bill Wendling48839d92009-05-17 05:52:39 +00001725<div class="doc_code">
Jim Laskeycec12a52006-03-14 18:08:46 +00001726<pre>
1727;;
1728;; Define composite type for enum Trees
1729;;
Devang Patele4b27562009-08-28 23:24:31 +00001730!2 = metadata !{
Devang Patel4b945502010-03-09 00:44:10 +00001731 i32 524292, ;; Tag
Devang Patele4b27562009-08-28 23:24:31 +00001732 metadata !1, ;; Context
1733 metadata !"Trees", ;; Name
Devang Patel4b945502010-03-09 00:44:10 +00001734 metadata !1, ;; File
Devang Patele4b27562009-08-28 23:24:31 +00001735 i32 1, ;; Line number
1736 i64 32, ;; Size in bits
1737 i64 32, ;; Align in bits
1738 i64 0, ;; Offset in bits
1739 i32 0, ;; Flags
1740 null, ;; Derived From type
1741 metadata !3, ;; Elements
1742 i32 0 ;; Runtime language
1743}
Devang Patel2a610c72009-08-25 05:24:07 +00001744
Devang Patel82459882009-08-26 05:01:18 +00001745;;
1746;; Define the array of enumerators used by composite type Trees.
1747;;
Devang Patele4b27562009-08-28 23:24:31 +00001748!3 = metadata !{metadata !4, metadata !5, metadata !6}
1749
1750;;
1751;; Define Spruce enumerator.
1752;;
Devang Patel4b945502010-03-09 00:44:10 +00001753!4 = metadata !{i32 524328, metadata !"Spruce", i64 100}
Devang Patele4b27562009-08-28 23:24:31 +00001754
1755;;
1756;; Define Oak enumerator.
1757;;
Devang Patel4b945502010-03-09 00:44:10 +00001758!5 = metadata !{i32 524328, metadata !"Oak", i64 200}
Devang Patele4b27562009-08-28 23:24:31 +00001759
1760;;
1761;; Define Maple enumerator.
1762;;
Devang Patel4b945502010-03-09 00:44:10 +00001763!6 = metadata !{i32 524328, metadata !"Maple", i64 300}
Devang Patele4b27562009-08-28 23:24:31 +00001764
Jim Laskeycec12a52006-03-14 18:08:46 +00001765</pre>
Bill Wendling48839d92009-05-17 05:52:39 +00001766</div>
Jim Laskeycec12a52006-03-14 18:08:46 +00001767
1768</div>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001769
1770<!-- *********************************************************************** -->
Misha Brukman82873732004-05-12 19:21:57 +00001771
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001772<hr>
Misha Brukman82873732004-05-12 19:21:57 +00001773<address>
1774 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001775 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukman82873732004-05-12 19:21:57 +00001776 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman44408702008-12-11 17:34:48 +00001777 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukman82873732004-05-12 19:21:57 +00001778
1779 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
Reid Spencer05fe4b02006-03-14 05:39:39 +00001780 <a href="http://llvm.org">LLVM Compiler Infrastructure</a><br>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001781 Last modified: $Date$
Misha Brukman82873732004-05-12 19:21:57 +00001782</address>
Chris Lattnerbdfb3392004-01-05 05:06:33 +00001783
1784</body>
1785</html>