[PATCH] D99163: [LangRef] Fix typos in the vector-type memory layout section
Fraser Cormack via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Tue Mar 23 02:51:59 PDT 2021
frasercrmck created this revision.
frasercrmck added reviewers: bjope, nlopes.
Herald added a subscriber: jdoerfert.
frasercrmck requested review of this revision.
Herald added a project: LLVM.
Herald added a subscriber: llvm-commits.
Repository:
rG LLVM Github Monorepo
https://reviews.llvm.org/D99163
Files:
llvm/docs/LangRef.rst
Index: llvm/docs/LangRef.rst
===================================================================
--- llvm/docs/LangRef.rst
+++ llvm/docs/LangRef.rst
@@ -3223,7 +3223,7 @@
Using a vector such as ``<i4 1, i4 2, i4 3, i4 5>`` as an example, together
with the analogy that we can replace a vector store by a bitcast followed by
-an integer store, we ge this for big endian:
+an integer store, we get this for big endian:
.. code-block:: llvm
@@ -3260,7 +3260,7 @@
When ``<N*M>`` isn't evenly divisible by the byte size the exact memory layout
is unspecified (just like it is for an integral type of the same size). This
is because different targets could put the padding at different positions when
-the type size is smaller than the types store size.
+the type size is smaller than the type's store size.
:Syntax:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D99163.332584.patch
Type: text/x-patch
Size: 828 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20210323/73b752e9/attachment.bin>
More information about the llvm-commits
mailing list