Say "bytes" instead of "address units", since that's what the

rest of LangRef uses.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@164402 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Dan Gohman 2012-09-21 18:41:30 +00:00
parent 273a92eb0a
commit ee9f726749

View File

@ -3069,8 +3069,8 @@ are padding and what the TBAA tags of the struct are.</p>
<p>The current metadata format is very simple. <tt>!tbaa.struct</tt> metadata nodes <p>The current metadata format is very simple. <tt>!tbaa.struct</tt> metadata nodes
are a list of operands which are in conceptual groups of three. For each are a list of operands which are in conceptual groups of three. For each
group of three, the first operand gives the byte offset of a field in address group of three, the first operand gives the byte offset of a field in bytes,
units, the second gives its size in address units, and the third gives its the second gives its size in bytes, and the third gives its
tbaa tag. e.g.:</p> tbaa tag. e.g.:</p>
<div class="doc_code"> <div class="doc_code">
@ -3079,9 +3079,9 @@ are padding and what the TBAA tags of the struct are.</p>
</pre> </pre>
</div> </div>
<p>This describes a struct with two fields. The first is at offset 0 address units <p>This describes a struct with two fields. The first is at offset 0 bytes
with size 4 address units, and has tbaa tag !1. The second is at offset 8 address with size 4 bytes, and has tbaa tag !1. The second is at offset 8 bytes
units and has size 4 address units and has tbaa tag !2.</p> and has size 4 bytes and has tbaa tag !2.</p>
<p>Note that the fields need not be contiguous. In this example, there is a <p>Note that the fields need not be contiguous. In this example, there is a
4 byte gap between the two fields. This gap represents padding which 4 byte gap between the two fields. This gap represents padding which