[llvm] 2d480ab - [LangRef] Fix a typo in the vector-type memory layout section

Fraser Cormack via llvm-commits llvm-commits at lists.llvm.org
Tue May 4 07:48:33 PDT 2021


Author: Fraser Cormack
Date: 2021-05-04T15:40:53+01:00
New Revision: 2d480abd9a908fe1c5a86ec1a67cd2e7aeeb66c9

URL: https://github.com/llvm/llvm-project/commit/2d480abd9a908fe1c5a86ec1a67cd2e7aeeb66c9
DIFF: https://github.com/llvm/llvm-project/commit/2d480abd9a908fe1c5a86ec1a67cd2e7aeeb66c9.diff

LOG: [LangRef] Fix a typo in the vector-type memory layout section

Added: 
    

Modified: 
    llvm/docs/LangRef.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst
index 5beed04d002a2..b23fe91ea0b44 100644
--- a/llvm/docs/LangRef.rst
+++ b/llvm/docs/LangRef.rst
@@ -3341,7 +3341,7 @@ vector length is unknown at compile time. Vector types are considered
 :Memory Layout:
 
 In general vector elements are laid out in memory in the same way as
-:ref:`array types <t_array>`. Such an anology works fine as long as the vector
+:ref:`array types <t_array>`. Such an analogy works fine as long as the vector
 elements are byte sized. However, when the elements of the vector aren't byte
 sized it gets a bit more complicated. One way to describe the layout is by
 describing what happens when a vector such as <N x iM> is bitcasted to an


        


More information about the llvm-commits mailing list