diff options
| author | John Criswell <criswell@uiuc.edu> | 2010-07-30 16:30:28 +0000 |
|---|---|---|
| committer | John Criswell <criswell@uiuc.edu> | 2010-07-30 16:30:28 +0000 |
| commit | cdcbbfcb159eec7249734469939ea9d99d0c08dc (patch) | |
| tree | ab6594ce74ec891630a26ddd78ef26950d5c054b /docs | |
| parent | 10757dd8e1a66128b205bd04797c8aed0cb7a1bd (diff) | |
| download | llvm-cdcbbfcb159eec7249734469939ea9d99d0c08dc.tar.gz llvm-cdcbbfcb159eec7249734469939ea9d99d0c08dc.tar.bz2 llvm-cdcbbfcb159eec7249734469939ea9d99d0c08dc.tar.xz | |
Grammar cop pullover: Corrected and improved some grammar in the description of
the llvm.memset() intrinsic family.
No content changes.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@109863 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/LangRef.html | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/LangRef.html b/docs/LangRef.html index 42ae0ae4b1..ff707a45b6 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -6119,8 +6119,8 @@ LLVM</a>.</p> <h5>Syntax:</h5> <p>This is an overloaded intrinsic. You can use llvm.memset on any integer bit - width and for different address spaces. Not all targets support all bit - widths however.</p> + width and for different address spaces. However, not all targets support all + bit widths.</p> <pre> declare void @llvm.memset.p0i8.i32(i8* <dest>, i8 <val>, @@ -6134,14 +6134,14 @@ LLVM</a>.</p> particular byte value.</p> <p>Note that, unlike the standard libc function, the <tt>llvm.memset</tt> - intrinsic does not return a value, takes extra alignment/volatile arguments, - and the destination can be in an arbitrary address space.</p> + intrinsic does not return a value and takes extra alignment/volatile + arguments. Also, the destination can be in an arbitrary address space.</p> <h5>Arguments:</h5> <p>The first argument is a pointer to the destination to fill, the second is the - byte value to fill it with, the third argument is an integer argument + byte value with which to fill it, the third argument is an integer argument specifying the number of bytes to fill, and the fourth argument is the known - alignment of destination location.</p> + alignment of the destination location.</p> <p>If the call to this intrinsic has an alignment value that is not 0 or 1, then the caller guarantees that the destination pointer is aligned to that |