[llvm-commits] CVS: llvm/docs/LangRef.html
Reid Spencer
reid at x10sys.com
Mon May 14 09:15:15 PDT 2007
Changes in directory llvm/docs:
LangRef.html updated: 1.242 -> 1.243
---
Log message:
Revise definition of part_select. The wrapping behavior is not useful so
in the reverse case the only difference is that the bits are returned in
reverse order.
---
Diffs of the changes: (+6 -11)
LangRef.html | 17 ++++++-----------
1 files changed, 6 insertions(+), 11 deletions(-)
Index: llvm/docs/LangRef.html
diff -u llvm/docs/LangRef.html:1.242 llvm/docs/LangRef.html:1.243
--- llvm/docs/LangRef.html:1.242 Sun Apr 29 13:35:00 2007
+++ llvm/docs/LangRef.html Mon May 14 11:14:57 2007
@@ -4655,16 +4655,11 @@
<li>A mask of the retained bits is created by shifting a -1 value.</li>
<li>The mask is ANDed with <tt>%val</tt> to produce the result.
</ol>
-<p>In reverse mode, a similar computation is made except that:</p>
-<ol>
- <li>The bits selected wrap around to include both the highest and lowest bits.
- For example, part.select(i16 X, 4, 7) selects bits from X with a mask of
- 0x00F0 (forwards case) while part.select(i16 X, 8, 3) selects bits from X
- with a mask of 0xFF0F.</li>
- <li>The bits returned in the reverse case are reversed. So, if X has the value
- 0x6ACF and we apply part.select(i16 X, 8, 3) to it, we get back the value
- 0x0A6F.</li>
-</ol>
+<p>In reverse mode, a similar computation is made except that the bits are
+returned in the reverse order. So, for example, if <tt>X</tt> has the value
+<tt>i16 0x0ACF (101011001111)</tt> and we apply
+<tt>part.select(i16 X, 8, 3)</tt> to it, we get back the value
+<tt>i16 0x0026 (000000100110)</tt>.</p>
</div>
<div class="doc_subsubsection">
@@ -4756,7 +4751,7 @@
<a href="mailto:sabre at nondot.org">Chris Lattner</a><br>
<a href="http://llvm.org">The LLVM Compiler Infrastructure</a><br>
- Last modified: $Date: 2007/04/29 18:35:00 $
+ Last modified: $Date: 2007/05/14 16:14:57 $
</address>
</body>
</html>
More information about the llvm-commits
mailing list