[llvm] 38cf50b - [LangRef] Fix typos in the vector-type memory layout section
Fraser Cormack via llvm-commits
llvm-commits at lists.llvm.org
Tue Mar 23 05:35:33 PDT 2021
Author: Fraser Cormack
Date: 2021-03-23T12:28:50Z
New Revision: 38cf50bc0484ed5602c86702190a7162c8d84159
URL: https://github.com/llvm/llvm-project/commit/38cf50bc0484ed5602c86702190a7162c8d84159
DIFF: https://github.com/llvm/llvm-project/commit/38cf50bc0484ed5602c86702190a7162c8d84159.diff
LOG: [LangRef] Fix typos in the vector-type memory layout section
Reviewed By: bjope
Differential Revision: https://reviews.llvm.org/D99163
Added:
Modified:
llvm/docs/LangRef.rst
Removed:
################################################################################
diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst
index e73018955196..4ddedd8cf087 100644
--- a/llvm/docs/LangRef.rst
+++ b/llvm/docs/LangRef.rst
@@ -3223,7 +3223,7 @@ element zero is put in the most significant bits.
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 @@ The same example for little endian:
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
diff erent targets could put the padding at
diff erent positions when
-the type size is smaller than the types store size.
+the type size is smaller than the type's store size.
:Syntax:
More information about the llvm-commits
mailing list