mirror of
https://github.com/RPCS3/llvm.git
synced 2025-02-24 21:00:36 +00:00
Small fixes to this documentation. Remove mention of uint/int type, fix typo
in 'number'. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@100001 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
parent
cfd3188a11
commit
655fd03360
@ -289,26 +289,25 @@ height="369">
|
||||
0x1000.)</p>
|
||||
|
||||
<p>The fields of debug descriptors used internally by LLVM
|
||||
are restricted to only the simple data types <tt>int</tt>, <tt>uint</tt>,
|
||||
<tt>bool</tt>, <tt>float</tt>, <tt>double</tt>, <tt>mdstring</tt> and
|
||||
<tt>mdnode</tt>. </p>
|
||||
are restricted to only the simple data types <tt>i32</tt>, <tt>i1</tt>,
|
||||
<tt>float</tt>, <tt>double</tt>, <tt>mdstring</tt> and <tt>mdnode</tt>. </p>
|
||||
|
||||
<div class="doc_code">
|
||||
<pre>
|
||||
!1 = metadata !{
|
||||
uint, ;; A tag
|
||||
i32, ;; A tag
|
||||
...
|
||||
}
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p><a name="LLVMDebugVersion">The first field of a descriptor is always an
|
||||
<tt>uint</tt> containing a tag value identifying the content of the
|
||||
<tt>i32</tt> containing a tag value identifying the content of the
|
||||
descriptor. The remaining fields are specific to the descriptor. The values
|
||||
of tags are loosely bound to the tag values of DWARF information entries.
|
||||
However, that does not restrict the use of the information supplied to DWARF
|
||||
targets. To facilitate versioning of debug information, the tag is augmented
|
||||
with the current debug version (LLVMDebugVersion = 8 << 16 or 0x80000 or
|
||||
with the current debug version (LLVMDebugVersion = 8 << 16 or 0x80000 or
|
||||
524288.)</a></p>
|
||||
|
||||
<p>The details of the various descriptors follow.</p>
|
||||
@ -829,8 +828,8 @@ DW_TAG_return_variable = 258
|
||||
rules.</p>
|
||||
|
||||
<p>In order to handle this, the LLVM debug format uses the metadata attached to
|
||||
llvm instructions to encode line nuber and scoping information. Consider the
|
||||
following C fragment, for example:</p>
|
||||
llvm instructions to encode line number and scoping information. Consider
|
||||
the following C fragment, for example:</p>
|
||||
|
||||
<div class="doc_code">
|
||||
<pre>
|
||||
|
Loading…
x
Reference in New Issue
Block a user