blob: 2eb9aec8f580472614583ca6234584d0ecc6c1d8 [file] [log] [blame]
Chris Lattner1811fca2004-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 Wendlinge9353d72009-05-17 05:52:39 +00005 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Chris Lattner1811fca2004-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 Spencerc3c4c4f2004-11-01 08:19:36 +000013<table class="layout" style="width:100%">
14 <tr class="layout">
15 <td class="left">
Chris Lattner1811fca2004-01-05 05:06:33 +000016<ul>
Misha Brukmanf91d9942004-05-12 19:21:57 +000017 <li><a href="#introduction">Introduction</a>
Chris Lattner1811fca2004-01-05 05:06:33 +000018 <ol>
19 <li><a href="#phil">Philosophy behind LLVM debugging information</a></li>
Jim Laskey5dcfd562006-03-23 17:54:33 +000020 <li><a href="#consumers">Debug information consumers</a></li>
Chris Lattner1811fca2004-01-05 05:06:33 +000021 <li><a href="#debugopt">Debugging optimized code</a></li>
Misha Brukmanf91d9942004-05-12 19:21:57 +000022 </ol></li>
Misha Brukmanf91d9942004-05-12 19:21:57 +000023 <li><a href="#format">Debugging information format</a>
Chris Lattner1811fca2004-01-05 05:06:33 +000024 <ol>
Jim Laskey14edc932006-03-14 18:08:46 +000025 <li><a href="#debug_info_descriptors">Debug information descriptors</a>
Chris Lattner1811fca2004-01-05 05:06:33 +000026 <ul>
Jim Laskey14edc932006-03-14 18:08:46 +000027 <li><a href="#format_compile_units">Compile unit descriptors</a></li>
Devang Patel59445db2010-03-09 00:44:10 +000028 <li><a href="#format_files">File descriptors</a></li>
Jim Laskey14edc932006-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 Laskey9dcffe72006-03-15 19:10:52 +000031 <li><a href="#format_blocks">Block descriptors</a></li>
Jim Laskey14edc932006-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 Laskey5dcfd562006-03-23 17:54:33 +000037 <li><a href="#format_variables">Local variables</a></li>
Misha Brukmanf91d9942004-05-12 19:21:57 +000038 </ul></li>
Jim Laskey14edc932006-03-14 18:08:46 +000039 <li><a href="#format_common_intrinsics">Debugger intrinsic functions</a>
40 <ul>
Jim Laskey14edc932006-03-14 18:08:46 +000041 <li><a href="#format_common_declare">llvm.dbg.declare</a></li>
Victor Hernandez0b62cc62010-01-11 22:53:48 +000042 <li><a href="#format_common_value">llvm.dbg.value</a></li>
Jim Laskey14edc932006-03-14 18:08:46 +000043 </ul></li>
Misha Brukmanf91d9942004-05-12 19:21:57 +000044 </ol></li>
Devang Patel4da997b2009-11-25 23:28:01 +000045 <li><a href="#format_common_lifetime">Object lifetimes and scoping</a></li>
Misha Brukmanf91d9942004-05-12 19:21:57 +000046 <li><a href="#ccxx_frontend">C/C++ front-end specific debug information</a>
Chris Lattner1811fca2004-01-05 05:06:33 +000047 <ol>
Jim Laskey14edc932006-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 Brukmanf91d9942004-05-12 19:21:57 +000055 </ol></li>
Chris Lattner1811fca2004-01-05 05:06:33 +000056</ul>
Misha Brukmanf91d9942004-05-12 19:21:57 +000057</td>
Reid Spencerc3c4c4f2004-11-01 08:19:36 +000058<td class="right">
Misha Brukman3c1f8e72004-05-12 21:26:16 +000059<img src="img/venusflytrap.jpg" alt="A leafy and green bug eater" width="247"
Misha Brukmanf91d9942004-05-12 19:21:57 +000060height="369">
61</td>
Reid Spencerc3c4c4f2004-11-01 08:19:36 +000062</tr></table>
Misha Brukmanf91d9942004-05-12 19:21:57 +000063
Chris Lattner020e1fc2004-05-23 21:07:27 +000064<div class="doc_author">
Jim Laskey14edc932006-03-14 18:08:46 +000065 <p>Written by <a href="mailto:sabre@nondot.org">Chris Lattner</a>
Jim Laskey6e8a2f42007-03-14 19:32:21 +000066 and <a href="mailto:jlaskey@mac.com">Jim Laskey</a></p>
Chris Lattner020e1fc2004-05-23 21:07:27 +000067</div>
68
Chris Lattner1811fca2004-01-05 05:06:33 +000069
70<!-- *********************************************************************** -->
Misha Brukmancda6a9b2004-12-09 20:27:37 +000071<div class="doc_section"><a name="introduction">Introduction</a></div>
72<!-- *********************************************************************** -->
Chris Lattner1811fca2004-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 Wendlinge9353d72009-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 Lattnercb3f64f2009-07-18 21:47:15 +000080 Further, this document provides specific examples of what debug information
Chris Lattner92ec3d12011-01-18 06:12:10 +000081 for C/C++ looks like.</p>
Chris Lattner1811fca2004-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 Brukmanf91d9942004-05-12 19:21:57 +000092<p>The idea of the LLVM debugging information is to capture how the important
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +000096
Misha Brukmanf91d9942004-05-12 19:21:57 +000097<ul>
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000101
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000104
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000108
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000112
Bill Wendlinge9353d72009-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 Brukmanf91d9942004-05-12 19:21:57 +0000117</ul>
Chris Lattner1811fca2004-01-05 05:06:33 +0000118
Bill Wendlinge9353d72009-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 Patel80ae3492009-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 Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000127
Jim Laskey14edc932006-03-14 18:08:46 +0000128<p>When a program is being debugged, a debugger interacts with the user and
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000132
133</div>
134
Chris Lattner1811fca2004-01-05 05:06:33 +0000135<!-- ======================================================================= -->
136<div class="doc_subsection">
Jim Laskey5dcfd562006-03-23 17:54:33 +0000137 <a name="consumers">Debug information consumers</a>
138</div>
139
140<div class="doc_text">
Bill Wendlinge9353d72009-05-17 05:52:39 +0000141
Jim Laskey5dcfd562006-03-23 17:54:33 +0000142<p>The role of debug information is to provide meta information normally
Bill Wendlinge9353d72009-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 Laskey5dcfd562006-03-23 17:54:33 +0000146
Chris Lattner904f2172010-04-05 04:11:11 +0000147<p>Currently, debug information is consumed by DwarfDebug to produce dwarf
Bill Wendlinge9353d72009-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 Laskey5dcfd562006-03-23 17:54:33 +0000150
151<p>It would also be reasonable to use debug information to feed profiling tools
Bill Wendlinge9353d72009-05-17 05:52:39 +0000152 for analysis of generated code, or, tools for reconstructing the original
153 source from generated code.</p>
Jim Laskey5dcfd562006-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 Lattner1811fca2004-01-05 05:06:33 +0000161 <a name="debugopt">Debugging optimized code</a>
162</div>
163
164<div class="doc_text">
Chris Lattner1811fca2004-01-05 05:06:33 +0000165
Misha Brukmanf91d9942004-05-12 19:21:57 +0000166<p>An extremely high priority of LLVM debugging information is to make it
Bill Wendlinge9353d72009-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 Brukmanf91d9942004-05-12 19:21:57 +0000169
170<ul>
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000178
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000184
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000190
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000195
Bill Wendlinge9353d72009-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 Brukmanf91d9942004-05-12 19:21:57 +0000200</ul>
Chris Lattner1811fca2004-01-05 05:06:33 +0000201
Misha Brukmanf91d9942004-05-12 19:21:57 +0000202<p>Basically, the debug information allows you to compile a program with
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000210
Misha Brukman39dcddf2008-12-16 02:54:22 +0000211<p><a href="TestingGuide.html#quicktestsuite">LLVM test suite</a> provides a
Bill Wendlinge9353d72009-05-17 05:52:39 +0000212 framework to test optimizer's handling of debugging information. It can be
213 run like this:</p>
Devang Patelb885a912008-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 Wendlinge9353d72009-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 Patelb885a912008-11-21 19:35:57 +0000226
Chris Lattner1811fca2004-01-05 05:06:33 +0000227</div>
228
Chris Lattner1811fca2004-01-05 05:06:33 +0000229<!-- *********************************************************************** -->
230<div class="doc_section">
Chris Lattner941515c2004-01-06 05:31:32 +0000231 <a name="format">Debugging information format</a>
Chris Lattner1811fca2004-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 Wendlinge9353d72009-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 Criswell2a4b0802010-03-17 15:01:50 +0000240 particular, the use of metadata avoids duplicated debugging information from
Devang Patel80ae3492009-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 Lattner1811fca2004-01-05 05:06:33 +0000244
245<p>To do this, most of the debugging information (descriptors for types,
Bill Wendlinge9353d72009-05-17 05:52:39 +0000246 variables, functions, source files, etc) is inserted by the language
Devang Patel80ae3492009-08-28 23:24:31 +0000247 front-end in the form of LLVM metadata. </p>
Chris Lattner1811fca2004-01-05 05:06:33 +0000248
Jim Laskey14edc932006-03-14 18:08:46 +0000249<p>Debug information is designed to be agnostic about the target debugger and
Bill Wendlinge9353d72009-05-17 05:52:39 +0000250 debugging information representation (e.g. DWARF/Stabs/etc). It uses a
Devang Patel80ae3492009-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 Lattner1811fca2004-01-05 05:06:33 +0000255
Misha Brukmanf91d9942004-05-12 19:21:57 +0000256<p>To provide basic functionality, the LLVM debugger does have to make some
Bill Wendlinge9353d72009-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 Patel59445db2010-03-09 00:44:10 +0000259 exist are <a href="#format_files">source files</a>,
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000263
264<p>This section of the documentation first describes the representation aspects
Bill Wendlinge9353d72009-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 Lattner1811fca2004-01-05 05:06:33 +0000267
268</div>
269
270<!-- ======================================================================= -->
271<div class="doc_subsection">
Jim Laskey14edc932006-03-14 18:08:46 +0000272 <a name="debug_info_descriptors">Debug information descriptors</a>
Chris Lattner1811fca2004-01-05 05:06:33 +0000273</div>
274
275<div class="doc_text">
Bill Wendlinge9353d72009-05-17 05:52:39 +0000276
Jim Laskey14edc932006-03-14 18:08:46 +0000277<p>In consideration of the complexity and volume of debug information, LLVM
Devang Patel80ae3492009-08-28 23:24:31 +0000278 provides a specification for well formed debug descriptors. </p>
Chris Lattner1811fca2004-01-05 05:06:33 +0000279
Jim Laskey14edc932006-03-14 18:08:46 +0000280<p>Consumers of LLVM debug information expect the descriptors for program
Bill Wendlinge9353d72009-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 Kramer0f420382009-10-12 14:46:08 +0000288 the range 0x1000 through 0x2000 (there is a defined enum DW_TAG_user_base =
Bill Wendlinge9353d72009-05-17 05:52:39 +0000289 0x1000.)</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000290
Devang Patel80ae3492009-08-28 23:24:31 +0000291<p>The fields of debug descriptors used internally by LLVM
Nick Lewyckya87014f2010-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 Lattner1811fca2004-01-05 05:06:33 +0000294
Bill Wendlinge9353d72009-05-17 05:52:39 +0000295<div class="doc_code">
Misha Brukmanf91d9942004-05-12 19:21:57 +0000296<pre>
Devang Patel80ae3492009-08-28 23:24:31 +0000297!1 = metadata !{
Nick Lewyckya87014f2010-03-31 07:50:17 +0000298 i32, ;; A tag
Bill Wendlinge9353d72009-05-17 05:52:39 +0000299 ...
300}
Misha Brukmanf91d9942004-05-12 19:21:57 +0000301</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000302</div>
Chris Lattner1811fca2004-01-05 05:06:33 +0000303
Jim Laskeyb2ff2d42006-06-16 13:14:03 +0000304<p><a name="LLVMDebugVersion">The first field of a descriptor is always an
Nick Lewyckya87014f2010-03-31 07:50:17 +0000305 <tt>i32</tt> containing a tag value identifying the content of the
Bill Wendlinge9353d72009-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 Lewyckya87014f2010-03-31 07:50:17 +0000310 with the current debug version (LLVMDebugVersion = 8 &lt;&lt; 16 or 0x80000 or
Devang Patel59445db2010-03-09 00:44:10 +0000311 524288.)</a></p>
Jim Laskey14edc932006-03-14 18:08:46 +0000312
Jim Laskeyb2ff2d42006-06-16 13:14:03 +0000313<p>The details of the various descriptors follow.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000314
315</div>
316
317<!-- ======================================================================= -->
318<div class="doc_subsubsection">
Jim Laskey14edc932006-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 Wendlinge9353d72009-05-17 05:52:39 +0000324<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000325<pre>
Devang Patel80ae3492009-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 Wendlinge9353d72009-05-17 05:52:39 +0000338}
Jim Laskey14edc932006-03-14 18:08:46 +0000339</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000340</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000341
Bill Wendlinge9353d72009-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 Laskey14edc932006-03-14 18:08:46 +0000347
Bill Wendlinge9353d72009-05-17 05:52:39 +0000348<p>Compile unit descriptors provide the root context for objects declared in a
Devang Patel59445db2010-03-09 00:44:10 +0000349 specific compilation unit. File descriptors are defined using this context.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000350
Devang Patel59445db2010-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 Criswell2a4b0802010-03-17 15:01:50 +0000372<p>These descriptors contain information for a file. Global variables and top
Devang Patel59445db2010-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 Wendlinge9353d72009-05-17 05:52:39 +0000379
Jim Laskey14edc932006-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 Wendlinge9353d72009-05-17 05:52:39 +0000389<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000390<pre>
Devang Patel80ae3492009-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 Patel59445db2010-03-09 00:44:10 +0000399 metadata, ;; Reference to file where defined
Devang Patel80ae3492009-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 Gohmanaabfdb32010-05-28 17:13:49 +0000404 {}* ;; Reference to the global variable
Bill Wendlinge9353d72009-05-17 05:52:39 +0000405}
Jim Laskey14edc932006-03-14 18:08:46 +0000406</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000407</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000408
409<p>These descriptors provide debug information about globals variables. The
Devang Patel1c6b6812011-03-29 17:27:08 +0000410provide details such as name, type and where the variable is defined. All
411global variables are collected by named metadata <tt>!llvm.dbg.gv</tt>.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000412
413</div>
414
415<!-- ======================================================================= -->
416<div class="doc_subsubsection">
417 <a name="format_subprograms">Subprogram descriptors</a>
418</div>
419
420<div class="doc_text">
421
Bill Wendlinge9353d72009-05-17 05:52:39 +0000422<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000423<pre>
Devang Patel80ae3492009-08-28 23:24:31 +0000424!2 = metadata !{
425 i32, ;; Tag = 46 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
426 ;; (DW_TAG_subprogram)
427 i32, ;; Unused field.
428 metadata, ;; Reference to context descriptor
429 metadata, ;; Name
430 metadata, ;; Display name (fully qualified C++ name)
431 metadata, ;; MIPS linkage name (for C++)
Devang Patel59445db2010-03-09 00:44:10 +0000432 metadata, ;; Reference to file where defined
Devang Patel80ae3492009-08-28 23:24:31 +0000433 i32, ;; Line number where defined
434 metadata, ;; Reference to type descriptor
435 i1, ;; True if the global is local to compile unit (static)
436 i1 ;; True if the global is defined in the compile unit (not extern)
Devang Patele89b7592010-06-04 22:49:55 +0000437 i32 ;; Virtuality, e.g. dwarf::DW_VIRTUALITY__virtual
438 i32 ;; Index into a virtual function
439 metadata, ;; indicates which base type contains the vtable pointer for the
440 ;; derived class
441 i1 ;; isArtificial
442 i1 ;; isOptimized
443 Function *;; Pointer to LLVM function
Devang Patel9f738842011-04-05 22:52:06 +0000444 metadata ;; Lists function template parameters
Bill Wendlinge9353d72009-05-17 05:52:39 +0000445}
Jim Laskey14edc932006-03-14 18:08:46 +0000446</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000447</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000448
449<p>These descriptors provide debug information about functions, methods and
Bill Wendlinge9353d72009-05-17 05:52:39 +0000450 subprograms. They provide details such as name, return types and the source
Devang Patel1c6b6812011-03-29 17:27:08 +0000451 location where the subprogram is defined.
452 All subprogram descriptors are collected by a named metadata
453 <tt>!llvm.dbg.sp</tt>.
454</p>
Jim Laskey9dcffe72006-03-15 19:10:52 +0000455
456</div>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000457
Jim Laskey9dcffe72006-03-15 19:10:52 +0000458<!-- ======================================================================= -->
459<div class="doc_subsubsection">
460 <a name="format_blocks">Block descriptors</a>
461</div>
462
463<div class="doc_text">
464
Bill Wendlinge9353d72009-05-17 05:52:39 +0000465<div class="doc_code">
Jim Laskey9dcffe72006-03-15 19:10:52 +0000466<pre>
Devang Patel80ae3492009-08-28 23:24:31 +0000467!3 = metadata !{
Devang Patel9fbc6802010-10-04 16:51:59 +0000468 i32, ;; Tag = 11 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_lexical_block)
Devang Patelcac38902010-10-01 22:45:00 +0000469 metadata,;; Reference to context descriptor
470 i32, ;; Line number
Devang Patelfb30b852011-03-08 16:25:29 +0000471 i32, ;; Column number
472 metadata,;; Reference to source file
473 i32 ;; Unique ID to identify blocks from a template function
Bill Wendlinge9353d72009-05-17 05:52:39 +0000474}
Jim Laskey9dcffe72006-03-15 19:10:52 +0000475</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000476</div>
Jim Laskey9dcffe72006-03-15 19:10:52 +0000477
478<p>These descriptors provide debug information about nested blocks within a
Devang Patelcac38902010-10-01 22:45:00 +0000479 subprogram. The line number and column numbers are used to dinstinguish
480 two lexical blocks at same depth. </p>
Jim Laskey9dcffe72006-03-15 19:10:52 +0000481
Jim Laskey14edc932006-03-14 18:08:46 +0000482</div>
483
484<!-- ======================================================================= -->
485<div class="doc_subsubsection">
486 <a name="format_basic_type">Basic type descriptors</a>
487</div>
488
489<div class="doc_text">
490
Bill Wendlinge9353d72009-05-17 05:52:39 +0000491<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000492<pre>
Devang Patel80ae3492009-08-28 23:24:31 +0000493!4 = metadata !{
494 i32, ;; Tag = 36 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
495 ;; (DW_TAG_base_type)
496 metadata, ;; Reference to context (typically a compile unit)
497 metadata, ;; Name (may be "" for anonymous types)
Devang Patel59445db2010-03-09 00:44:10 +0000498 metadata, ;; Reference to file where defined (may be NULL)
Devang Patel80ae3492009-08-28 23:24:31 +0000499 i32, ;; Line number where defined (may be 0)
500 i64, ;; Size in bits
501 i64, ;; Alignment in bits
502 i64, ;; Offset in bits
503 i32, ;; Flags
504 i32 ;; DWARF type encoding
Bill Wendlinge9353d72009-05-17 05:52:39 +0000505}
Jim Laskey14edc932006-03-14 18:08:46 +0000506</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000507</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000508
509<p>These descriptors define primitive types used in the code. Example int, bool
Bill Wendlinge9353d72009-05-17 05:52:39 +0000510 and float. The context provides the scope of the type, which is usually the
511 top level. Since basic types are not usually user defined the compile unit
512 and line number can be left as NULL and 0. The size, alignment and offset
513 are expressed in bits and can be 64 bit values. The alignment is used to
514 round the offset when embedded in a
515 <a href="#format_composite_type">composite type</a> (example to keep float
516 doubles on 64 bit boundaries.) The offset is the bit offset if embedded in
517 a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000518
519<p>The type encoding provides the details of the type. The values are typically
Bill Wendlinge9353d72009-05-17 05:52:39 +0000520 one of the following:</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000521
Bill Wendlinge9353d72009-05-17 05:52:39 +0000522<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000523<pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000524DW_ATE_address = 1
525DW_ATE_boolean = 2
526DW_ATE_float = 4
527DW_ATE_signed = 5
528DW_ATE_signed_char = 6
529DW_ATE_unsigned = 7
530DW_ATE_unsigned_char = 8
Jim Laskey14edc932006-03-14 18:08:46 +0000531</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000532</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000533
534</div>
535
536<!-- ======================================================================= -->
537<div class="doc_subsubsection">
538 <a name="format_derived_type">Derived type descriptors</a>
539</div>
540
541<div class="doc_text">
542
Bill Wendlinge9353d72009-05-17 05:52:39 +0000543<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000544<pre>
Devang Patel80ae3492009-08-28 23:24:31 +0000545!5 = metadata !{
546 i32, ;; Tag (see below)
547 metadata, ;; Reference to context
548 metadata, ;; Name (may be "" for anonymous types)
Devang Patel59445db2010-03-09 00:44:10 +0000549 metadata, ;; Reference to file where defined (may be NULL)
Devang Patel80ae3492009-08-28 23:24:31 +0000550 i32, ;; Line number where defined (may be 0)
Devang Patelbed5e7d2010-10-01 19:19:30 +0000551 i64, ;; Size in bits
552 i64, ;; Alignment in bits
553 i64, ;; Offset in bits
Devang Patel80ae3492009-08-28 23:24:31 +0000554 metadata ;; Reference to type derived from
Bill Wendlinge9353d72009-05-17 05:52:39 +0000555}
Jim Laskey14edc932006-03-14 18:08:46 +0000556</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000557</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000558
559<p>These descriptors are used to define types derived from other types. The
560value of the tag varies depending on the meaning. The following are possible
Misha Brukman39dcddf2008-12-16 02:54:22 +0000561tag values:</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000562
Bill Wendlinge9353d72009-05-17 05:52:39 +0000563<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000564<pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000565DW_TAG_formal_parameter = 5
566DW_TAG_member = 13
567DW_TAG_pointer_type = 15
568DW_TAG_reference_type = 16
569DW_TAG_typedef = 22
570DW_TAG_const_type = 38
571DW_TAG_volatile_type = 53
572DW_TAG_restrict_type = 55
Jim Laskey14edc932006-03-14 18:08:46 +0000573</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000574</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000575
Bill Wendlinge9353d72009-05-17 05:52:39 +0000576<p><tt>DW_TAG_member</tt> is used to define a member of
577 a <a href="#format_composite_type">composite type</a>
578 or <a href="#format_subprograms">subprogram</a>. The type of the member is
579 the <a href="#format_derived_type">derived
580 type</a>. <tt>DW_TAG_formal_parameter</tt> is used to define a member which
581 is a formal argument of a subprogram.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000582
Bill Wendlinge9353d72009-05-17 05:52:39 +0000583<p><tt>DW_TAG_typedef</tt> is used to provide a name for the derived type.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000584
Bill Wendlinge9353d72009-05-17 05:52:39 +0000585<p><tt>DW_TAG_pointer_type</tt>,<tt>DW_TAG_reference_type</tt>,
586 <tt>DW_TAG_const_type</tt>, <tt>DW_TAG_volatile_type</tt>
587 and <tt>DW_TAG_restrict_type</tt> are used to qualify
588 the <a href="#format_derived_type">derived type</a>. </p>
Jim Laskey14edc932006-03-14 18:08:46 +0000589
590<p><a href="#format_derived_type">Derived type</a> location can be determined
Bill Wendlinge9353d72009-05-17 05:52:39 +0000591 from the compile unit and line number. The size, alignment and offset are
592 expressed in bits and can be 64 bit values. The alignment is used to round
593 the offset when embedded in a <a href="#format_composite_type">composite
594 type</a> (example to keep float doubles on 64 bit boundaries.) The offset is
595 the bit offset if embedded in a <a href="#format_composite_type">composite
596 type</a>.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000597
Devang Patel7846c1e2011-02-03 00:22:17 +0000598<p>Note that the <tt>void *</tt> type is expressed as a type derived from NULL.
599</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000600
601</div>
602
603<!-- ======================================================================= -->
604<div class="doc_subsubsection">
605 <a name="format_composite_type">Composite type descriptors</a>
606</div>
607
608<div class="doc_text">
609
Bill Wendlinge9353d72009-05-17 05:52:39 +0000610<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000611<pre>
Devang Patel80ae3492009-08-28 23:24:31 +0000612!6 = metadata !{
613 i32, ;; Tag (see below)
614 metadata, ;; Reference to context
615 metadata, ;; Name (may be "" for anonymous types)
Devang Patel59445db2010-03-09 00:44:10 +0000616 metadata, ;; Reference to file where defined (may be NULL)
Devang Patel80ae3492009-08-28 23:24:31 +0000617 i32, ;; Line number where defined (may be 0)
618 i64, ;; Size in bits
619 i64, ;; Alignment in bits
620 i64, ;; Offset in bits
621 i32, ;; Flags
622 metadata, ;; Reference to type derived from
623 metadata, ;; Reference to array of member descriptors
624 i32 ;; Runtime languages
Bill Wendlinge9353d72009-05-17 05:52:39 +0000625}
Jim Laskey14edc932006-03-14 18:08:46 +0000626</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000627</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000628
629<p>These descriptors are used to define types that are composed of 0 or more
630elements. The value of the tag varies depending on the meaning. The following
Misha Brukman39dcddf2008-12-16 02:54:22 +0000631are possible tag values:</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000632
Bill Wendlinge9353d72009-05-17 05:52:39 +0000633<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000634<pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000635DW_TAG_array_type = 1
636DW_TAG_enumeration_type = 4
637DW_TAG_structure_type = 19
638DW_TAG_union_type = 23
639DW_TAG_vector_type = 259
Bruno Cardoso Lopes9d809ca2009-05-29 17:08:57 +0000640DW_TAG_subroutine_type = 21
641DW_TAG_inheritance = 28
Jim Laskey14edc932006-03-14 18:08:46 +0000642</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000643</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000644
Jim Laskey19f964e2006-06-15 20:51:43 +0000645<p>The vector flag indicates that an array type is a native packed vector.</p>
646
Jim Laskeyb2ff2d42006-06-16 13:14:03 +0000647<p>The members of array types (tag = <tt>DW_TAG_array_type</tt>) or vector types
Bill Wendlinge9353d72009-05-17 05:52:39 +0000648 (tag = <tt>DW_TAG_vector_type</tt>) are <a href="#format_subrange">subrange
649 descriptors</a>, each representing the range of subscripts at that level of
650 indexing.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000651
652<p>The members of enumeration types (tag = <tt>DW_TAG_enumeration_type</tt>) are
Bill Wendlinge9353d72009-05-17 05:52:39 +0000653 <a href="#format_enumeration">enumerator descriptors</a>, each representing
Devang Patel1c6b6812011-03-29 17:27:08 +0000654 the definition of enumeration value for the set. All enumeration type
655 descriptors are collected by named metadata <tt>!llvm.dbg.enum</tt>.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000656
657<p>The members of structure (tag = <tt>DW_TAG_structure_type</tt>) or union (tag
Bill Wendlinge9353d72009-05-17 05:52:39 +0000658 = <tt>DW_TAG_union_type</tt>) types are any one of
659 the <a href="#format_basic_type">basic</a>,
660 <a href="#format_derived_type">derived</a>
661 or <a href="#format_composite_type">composite</a> type descriptors, each
662 representing a field member of the structure or union.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000663
Jim Laskey4771cca2006-08-21 21:21:06 +0000664<p>For C++ classes (tag = <tt>DW_TAG_structure_type</tt>), member descriptors
Bill Wendlinge9353d72009-05-17 05:52:39 +0000665 provide information about base classes, static members and member
666 functions. If a member is a <a href="#format_derived_type">derived type
667 descriptor</a> and has a tag of <tt>DW_TAG_inheritance</tt>, then the type
668 represents a base class. If the member of is
669 a <a href="#format_global_variables">global variable descriptor</a> then it
670 represents a static member. And, if the member is
671 a <a href="#format_subprograms">subprogram descriptor</a> then it represents
672 a member function. For static members and member
673 functions, <tt>getName()</tt> returns the members link or the C++ mangled
674 name. <tt>getDisplayName()</tt> the simplied version of the name.</p>
Jim Laskey4771cca2006-08-21 21:21:06 +0000675
Bill Wendlinge9353d72009-05-17 05:52:39 +0000676<p>The first member of subroutine (tag = <tt>DW_TAG_subroutine_type</tt>) type
677 elements is the return type for the subroutine. The remaining elements are
678 the formal arguments to the subroutine.</p>
Jim Laskey4810c262006-06-20 21:13:20 +0000679
Jim Laskey14edc932006-03-14 18:08:46 +0000680<p><a href="#format_composite_type">Composite type</a> location can be
Bill Wendlinge9353d72009-05-17 05:52:39 +0000681 determined from the compile unit and line number. The size, alignment and
682 offset are expressed in bits and can be 64 bit values. The alignment is used
683 to round the offset when embedded in
684 a <a href="#format_composite_type">composite type</a> (as an example, to keep
685 float doubles on 64 bit boundaries.) The offset is the bit offset if embedded
686 in a <a href="#format_composite_type">composite type</a>.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000687
688</div>
689
690<!-- ======================================================================= -->
691<div class="doc_subsubsection">
692 <a name="format_subrange">Subrange descriptors</a>
693</div>
694
695<div class="doc_text">
696
Bill Wendlinge9353d72009-05-17 05:52:39 +0000697<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000698<pre>
Devang Patel7846c1e2011-02-03 00:22:17 +0000699!42 = metadata !{
Bill Wendlinge9353d72009-05-17 05:52:39 +0000700 i32, ;; Tag = 33 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a> (DW_TAG_subrange_type)
701 i64, ;; Low value
702 i64 ;; High value
703}
Jim Laskey14edc932006-03-14 18:08:46 +0000704</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000705</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000706
707<p>These descriptors are used to define ranges of array subscripts for an array
Bill Wendlinge9353d72009-05-17 05:52:39 +0000708 <a href="#format_composite_type">composite type</a>. The low value defines
709 the lower bounds typically zero for C/C++. The high value is the upper
710 bounds. Values are 64 bit. High - low + 1 is the size of the array. If low
Devang Patel778947c2011-04-08 23:39:38 +0000711 > high the array bounds are not included in generated debugging information.
712</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000713
714</div>
715
716<!-- ======================================================================= -->
717<div class="doc_subsubsection">
718 <a name="format_enumeration">Enumerator descriptors</a>
719</div>
720
721<div class="doc_text">
722
Bill Wendlinge9353d72009-05-17 05:52:39 +0000723<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +0000724<pre>
Devang Patel80ae3492009-08-28 23:24:31 +0000725!6 = metadata !{
726 i32, ;; Tag = 40 + <a href="#LLVMDebugVersion">LLVMDebugVersion</a>
727 ;; (DW_TAG_enumerator)
728 metadata, ;; Name
729 i64 ;; Value
Bill Wendlinge9353d72009-05-17 05:52:39 +0000730}
Jim Laskey14edc932006-03-14 18:08:46 +0000731</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000732</div>
Jim Laskey14edc932006-03-14 18:08:46 +0000733
Bill Wendlinge9353d72009-05-17 05:52:39 +0000734<p>These descriptors are used to define members of an
735 enumeration <a href="#format_composite_type">composite type</a>, it
736 associates the name to the value.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000737
738</div>
739
740<!-- ======================================================================= -->
Jim Laskey5dcfd562006-03-23 17:54:33 +0000741<div class="doc_subsubsection">
742 <a name="format_variables">Local variables</a>
743</div>
744
745<div class="doc_text">
Bill Wendlinge9353d72009-05-17 05:52:39 +0000746
747<div class="doc_code">
Jim Laskey5dcfd562006-03-23 17:54:33 +0000748<pre>
Devang Patel80ae3492009-08-28 23:24:31 +0000749!7 = metadata !{
750 i32, ;; Tag (see below)
751 metadata, ;; Context
752 metadata, ;; Name
Devang Patel59445db2010-03-09 00:44:10 +0000753 metadata, ;; Reference to file where defined
Devang Patele1aa67c2011-03-08 16:29:40 +0000754 i32, ;; 24 bit - Line number where defined
755 ;; 8 bit - Argument number. 1 indicates 1st argument.
Devang Patel80ae3492009-08-28 23:24:31 +0000756 metadata ;; Type descriptor
Bill Wendlinge9353d72009-05-17 05:52:39 +0000757}
Jim Laskey5dcfd562006-03-23 17:54:33 +0000758</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000759</div>
Jim Laskey5dcfd562006-03-23 17:54:33 +0000760
761<p>These descriptors are used to define variables local to a sub program. The
Bill Wendlinge9353d72009-05-17 05:52:39 +0000762 value of the tag depends on the usage of the variable:</p>
Jim Laskey5dcfd562006-03-23 17:54:33 +0000763
Bill Wendlinge9353d72009-05-17 05:52:39 +0000764<div class="doc_code">
Jim Laskey5dcfd562006-03-23 17:54:33 +0000765<pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000766DW_TAG_auto_variable = 256
767DW_TAG_arg_variable = 257
768DW_TAG_return_variable = 258
Jim Laskey5dcfd562006-03-23 17:54:33 +0000769</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000770</div>
Jim Laskey5dcfd562006-03-23 17:54:33 +0000771
772<p>An auto variable is any variable declared in the body of the function. An
Bill Wendlinge9353d72009-05-17 05:52:39 +0000773 argument variable is any variable that appears as a formal argument to the
774 function. A return variable is used to track the result of a function and
775 has no source correspondent.</p>
Jim Laskey5dcfd562006-03-23 17:54:33 +0000776
Jim Laskey3481e122006-03-24 09:20:27 +0000777<p>The context is either the subprogram or block where the variable is defined.
Bill Wendlinge9353d72009-05-17 05:52:39 +0000778 Name the source variable name. Compile unit and line indicate where the
779 variable was defined. Type descriptor defines the declared type of the
780 variable.</p>
Jim Laskey5dcfd562006-03-23 17:54:33 +0000781
782</div>
783
784<!-- ======================================================================= -->
Chris Lattner1811fca2004-01-05 05:06:33 +0000785<div class="doc_subsection">
Jim Laskey14edc932006-03-14 18:08:46 +0000786 <a name="format_common_intrinsics">Debugger intrinsic functions</a>
787</div>
788
789<div class="doc_text">
790
791<p>LLVM uses several intrinsic functions (name prefixed with "llvm.dbg") to
Bill Wendlinge9353d72009-05-17 05:52:39 +0000792 provide debug information at various points in generated code.</p>
Jim Laskey14edc932006-03-14 18:08:46 +0000793
794</div>
795
796<!-- ======================================================================= -->
797<div class="doc_subsubsection">
Jim Laskey14edc932006-03-14 18:08:46 +0000798 <a name="format_common_declare">llvm.dbg.declare</a>
799</div>
800
801<div class="doc_text">
802<pre>
Devang Patel6df452c2010-10-01 19:22:16 +0000803 void %<a href="#format_common_declare">llvm.dbg.declare</a>(metadata, metadata)
Jim Laskey14edc932006-03-14 18:08:46 +0000804</pre>
805
Jim Laskey3481e122006-03-24 09:20:27 +0000806<p>This intrinsic provides information about a local element (ex. variable.) The
Devang Patel6df452c2010-10-01 19:22:16 +0000807 first argument is metadata holding alloca for the variable.</tt>. The
Devang Patel9a8539c2011-02-01 17:22:12 +0000808 second argument is metadata containing description of the variable. </p>
Jim Laskey14edc932006-03-14 18:08:46 +0000809</div>
810
811<!-- ======================================================================= -->
Victor Hernandez0b62cc62010-01-11 22:53:48 +0000812<div class="doc_subsubsection">
813 <a name="format_common_value">llvm.dbg.value</a>
814</div>
815
816<div class="doc_text">
817<pre>
Dan Gohmand6a6f612010-05-28 17:07:41 +0000818 void %<a href="#format_common_value">llvm.dbg.value</a>(metadata, i64, metadata)
Victor Hernandez0b62cc62010-01-11 22:53:48 +0000819</pre>
820
821<p>This intrinsic provides information when a user source variable is set to a
822 new value. The first argument is the new value (wrapped as metadata). The
823 second argument is the offset in the user source variable where the new value
Devang Patel9a8539c2011-02-01 17:22:12 +0000824 is written. The third argument is metadata containing description of the
825 user source variable. </p>
Victor Hernandez0b62cc62010-01-11 22:53:48 +0000826</div>
827
828<!-- ======================================================================= -->
Jim Laskey14edc932006-03-14 18:08:46 +0000829<div class="doc_subsection">
Chris Lattner941515c2004-01-06 05:31:32 +0000830 <a name="format_common_lifetime">Object lifetimes and scoping</a>
Chris Lattner1811fca2004-01-05 05:06:33 +0000831</div>
832
833<div class="doc_text">
Bill Wendling991b84e2009-12-01 00:53:11 +0000834<p>In many languages, the local variables in functions can have their lifetimes
835 or scopes limited to a subset of a function. In the C family of languages,
Bill Wendlinge9353d72009-05-17 05:52:39 +0000836 for example, variables are only live (readable and writable) within the
837 source block that they are defined in. In functional languages, values are
838 only readable after they have been defined. Though this is a very obvious
Bill Wendling991b84e2009-12-01 00:53:11 +0000839 concept, it is non-trivial to model in LLVM, because it has no notion of
Bill Wendlinge9353d72009-05-17 05:52:39 +0000840 scoping in this sense, and does not want to be tied to a language's scoping
841 rules.</p>
Chris Lattner1811fca2004-01-05 05:06:33 +0000842
Bill Wendling991b84e2009-12-01 00:53:11 +0000843<p>In order to handle this, the LLVM debug format uses the metadata attached to
Nick Lewyckya87014f2010-03-31 07:50:17 +0000844 llvm instructions to encode line number and scoping information. Consider
845 the following C fragment, for example:</p>
Chris Lattner1811fca2004-01-05 05:06:33 +0000846
Bill Wendlinge9353d72009-05-17 05:52:39 +0000847<div class="doc_code">
Misha Brukmanf91d9942004-05-12 19:21:57 +0000848<pre>
Chris Lattner1811fca2004-01-05 05:06:33 +00008491. void foo() {
Devang Patel4da997b2009-11-25 23:28:01 +00008502. int X = 21;
8513. int Y = 22;
Chris Lattner1811fca2004-01-05 05:06:33 +00008524. {
Devang Patel4da997b2009-11-25 23:28:01 +00008535. int Z = 23;
8546. Z = X;
Chris Lattner1811fca2004-01-05 05:06:33 +00008557. }
Devang Patel4da997b2009-11-25 23:28:01 +00008568. X = Y;
Chris Lattner1811fca2004-01-05 05:06:33 +00008579. }
Misha Brukmanf91d9942004-05-12 19:21:57 +0000858</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000859</div>
Chris Lattner1811fca2004-01-05 05:06:33 +0000860
Jim Laskey14edc932006-03-14 18:08:46 +0000861<p>Compiled to LLVM, this function would be represented like this:</p>
Chris Lattner1811fca2004-01-05 05:06:33 +0000862
Bill Wendlinge9353d72009-05-17 05:52:39 +0000863<div class="doc_code">
Misha Brukmanf91d9942004-05-12 19:21:57 +0000864<pre>
Bill Wendling991b84e2009-12-01 00:53:11 +0000865define void @foo() nounwind ssp {
Jim Laskey14edc932006-03-14 18:08:46 +0000866entry:
Bill Wendling05252352009-12-01 00:59:58 +0000867 %X = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
868 %Y = alloca i32, align 4 ; &lt;i32*&gt; [#uses=4]
869 %Z = alloca i32, align 4 ; &lt;i32*&gt; [#uses=3]
Dan Gohmanaabfdb32010-05-28 17:13:49 +0000870 %0 = bitcast i32* %X to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel7846c1e2011-02-03 00:22:17 +0000871 call void @llvm.dbg.declare(metadata !{i32 * %X}, metadata !0), !dbg !7
Devang Patel4da997b2009-11-25 23:28:01 +0000872 store i32 21, i32* %X, !dbg !8
Dan Gohmanaabfdb32010-05-28 17:13:49 +0000873 %1 = bitcast i32* %Y to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel7846c1e2011-02-03 00:22:17 +0000874 call void @llvm.dbg.declare(metadata !{i32 * %Y}, metadata !9), !dbg !10
Devang Patel4da997b2009-11-25 23:28:01 +0000875 store i32 22, i32* %Y, !dbg !11
Dan Gohmanaabfdb32010-05-28 17:13:49 +0000876 %2 = bitcast i32* %Z to {}* ; &lt;{}*&gt; [#uses=1]
Devang Patel7846c1e2011-02-03 00:22:17 +0000877 call void @llvm.dbg.declare(metadata !{i32 * %Z}, metadata !12), !dbg !14
Devang Patel4da997b2009-11-25 23:28:01 +0000878 store i32 23, i32* %Z, !dbg !15
Bill Wendling05252352009-12-01 00:59:58 +0000879 %tmp = load i32* %X, !dbg !16 ; &lt;i32&gt; [#uses=1]
880 %tmp1 = load i32* %Y, !dbg !16 ; &lt;i32&gt; [#uses=1]
881 %add = add nsw i32 %tmp, %tmp1, !dbg !16 ; &lt;i32&gt; [#uses=1]
Devang Patel4da997b2009-11-25 23:28:01 +0000882 store i32 %add, i32* %Z, !dbg !16
Bill Wendling05252352009-12-01 00:59:58 +0000883 %tmp2 = load i32* %Y, !dbg !17 ; &lt;i32&gt; [#uses=1]
Devang Patel4da997b2009-11-25 23:28:01 +0000884 store i32 %tmp2, i32* %X, !dbg !17
885 ret void, !dbg !18
Chris Lattner1811fca2004-01-05 05:06:33 +0000886}
Devang Patel4da997b2009-11-25 23:28:01 +0000887
Devang Patel7846c1e2011-02-03 00:22:17 +0000888declare void @llvm.dbg.declare(metadata, metadata) nounwind readnone
Devang Patel4da997b2009-11-25 23:28:01 +0000889
890!0 = metadata !{i32 459008, metadata !1, metadata !"X",
891 metadata !3, i32 2, metadata !6}; [ DW_TAG_auto_variable ]
892!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
893!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo", metadata !"foo",
894 metadata !"foo", metadata !3, i32 1, metadata !4,
895 i1 false, i1 true}; [DW_TAG_subprogram ]
896!3 = metadata !{i32 458769, i32 0, i32 12, metadata !"foo.c",
897 metadata !"/private/tmp", metadata !"clang 1.1", i1 true,
898 i1 false, metadata !"", i32 0}; [DW_TAG_compile_unit ]
899!4 = metadata !{i32 458773, metadata !3, metadata !"", null, i32 0, i64 0, i64 0,
900 i64 0, i32 0, null, metadata !5, i32 0}; [DW_TAG_subroutine_type ]
901!5 = metadata !{null}
902!6 = metadata !{i32 458788, metadata !3, metadata !"int", metadata !3, i32 0,
903 i64 32, i64 32, i64 0, i32 0, i32 5}; [DW_TAG_base_type ]
904!7 = metadata !{i32 2, i32 7, metadata !1, null}
905!8 = metadata !{i32 2, i32 3, metadata !1, null}
906!9 = metadata !{i32 459008, metadata !1, metadata !"Y", metadata !3, i32 3,
907 metadata !6}; [ DW_TAG_auto_variable ]
908!10 = metadata !{i32 3, i32 7, metadata !1, null}
909!11 = metadata !{i32 3, i32 3, metadata !1, null}
910!12 = metadata !{i32 459008, metadata !13, metadata !"Z", metadata !3, i32 5,
911 metadata !6}; [ DW_TAG_auto_variable ]
912!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
913!14 = metadata !{i32 5, i32 9, metadata !13, null}
914!15 = metadata !{i32 5, i32 5, metadata !13, null}
915!16 = metadata !{i32 6, i32 5, metadata !13, null}
916!17 = metadata !{i32 8, i32 3, metadata !1, null}
917!18 = metadata !{i32 9, i32 1, metadata !2, null}
Misha Brukmanf91d9942004-05-12 19:21:57 +0000918</pre>
Chris Lattner1811fca2004-01-05 05:06:33 +0000919</div>
920
Bill Wendling991b84e2009-12-01 00:53:11 +0000921<p>This example illustrates a few important details about LLVM debugging
922 information. In particular, it shows how the <tt>llvm.dbg.declare</tt>
923 intrinsic and location information, which are attached to an instruction,
924 are applied together to allow a debugger to analyze the relationship between
925 statements, variable definitions, and the code used to implement the
926 function.</p>
Chris Lattner1811fca2004-01-05 05:06:33 +0000927
Bill Wendling991b84e2009-12-01 00:53:11 +0000928<div class="doc_code">
Bill Wendling05252352009-12-01 00:59:58 +0000929<pre>
Devang Patel7846c1e2011-02-03 00:22:17 +0000930call void @llvm.dbg.declare(metadata, metadata !0), !dbg !7
Bill Wendling991b84e2009-12-01 00:53:11 +0000931</pre>
932</div>
933
934<p>The first intrinsic
Devang Patel4da997b2009-11-25 23:28:01 +0000935 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendling991b84e2009-12-01 00:53:11 +0000936 encodes debugging information for the variable <tt>X</tt>. The metadata
937 <tt>!dbg !7</tt> attached to the intrinsic provides scope information for the
938 variable <tt>X</tt>.</p>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000939
Bill Wendling991b84e2009-12-01 00:53:11 +0000940<div class="doc_code">
941<pre>
942!7 = metadata !{i32 2, i32 7, metadata !1, null}
943!1 = metadata !{i32 458763, metadata !2}; [DW_TAG_lexical_block ]
944!2 = metadata !{i32 458798, i32 0, metadata !3, metadata !"foo",
945 metadata !"foo", metadata !"foo", metadata !3, i32 1,
946 metadata !4, i1 false, i1 true}; [DW_TAG_subprogram ]
947</pre>
948</div>
949
950<p>Here <tt>!7</tt> is metadata providing location information. It has four
951 fields: line number, column number, scope, and original scope. The original
952 scope represents inline location if this instruction is inlined inside a
953 caller, and is null otherwise. In this example, scope is encoded by
Devang Patel4da997b2009-11-25 23:28:01 +0000954 <tt>!1</tt>. <tt>!1</tt> represents a lexical block inside the scope
955 <tt>!2</tt>, where <tt>!2</tt> is a
Bill Wendling991b84e2009-12-01 00:53:11 +0000956 <a href="#format_subprograms">subprogram descriptor</a>. This way the
957 location information attached to the intrinsics indicates that the
958 variable <tt>X</tt> is declared at line number 2 at a function level scope in
959 function <tt>foo</tt>.</p>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000960
Devang Patel4da997b2009-11-25 23:28:01 +0000961<p>Now lets take another example.</p>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000962
Bill Wendling991b84e2009-12-01 00:53:11 +0000963<div class="doc_code">
Bill Wendling05252352009-12-01 00:59:58 +0000964<pre>
Devang Patel7846c1e2011-02-03 00:22:17 +0000965call void @llvm.dbg.declare(metadata, metadata !12), !dbg !14
Bill Wendling991b84e2009-12-01 00:53:11 +0000966</pre>
967</div>
968
969<p>The second intrinsic
Devang Patel4da997b2009-11-25 23:28:01 +0000970 <tt>%<a href="#format_common_declare">llvm.dbg.declare</a></tt>
Bill Wendling991b84e2009-12-01 00:53:11 +0000971 encodes debugging information for variable <tt>Z</tt>. The metadata
972 <tt>!dbg !14</tt> attached to the intrinsic provides scope information for
973 the variable <tt>Z</tt>.</p>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000974
Bill Wendling991b84e2009-12-01 00:53:11 +0000975<div class="doc_code">
976<pre>
977!13 = metadata !{i32 458763, metadata !1}; [DW_TAG_lexical_block ]
978!14 = metadata !{i32 5, i32 9, metadata !13, null}
979</pre>
980</div>
Bill Wendlinge9353d72009-05-17 05:52:39 +0000981
John Criswell2a4b0802010-03-17 15:01:50 +0000982<p>Here <tt>!14</tt> indicates that <tt>Z</tt> is declared at line number 5 and
Bill Wendling991b84e2009-12-01 00:53:11 +0000983 column number 9 inside of lexical scope <tt>!13</tt>. The lexical scope
984 itself resides inside of lexical scope <tt>!1</tt> described above.</p>
985
986<p>The scope information attached with each instruction provides a
987 straightforward way to find instructions covered by a scope.</p>
988
Bill Wendlinge9353d72009-05-17 05:52:39 +0000989</div>
Chris Lattner1811fca2004-01-05 05:06:33 +0000990
991<!-- *********************************************************************** -->
992<div class="doc_section">
Chris Lattner941515c2004-01-06 05:31:32 +0000993 <a name="ccxx_frontend">C/C++ front-end specific debug information</a>
Chris Lattner1811fca2004-01-05 05:06:33 +0000994</div>
Misha Brukmancda6a9b2004-12-09 20:27:37 +0000995<!-- *********************************************************************** -->
Chris Lattner1811fca2004-01-05 05:06:33 +0000996
997<div class="doc_text">
998
Misha Brukmanf91d9942004-05-12 19:21:57 +0000999<p>The C and C++ front-ends represent information about the program in a format
Bill Wendlinge9353d72009-05-17 05:52:39 +00001000 that is effectively identical
1001 to <a href="http://www.eagercon.com/dwarf/dwarf3std.htm">DWARF 3.0</a> in
1002 terms of information content. This allows code generators to trivially
1003 support native debuggers by generating standard dwarf information, and
1004 contains enough information for non-dwarf targets to translate it as
1005 needed.</p>
Chris Lattner1811fca2004-01-05 05:06:33 +00001006
Jim Laskey14edc932006-03-14 18:08:46 +00001007<p>This section describes the forms used to represent C and C++ programs. Other
Bill Wendlinge9353d72009-05-17 05:52:39 +00001008 languages could pattern themselves after this (which itself is tuned to
1009 representing programs in the same way that DWARF 3 does), or they could
1010 choose to provide completely different forms if they don't fit into the DWARF
1011 model. As support for debugging information gets added to the various LLVM
1012 source-language front-ends, the information used should be documented
1013 here.</p>
Chris Lattner1811fca2004-01-05 05:06:33 +00001014
Jim Laskey14edc932006-03-14 18:08:46 +00001015<p>The following sections provide examples of various C/C++ constructs and the
Bill Wendlinge9353d72009-05-17 05:52:39 +00001016 debug information that would best describe those constructs.</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001017
Chris Lattner1811fca2004-01-05 05:06:33 +00001018</div>
1019
1020<!-- ======================================================================= -->
1021<div class="doc_subsection">
Jim Laskey14edc932006-03-14 18:08:46 +00001022 <a name="ccxx_compile_units">C/C++ source file information</a>
Chris Lattner1811fca2004-01-05 05:06:33 +00001023</div>
1024
1025<div class="doc_text">
Chris Lattner1811fca2004-01-05 05:06:33 +00001026
Bill Wendlinge9353d72009-05-17 05:52:39 +00001027<p>Given the source files <tt>MySource.cpp</tt> and <tt>MyHeader.h</tt> located
1028 in the directory <tt>/Users/mine/sources</tt>, the following code:</p>
Chris Lattner941515c2004-01-06 05:31:32 +00001029
Bill Wendlinge9353d72009-05-17 05:52:39 +00001030<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001031<pre>
1032#include "MyHeader.h"
Chris Lattner941515c2004-01-06 05:31:32 +00001033
Jim Laskey14edc932006-03-14 18:08:46 +00001034int main(int argc, char *argv[]) {
1035 return 0;
1036}
1037</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001038</div>
Chris Lattner941515c2004-01-06 05:31:32 +00001039
Misha Brukman39dcddf2008-12-16 02:54:22 +00001040<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001041
Bill Wendlinge9353d72009-05-17 05:52:39 +00001042<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001043<pre>
1044...
1045;;
Devang Patel59445db2010-03-09 00:44:10 +00001046;; Define the compile unit for the main source file "/Users/mine/sources/MySource.cpp".
Jim Laskey14edc932006-03-14 18:08:46 +00001047;;
Devang Patel59445db2010-03-09 00:44:10 +00001048!2 = metadata !{
1049 i32 524305, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001050 i32 0, ;; Unused
1051 i32 4, ;; Language Id
1052 metadata !"MySource.cpp",
1053 metadata !"/Users/mine/sources",
1054 metadata !"4.2.1 (Based on Apple Inc. build 5649) (LLVM build 00)",
1055 i1 true, ;; Main Compile Unit
1056 i1 false, ;; Optimized compile unit
1057 metadata !"", ;; Compiler flags
1058 i32 0} ;; Runtime version
1059
Jim Laskey14edc932006-03-14 18:08:46 +00001060;;
Devang Patel59445db2010-03-09 00:44:10 +00001061;; Define the file for the file "/Users/mine/sources/MySource.cpp".
Jim Laskey14edc932006-03-14 18:08:46 +00001062;;
Devang Patel80ae3492009-08-28 23:24:31 +00001063!1 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001064 i32 524329, ;; Tag
1065 metadata !"MySource.cpp",
Devang Patel80ae3492009-08-28 23:24:31 +00001066 metadata !"/Users/mine/sources",
Devang Patel4a7904d62010-07-13 16:53:20 +00001067 metadata !2 ;; Compile unit
Devang Patel59445db2010-03-09 00:44:10 +00001068}
1069
1070;;
1071;; Define the file for the file "/Users/mine/sources/Myheader.h"
1072;;
1073!3 = metadata !{
1074 i32 524329, ;; Tag
1075 metadata !"Myheader.h"
1076 metadata !"/Users/mine/sources",
Devang Patel4a7904d62010-07-13 16:53:20 +00001077 metadata !2 ;; Compile unit
Devang Patel59445db2010-03-09 00:44:10 +00001078}
Jim Laskey14edc932006-03-14 18:08:46 +00001079
Jim Laskey14edc932006-03-14 18:08:46 +00001080...
1081</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001082</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001083
Devang Patel5bc1c4b2010-03-26 19:08:36 +00001084<p>llvm::Instruction provides easy access to metadata attached with an
1085instruction. One can extract line number information encoded in LLVM IR
1086using <tt>Instruction::getMetadata()</tt> and
1087<tt>DILocation::getLineNumber()</tt>.
1088<pre>
1089 if (MDNode *N = I->getMetadata("dbg")) { // Here I is an LLVM instruction
1090 DILocation Loc(N); // DILocation is in DebugInfo.h
1091 unsigned Line = Loc.getLineNumber();
1092 StringRef File = Loc.getFilename();
1093 StringRef Dir = Loc.getDirectory();
1094 }
1095</pre>
Chris Lattner941515c2004-01-06 05:31:32 +00001096</div>
1097
1098<!-- ======================================================================= -->
1099<div class="doc_subsection">
Jim Laskey14edc932006-03-14 18:08:46 +00001100 <a name="ccxx_global_variable">C/C++ global variable information</a>
Chris Lattner941515c2004-01-06 05:31:32 +00001101</div>
1102
1103<div class="doc_text">
Jim Laskey14edc932006-03-14 18:08:46 +00001104
Misha Brukman39dcddf2008-12-16 02:54:22 +00001105<p>Given an integer global variable declared as follows:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001106
Bill Wendlinge9353d72009-05-17 05:52:39 +00001107<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001108<pre>
1109int MyGlobal = 100;
1110</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001111</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001112
Misha Brukman39dcddf2008-12-16 02:54:22 +00001113<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001114
Bill Wendlinge9353d72009-05-17 05:52:39 +00001115<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001116<pre>
1117;;
Jim Laskey14edc932006-03-14 18:08:46 +00001118;; Define the global itself.
1119;;
1120%MyGlobal = global int 100
1121...
1122;;
Devang Patel80ae3492009-08-28 23:24:31 +00001123;; List of debug info of globals
Jim Laskey14edc932006-03-14 18:08:46 +00001124;;
Devang Patel80ae3492009-08-28 23:24:31 +00001125!llvm.dbg.gv = !{!0}
Jim Laskey14edc932006-03-14 18:08:46 +00001126
1127;;
1128;; Define the global variable descriptor. Note the reference to the global
1129;; variable anchor and the global variable itself.
1130;;
Devang Patel80ae3492009-08-28 23:24:31 +00001131!0 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001132 i32 524340, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001133 i32 0, ;; Unused
1134 metadata !1, ;; Context
1135 metadata !"MyGlobal", ;; Name
1136 metadata !"MyGlobal", ;; Display Name
1137 metadata !"MyGlobal", ;; Linkage Name
Devang Patel59445db2010-03-09 00:44:10 +00001138 metadata !3, ;; Compile Unit
Devang Patel80ae3492009-08-28 23:24:31 +00001139 i32 1, ;; Line Number
Devang Patel59445db2010-03-09 00:44:10 +00001140 metadata !4, ;; Type
Devang Patel80ae3492009-08-28 23:24:31 +00001141 i1 false, ;; Is a local variable
1142 i1 true, ;; Is this a definition
1143 i32* @MyGlobal ;; The global variable
1144}
1145
Jim Laskey14edc932006-03-14 18:08:46 +00001146;;
1147;; Define the basic type of 32 bit signed integer. Note that since int is an
1148;; intrinsic type the source file is NULL and line 0.
1149;;
Devang Patel59445db2010-03-09 00:44:10 +00001150!4 = metadata !{
1151 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001152 metadata !1, ;; Context
1153 metadata !"int", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001154 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001155 i32 0, ;; Line number
1156 i64 32, ;; Size in Bits
1157 i64 32, ;; Align in Bits
1158 i64 0, ;; Offset in Bits
1159 i32 0, ;; Flags
1160 i32 5 ;; Encoding
1161}
Jim Laskey14edc932006-03-14 18:08:46 +00001162
Jim Laskey14edc932006-03-14 18:08:46 +00001163</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001164</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001165
Chris Lattner941515c2004-01-06 05:31:32 +00001166</div>
Chris Lattner1811fca2004-01-05 05:06:33 +00001167
Jim Laskey14edc932006-03-14 18:08:46 +00001168<!-- ======================================================================= -->
1169<div class="doc_subsection">
1170 <a name="ccxx_subprogram">C/C++ function information</a>
1171</div>
1172
1173<div class="doc_text">
1174
Misha Brukman39dcddf2008-12-16 02:54:22 +00001175<p>Given a function declared as follows:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001176
Bill Wendlinge9353d72009-05-17 05:52:39 +00001177<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001178<pre>
1179int main(int argc, char *argv[]) {
1180 return 0;
1181}
1182</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001183</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001184
Misha Brukman39dcddf2008-12-16 02:54:22 +00001185<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001186
Bill Wendlinge9353d72009-05-17 05:52:39 +00001187<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001188<pre>
1189;;
Jim Laskey14edc932006-03-14 18:08:46 +00001190;; Define the anchor for subprograms. Note that the second field of the
1191;; anchor is 46, which is the same as the tag for subprograms
1192;; (46 = DW_TAG_subprogram.)
1193;;
Devang Patel59445db2010-03-09 00:44:10 +00001194!6 = metadata !{
1195 i32 524334, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001196 i32 0, ;; Unused
1197 metadata !1, ;; Context
1198 metadata !"main", ;; Name
1199 metadata !"main", ;; Display name
1200 metadata !"main", ;; Linkage name
Devang Patel59445db2010-03-09 00:44:10 +00001201 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001202 i32 1, ;; Line number
Devang Patel59445db2010-03-09 00:44:10 +00001203 metadata !4, ;; Type
Devang Patel80ae3492009-08-28 23:24:31 +00001204 i1 false, ;; Is local
Devang Patel9f738842011-04-05 22:52:06 +00001205 i1 true, ;; Is definition
1206 i32 0, ;; Virtuality attribute, e.g. pure virtual function
1207 i32 0, ;; Index into virtual table for C++ methods
1208 i32 0, ;; Type that holds virtual table.
1209 i32 0, ;; Flags
1210 i1 false, ;; True if this function is optimized
1211 Function *, ;; Pointer to llvm::Function
1212 null ;; Function template parameters
Devang Patel80ae3492009-08-28 23:24:31 +00001213}
Jim Laskey14edc932006-03-14 18:08:46 +00001214;;
1215;; Define the subprogram itself.
1216;;
Devang Patel80ae3492009-08-28 23:24:31 +00001217define i32 @main(i32 %argc, i8** %argv) {
Jim Laskey14edc932006-03-14 18:08:46 +00001218...
1219}
1220</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001221</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001222
1223</div>
1224
1225<!-- ======================================================================= -->
1226<div class="doc_subsection">
1227 <a name="ccxx_basic_types">C/C++ basic types</a>
1228</div>
1229
1230<div class="doc_text">
1231
Misha Brukman39dcddf2008-12-16 02:54:22 +00001232<p>The following are the basic type descriptors for C/C++ core types:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001233
1234</div>
1235
1236<!-- ======================================================================= -->
1237<div class="doc_subsubsection">
1238 <a name="ccxx_basic_type_bool">bool</a>
1239</div>
1240
1241<div class="doc_text">
1242
Bill Wendlinge9353d72009-05-17 05:52:39 +00001243<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001244<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001245!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001246 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001247 metadata !1, ;; Context
1248 metadata !"bool", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001249 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001250 i32 0, ;; Line number
1251 i64 8, ;; Size in Bits
1252 i64 8, ;; Align in Bits
1253 i64 0, ;; Offset in Bits
1254 i32 0, ;; Flags
1255 i32 2 ;; Encoding
1256}
Jim Laskey14edc932006-03-14 18:08:46 +00001257</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001258</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001259
1260</div>
1261
1262<!-- ======================================================================= -->
1263<div class="doc_subsubsection">
1264 <a name="ccxx_basic_char">char</a>
1265</div>
1266
1267<div class="doc_text">
1268
Bill Wendlinge9353d72009-05-17 05:52:39 +00001269<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001270<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001271!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001272 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001273 metadata !1, ;; Context
1274 metadata !"char", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001275 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001276 i32 0, ;; Line number
1277 i64 8, ;; Size in Bits
1278 i64 8, ;; Align in Bits
1279 i64 0, ;; Offset in Bits
1280 i32 0, ;; Flags
1281 i32 6 ;; Encoding
1282}
Jim Laskey14edc932006-03-14 18:08:46 +00001283</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001284</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001285
1286</div>
1287
1288<!-- ======================================================================= -->
1289<div class="doc_subsubsection">
1290 <a name="ccxx_basic_unsigned_char">unsigned char</a>
1291</div>
1292
1293<div class="doc_text">
1294
Bill Wendlinge9353d72009-05-17 05:52:39 +00001295<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001296<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001297!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001298 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001299 metadata !1, ;; Context
1300 metadata !"unsigned char",
Devang Patel59445db2010-03-09 00:44:10 +00001301 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001302 i32 0, ;; Line number
1303 i64 8, ;; Size in Bits
1304 i64 8, ;; Align in Bits
1305 i64 0, ;; Offset in Bits
1306 i32 0, ;; Flags
1307 i32 8 ;; Encoding
1308}
Jim Laskey14edc932006-03-14 18:08:46 +00001309</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001310</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001311
1312</div>
1313
1314<!-- ======================================================================= -->
1315<div class="doc_subsubsection">
1316 <a name="ccxx_basic_short">short</a>
1317</div>
1318
1319<div class="doc_text">
1320
Bill Wendlinge9353d72009-05-17 05:52:39 +00001321<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001322<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001323!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001324 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001325 metadata !1, ;; Context
1326 metadata !"short int",
Devang Patel59445db2010-03-09 00:44:10 +00001327 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001328 i32 0, ;; Line number
1329 i64 16, ;; Size in Bits
1330 i64 16, ;; Align in Bits
1331 i64 0, ;; Offset in Bits
1332 i32 0, ;; Flags
1333 i32 5 ;; Encoding
1334}
Jim Laskey14edc932006-03-14 18:08:46 +00001335</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001336</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001337
1338</div>
1339
1340<!-- ======================================================================= -->
1341<div class="doc_subsubsection">
1342 <a name="ccxx_basic_unsigned_short">unsigned short</a>
1343</div>
1344
1345<div class="doc_text">
1346
Bill Wendlinge9353d72009-05-17 05:52:39 +00001347<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001348<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001349!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001350 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001351 metadata !1, ;; Context
1352 metadata !"short unsigned int",
Devang Patel59445db2010-03-09 00:44:10 +00001353 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001354 i32 0, ;; Line number
1355 i64 16, ;; Size in Bits
1356 i64 16, ;; Align in Bits
1357 i64 0, ;; Offset in Bits
1358 i32 0, ;; Flags
1359 i32 7 ;; Encoding
1360}
Jim Laskey14edc932006-03-14 18:08:46 +00001361</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001362</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001363
1364</div>
1365
1366<!-- ======================================================================= -->
1367<div class="doc_subsubsection">
1368 <a name="ccxx_basic_int">int</a>
1369</div>
1370
1371<div class="doc_text">
1372
Bill Wendlinge9353d72009-05-17 05:52:39 +00001373<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001374<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001375!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001376 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001377 metadata !1, ;; Context
1378 metadata !"int", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001379 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001380 i32 0, ;; Line number
1381 i64 32, ;; Size in Bits
1382 i64 32, ;; Align in Bits
1383 i64 0, ;; Offset in Bits
1384 i32 0, ;; Flags
1385 i32 5 ;; Encoding
1386}
Bill Wendlinge9353d72009-05-17 05:52:39 +00001387</pre></div>
Jim Laskey14edc932006-03-14 18:08:46 +00001388
1389</div>
1390
1391<!-- ======================================================================= -->
1392<div class="doc_subsubsection">
1393 <a name="ccxx_basic_unsigned_int">unsigned int</a>
1394</div>
1395
1396<div class="doc_text">
1397
Bill Wendlinge9353d72009-05-17 05:52:39 +00001398<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001399<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001400!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001401 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001402 metadata !1, ;; Context
1403 metadata !"unsigned int",
Devang Patel59445db2010-03-09 00:44:10 +00001404 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001405 i32 0, ;; Line number
1406 i64 32, ;; Size in Bits
1407 i64 32, ;; Align in Bits
1408 i64 0, ;; Offset in Bits
1409 i32 0, ;; Flags
1410 i32 7 ;; Encoding
1411}
Jim Laskey14edc932006-03-14 18:08:46 +00001412</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001413</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001414
1415</div>
1416
1417<!-- ======================================================================= -->
1418<div class="doc_subsubsection">
1419 <a name="ccxx_basic_long_long">long long</a>
1420</div>
1421
1422<div class="doc_text">
1423
Bill Wendlinge9353d72009-05-17 05:52:39 +00001424<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001425<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001426!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001427 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001428 metadata !1, ;; Context
1429 metadata !"long long int",
Devang Patel59445db2010-03-09 00:44:10 +00001430 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001431 i32 0, ;; Line number
1432 i64 64, ;; Size in Bits
1433 i64 64, ;; Align in Bits
1434 i64 0, ;; Offset in Bits
1435 i32 0, ;; Flags
1436 i32 5 ;; Encoding
1437}
Jim Laskey14edc932006-03-14 18:08:46 +00001438</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001439</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001440
1441</div>
1442
1443<!-- ======================================================================= -->
1444<div class="doc_subsubsection">
1445 <a name="ccxx_basic_unsigned_long_long">unsigned long long</a>
1446</div>
1447
1448<div class="doc_text">
1449
Bill Wendlinge9353d72009-05-17 05:52:39 +00001450<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001451<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001452!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001453 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001454 metadata !1, ;; Context
1455 metadata !"long long unsigned int",
Devang Patel59445db2010-03-09 00:44:10 +00001456 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001457 i32 0, ;; Line number
1458 i64 64, ;; Size in Bits
1459 i64 64, ;; Align in Bits
1460 i64 0, ;; Offset in Bits
1461 i32 0, ;; Flags
1462 i32 7 ;; Encoding
1463}
Jim Laskey14edc932006-03-14 18:08:46 +00001464</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001465</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001466
1467</div>
1468
1469<!-- ======================================================================= -->
1470<div class="doc_subsubsection">
1471 <a name="ccxx_basic_float">float</a>
1472</div>
1473
1474<div class="doc_text">
1475
Bill Wendlinge9353d72009-05-17 05:52:39 +00001476<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001477<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001478!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001479 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001480 metadata !1, ;; Context
1481 metadata !"float",
Devang Patel59445db2010-03-09 00:44:10 +00001482 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001483 i32 0, ;; Line number
1484 i64 32, ;; Size in Bits
1485 i64 32, ;; Align in Bits
1486 i64 0, ;; Offset in Bits
1487 i32 0, ;; Flags
1488 i32 4 ;; Encoding
1489}
Jim Laskey14edc932006-03-14 18:08:46 +00001490</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001491</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001492
1493</div>
1494
1495<!-- ======================================================================= -->
1496<div class="doc_subsubsection">
1497 <a name="ccxx_basic_double">double</a>
1498</div>
1499
1500<div class="doc_text">
1501
Bill Wendlinge9353d72009-05-17 05:52:39 +00001502<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001503<pre>
Devang Patel80ae3492009-08-28 23:24:31 +00001504!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001505 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001506 metadata !1, ;; Context
1507 metadata !"double",;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001508 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001509 i32 0, ;; Line number
1510 i64 64, ;; Size in Bits
1511 i64 64, ;; Align in Bits
1512 i64 0, ;; Offset in Bits
1513 i32 0, ;; Flags
1514 i32 4 ;; Encoding
1515}
Jim Laskey14edc932006-03-14 18:08:46 +00001516</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001517</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001518
1519</div>
1520
1521<!-- ======================================================================= -->
1522<div class="doc_subsection">
1523 <a name="ccxx_derived_types">C/C++ derived types</a>
1524</div>
1525
1526<div class="doc_text">
1527
Misha Brukman39dcddf2008-12-16 02:54:22 +00001528<p>Given the following as an example of C/C++ derived type:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001529
Bill Wendlinge9353d72009-05-17 05:52:39 +00001530<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001531<pre>
1532typedef const int *IntPtr;
1533</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001534</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001535
Misha Brukman39dcddf2008-12-16 02:54:22 +00001536<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001537
Bill Wendlinge9353d72009-05-17 05:52:39 +00001538<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001539<pre>
1540;;
1541;; Define the typedef "IntPtr".
1542;;
Devang Patel80ae3492009-08-28 23:24:31 +00001543!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001544 i32 524310, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001545 metadata !1, ;; Context
1546 metadata !"IntPtr", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001547 metadata !3, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001548 i32 0, ;; Line number
1549 i64 0, ;; Size in bits
1550 i64 0, ;; Align in bits
1551 i64 0, ;; Offset in bits
1552 i32 0, ;; Flags
1553 metadata !4 ;; Derived From type
1554}
Jim Laskey14edc932006-03-14 18:08:46 +00001555
1556;;
1557;; Define the pointer type.
1558;;
Devang Patel80ae3492009-08-28 23:24:31 +00001559!4 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001560 i32 524303, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001561 metadata !1, ;; Context
1562 metadata !"", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001563 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001564 i32 0, ;; Line number
1565 i64 64, ;; Size in bits
1566 i64 64, ;; Align in bits
1567 i64 0, ;; Offset in bits
1568 i32 0, ;; Flags
1569 metadata !5 ;; Derived From type
1570}
Jim Laskey14edc932006-03-14 18:08:46 +00001571;;
1572;; Define the const type.
1573;;
Devang Patel80ae3492009-08-28 23:24:31 +00001574!5 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001575 i32 524326, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001576 metadata !1, ;; Context
1577 metadata !"", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001578 metadata !1, ;; File
Devang Patel80ae3492009-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 metadata !6 ;; Derived From type
1585}
Jim Laskey14edc932006-03-14 18:08:46 +00001586;;
1587;; Define the int type.
1588;;
Devang Patel80ae3492009-08-28 23:24:31 +00001589!6 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001590 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001591 metadata !1, ;; Context
1592 metadata !"int", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001593 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001594 i32 0, ;; Line number
1595 i64 32, ;; Size in bits
1596 i64 32, ;; Align in bits
1597 i64 0, ;; Offset in bits
1598 i32 0, ;; Flags
1599 5 ;; Encoding
1600}
Jim Laskey14edc932006-03-14 18:08:46 +00001601</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001602</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001603
1604</div>
1605
1606<!-- ======================================================================= -->
1607<div class="doc_subsection">
1608 <a name="ccxx_composite_types">C/C++ struct/union types</a>
1609</div>
1610
1611<div class="doc_text">
1612
Misha Brukman39dcddf2008-12-16 02:54:22 +00001613<p>Given the following as an example of C/C++ struct type:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001614
Bill Wendlinge9353d72009-05-17 05:52:39 +00001615<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001616<pre>
1617struct Color {
1618 unsigned Red;
1619 unsigned Green;
1620 unsigned Blue;
1621};
1622</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001623</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001624
Misha Brukman39dcddf2008-12-16 02:54:22 +00001625<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001626
Bill Wendlinge9353d72009-05-17 05:52:39 +00001627<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001628<pre>
1629;;
1630;; Define basic type for unsigned int.
1631;;
Devang Patel80ae3492009-08-28 23:24:31 +00001632!5 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001633 i32 524324, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001634 metadata !1, ;; Context
1635 metadata !"unsigned int",
Devang Patel59445db2010-03-09 00:44:10 +00001636 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001637 i32 0, ;; Line number
1638 i64 32, ;; Size in Bits
1639 i64 32, ;; Align in Bits
1640 i64 0, ;; Offset in Bits
1641 i32 0, ;; Flags
1642 i32 7 ;; Encoding
1643}
Jim Laskey14edc932006-03-14 18:08:46 +00001644;;
1645;; Define composite type for struct Color.
1646;;
Devang Patel80ae3492009-08-28 23:24:31 +00001647!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001648 i32 524307, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001649 metadata !1, ;; Context
1650 metadata !"Color", ;; Name
1651 metadata !1, ;; Compile unit
1652 i32 1, ;; Line number
1653 i64 96, ;; Size in bits
1654 i64 32, ;; Align in bits
1655 i64 0, ;; Offset in bits
1656 i32 0, ;; Flags
1657 null, ;; Derived From
1658 metadata !3, ;; Elements
1659 i32 0 ;; Runtime Language
1660}
Jim Laskey14edc932006-03-14 18:08:46 +00001661
1662;;
1663;; Define the Red field.
1664;;
Devang Patel80ae3492009-08-28 23:24:31 +00001665!4 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001666 i32 524301, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001667 metadata !1, ;; Context
1668 metadata !"Red", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001669 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001670 i32 2, ;; Line number
1671 i64 32, ;; Size in bits
1672 i64 32, ;; Align in bits
1673 i64 0, ;; Offset in bits
1674 i32 0, ;; Flags
1675 metadata !5 ;; Derived From type
1676}
Jim Laskey14edc932006-03-14 18:08:46 +00001677
1678;;
1679;; Define the Green field.
1680;;
Devang Patel80ae3492009-08-28 23:24:31 +00001681!6 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001682 i32 524301, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001683 metadata !1, ;; Context
1684 metadata !"Green", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001685 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001686 i32 3, ;; Line number
1687 i64 32, ;; Size in bits
1688 i64 32, ;; Align in bits
1689 i64 32, ;; Offset in bits
1690 i32 0, ;; Flags
1691 metadata !5 ;; Derived From type
1692}
Jim Laskey14edc932006-03-14 18:08:46 +00001693
1694;;
1695;; Define the Blue field.
1696;;
Devang Patel80ae3492009-08-28 23:24:31 +00001697!7 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001698 i32 524301, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001699 metadata !1, ;; Context
1700 metadata !"Blue", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001701 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001702 i32 4, ;; Line number
1703 i64 32, ;; Size in bits
1704 i64 32, ;; Align in bits
1705 i64 64, ;; Offset in bits
1706 i32 0, ;; Flags
1707 metadata !5 ;; Derived From type
1708}
Jim Laskey14edc932006-03-14 18:08:46 +00001709
1710;;
1711;; Define the array of fields used by the composite type Color.
1712;;
Devang Patel80ae3492009-08-28 23:24:31 +00001713!3 = metadata !{metadata !4, metadata !6, metadata !7}
Jim Laskey14edc932006-03-14 18:08:46 +00001714</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001715</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001716
1717</div>
1718
1719<!-- ======================================================================= -->
1720<div class="doc_subsection">
1721 <a name="ccxx_enumeration_types">C/C++ enumeration types</a>
1722</div>
1723
1724<div class="doc_text">
1725
Misha Brukman39dcddf2008-12-16 02:54:22 +00001726<p>Given the following as an example of C/C++ enumeration type:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001727
Bill Wendlinge9353d72009-05-17 05:52:39 +00001728<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001729<pre>
1730enum Trees {
1731 Spruce = 100,
1732 Oak = 200,
1733 Maple = 300
1734};
1735</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001736</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001737
Misha Brukman39dcddf2008-12-16 02:54:22 +00001738<p>a C/C++ front-end would generate the following descriptors:</p>
Jim Laskey14edc932006-03-14 18:08:46 +00001739
Bill Wendlinge9353d72009-05-17 05:52:39 +00001740<div class="doc_code">
Jim Laskey14edc932006-03-14 18:08:46 +00001741<pre>
1742;;
1743;; Define composite type for enum Trees
1744;;
Devang Patel80ae3492009-08-28 23:24:31 +00001745!2 = metadata !{
Devang Patel59445db2010-03-09 00:44:10 +00001746 i32 524292, ;; Tag
Devang Patel80ae3492009-08-28 23:24:31 +00001747 metadata !1, ;; Context
1748 metadata !"Trees", ;; Name
Devang Patel59445db2010-03-09 00:44:10 +00001749 metadata !1, ;; File
Devang Patel80ae3492009-08-28 23:24:31 +00001750 i32 1, ;; Line number
1751 i64 32, ;; Size in bits
1752 i64 32, ;; Align in bits
1753 i64 0, ;; Offset in bits
1754 i32 0, ;; Flags
1755 null, ;; Derived From type
1756 metadata !3, ;; Elements
1757 i32 0 ;; Runtime language
1758}
Devang Patel02aac922009-08-25 05:24:07 +00001759
Devang Patelf08e35d2009-08-26 05:01:18 +00001760;;
1761;; Define the array of enumerators used by composite type Trees.
1762;;
Devang Patel80ae3492009-08-28 23:24:31 +00001763!3 = metadata !{metadata !4, metadata !5, metadata !6}
1764
1765;;
1766;; Define Spruce enumerator.
1767;;
Devang Patel59445db2010-03-09 00:44:10 +00001768!4 = metadata !{i32 524328, metadata !"Spruce", i64 100}
Devang Patel80ae3492009-08-28 23:24:31 +00001769
1770;;
1771;; Define Oak enumerator.
1772;;
Devang Patel59445db2010-03-09 00:44:10 +00001773!5 = metadata !{i32 524328, metadata !"Oak", i64 200}
Devang Patel80ae3492009-08-28 23:24:31 +00001774
1775;;
1776;; Define Maple enumerator.
1777;;
Devang Patel59445db2010-03-09 00:44:10 +00001778!6 = metadata !{i32 524328, metadata !"Maple", i64 300}
Devang Patel80ae3492009-08-28 23:24:31 +00001779
Jim Laskey14edc932006-03-14 18:08:46 +00001780</pre>
Bill Wendlinge9353d72009-05-17 05:52:39 +00001781</div>
Jim Laskey14edc932006-03-14 18:08:46 +00001782
1783</div>
Chris Lattner1811fca2004-01-05 05:06:33 +00001784
1785<!-- *********************************************************************** -->
Misha Brukmanf91d9942004-05-12 19:21:57 +00001786
Chris Lattner1811fca2004-01-05 05:06:33 +00001787<hr>
Misha Brukmanf91d9942004-05-12 19:21:57 +00001788<address>
1789 <a href="http://jigsaw.w3.org/css-validator/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +00001790 src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS"></a>
Misha Brukmanf91d9942004-05-12 19:21:57 +00001791 <a href="http://validator.w3.org/check/referer"><img
Misha Brukman86242e12008-12-11 17:34:48 +00001792 src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01"></a>
Misha Brukmanf91d9942004-05-12 19:21:57 +00001793
1794 <a href="mailto:sabre@nondot.org">Chris Lattner</a><br>
NAKAMURA Takumica46f5a2011-04-09 02:13:37 +00001795 <a href="http://llvm.org/">LLVM Compiler Infrastructure</a><br>
Chris Lattner1811fca2004-01-05 05:06:33 +00001796 Last modified: $Date$
Misha Brukmanf91d9942004-05-12 19:21:57 +00001797</address>
Chris Lattner1811fca2004-01-05 05:06:33 +00001798
1799</body>
1800</html>