[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 05:35:36 PDT 2021


This revision was automatically updated to reflect the committed changes.
Closed by commit rG38cf50bc0484: [LangRef] Fix typos in the vector-type memory layout section (authored by frasercrmck).

Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D99163/new/

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.332638.patch
Type: text/x-patch
Size: 828 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20210323/4fd8106c/attachment.bin>


More information about the llvm-commits mailing list