[flang-commits] [flang] 9e37b1e - [flang] Fixed a number of typos

Valentin Clement via flang-commits flang-commits at lists.llvm.org
Thu Aug 25 09:11:53 PDT 2022 

Author: Gabriel Ravier
Date: 2022-08-25T18:11:38+02:00
New Revision: 9e37b1e5a0c15f36c5642406d5aa02a657a0b19c

URL: https://github.com/llvm/llvm-project/commit/9e37b1e5a0c15f36c5642406d5aa02a657a0b19c
DIFF: https://github.com/llvm/llvm-project/commit/9e37b1e5a0c15f36c5642406d5aa02a657a0b19c.diff

LOG: [flang] Fixed a number of typos

I went over the output of the following mess of a command:

`(ulimit -m 2000000; ulimit -v 2000000; git ls-files -z | parallel --xargs -0 cat | aspell list --mode=none --ignore-case | grep -E '^[A-Za-z][a-z]*$' | sort | uniq -c | sort -n | grep -vE '.{25}' | aspell pipe -W3 | grep : | cut -d' ' -f2 | less)`

and proceeded to spend a few days looking at it to find probable typos
and fixed a few hundred of them in all of the llvm project (note, the
ones I found are not anywhere near all of them, but it seems like a
good start).

Reviewed By: awarzynski, clementval

Differential Revision: https://reviews.llvm.org/D130844

Added: 
    

Modified: 
    flang/docs/Extensions.md
    flang/docs/FIRArrayOperations.md
    flang/examples/FlangOmpReport/yaml_summarizer.py
    flang/lib/Optimizer/CodeGen/TargetRewrite.cpp
    flang/lib/Semantics/check-nullify.cpp
    flang/test/Driver/default-backend-pipelines.f90
    flang/test/Semantics/altreturn06.f90
    flang/test/Semantics/call27.f90

Removed: 
    


################################################################################
diff  --git a/flang/docs/Extensions.md b/flang/docs/Extensions.md
index bd3c7ea415871..9e674c15c2f1e 100644
--- a/flang/docs/Extensions.md
+++ b/flang/docs/Extensions.md
@@ -140,7 +140,7 @@ end
   for the default kind of INTEGER are assumed to have the least larger kind
   that can hold them, if one exists.
 * BOZ literals can be used as INTEGER values in contexts where the type is
-  unambiguous: the right hand sides of assigments and initializations
+  unambiguous: the right hand sides of assignments and initializations
   of INTEGER entities, as actual arguments to a few intrinsic functions
   (ACHAR, BTEST, CHAR), and as actual arguments of references to
   procedures with explicit interfaces whose corresponding dummy
@@ -292,7 +292,7 @@ end
 * Use of INTEGER data with the intrinsic logical operators `.NOT.`, `.AND.`, `.OR.`,
   and `.XOR.`.
 * IF (integer expression) THEN ... END IF  (PGI/Intel)
-* Comparsion of LOGICAL with ==/.EQ. rather than .EQV. (also .NEQV.) (PGI/Intel)
+* Comparison of LOGICAL with ==/.EQ. rather than .EQV. (also .NEQV.) (PGI/Intel)
 * Procedure pointers in COMMON blocks (PGI/Intel)
 * Underindexing multi-dimensional arrays (e.g., A(1) rather than A(1,1)) (PGI only)
 * Legacy PGI `NCHARACTER` type and `NC` Kanji character literals

diff  --git a/flang/docs/FIRArrayOperations.md b/flang/docs/FIRArrayOperations.md
index 822bafca84eb5..845a739d789f0 100644
--- a/flang/docs/FIRArrayOperations.md
+++ b/flang/docs/FIRArrayOperations.md
@@ -115,7 +115,7 @@ chained updates, `%r`, and stores the result to the array at address, `%a`.
 This operation taken with `array_load`'s captures Fortran's
 copy-in/copy-out semantics. The first operands of `array_merge_store` is the
 result of the initial `array_load` operation. While this value could be
-retrieved by reference chasiing through the 
diff erent array operations it is
+retrieved by reference chasing through the 
diff erent array operations it is
 useful to have it on hand directly for analysis passes since this directly
 defines the "bounds" of the Fortran statement represented by these operations.
 The intention is to allow copy-in/copy-out regions to be easily delineated,

diff  --git a/flang/examples/FlangOmpReport/yaml_summarizer.py b/flang/examples/FlangOmpReport/yaml_summarizer.py
index 9d8df285d6169..d1d73cde07681 100644
--- a/flang/examples/FlangOmpReport/yaml_summarizer.py
+++ b/flang/examples/FlangOmpReport/yaml_summarizer.py
@@ -44,7 +44,7 @@
     $ python3 yaml_summarizer.py file_1.yaml file_2.yaml
     <Unique OMP constructs with there grouped clauses from file_1.yaml and file_2.yaml>
 
-    Construcsts are in the form:
+    Constructs are in the form:
     - construct: someOMPconstruct
     count: 8
     clauses:

diff  --git a/flang/lib/Optimizer/CodeGen/TargetRewrite.cpp b/flang/lib/Optimizer/CodeGen/TargetRewrite.cpp
index 5bcf79ea83c06..1a67230f8cc1c 100644
--- a/flang/lib/Optimizer/CodeGen/TargetRewrite.cpp
+++ b/flang/lib/Optimizer/CodeGen/TargetRewrite.cpp
@@ -434,7 +434,7 @@ class TargetRewrite : public fir::TargetRewriteBase<TargetRewrite> {
     return mlir::success();
   }
 
-  /// If the signature does not need any special target-specific converions,
+  /// If the signature does not need any special target-specific conversions,
   /// then it is considered portable for any target, and this function will
   /// return `true`. Otherwise, the signature is not portable and `false` is
   /// returned.

diff  --git a/flang/lib/Semantics/check-nullify.cpp b/flang/lib/Semantics/check-nullify.cpp
index c9b3f1077bdc7..7624f7973d2a9 100644
--- a/flang/lib/Semantics/check-nullify.cpp
+++ b/flang/lib/Semantics/check-nullify.cpp
@@ -60,7 +60,7 @@ void NullifyChecker::Leave(const parser::NullifyStmt &nullifyStmt) {
   //   A pointer-object shall not depend on the value,
   //   bounds, or association status of another pointer-
   //   object in the same NULLIFY statement.
-  // This restriction is the programmer's responsibilty.
+  // This restriction is the programmer's responsibility.
   // Some dependencies can be found compile time or at
   // runtime, but for now we choose to skip such checks.
 }

diff  --git a/flang/test/Driver/default-backend-pipelines.f90 b/flang/test/Driver/default-backend-pipelines.f90
index f14c7796daeab..e6910c170f117 100644
--- a/flang/test/Driver/default-backend-pipelines.f90
+++ b/flang/test/Driver/default-backend-pipelines.f90
@@ -1,4 +1,4 @@
-! Verify that`-O{n}` is indeed taken into account when definining the LLVM backend pass pipeline.
+! Verify that`-O{n}` is indeed taken into account when defining the LLVM backend pass pipeline.
 
 ! REQUIRES: aarch64-registered-target
 

diff  --git a/flang/test/Semantics/altreturn06.f90 b/flang/test/Semantics/altreturn06.f90
index 5be40e8009d5b..5a3433f77afc8 100644
--- a/flang/test/Semantics/altreturn06.f90
+++ b/flang/test/Semantics/altreturn06.f90
@@ -1,5 +1,5 @@
 ! RUN: %python %S/test_errors.py %s %flang_fc1
-! Test alternat return argument passing for internal and external subprograms
+! Test alternate return argument passing for internal and external subprograms
 ! Both of the following are OK
   call extSubprogram (*100)
   call intSubprogram (*100)

diff  --git a/flang/test/Semantics/call27.f90 b/flang/test/Semantics/call27.f90
index 97c6304fb3e40..965ec401953f4 100644
--- a/flang/test/Semantics/call27.f90
+++ b/flang/test/Semantics/call27.f90
@@ -1,5 +1,5 @@
 ! RUN: %python %S/test_errors.py %s %flang_fc1
-! Catch NULL() actual argement association with allocatable dummy argument
+! Catch NULL() actual argument association with allocatable dummy argument
 program test
   !ERROR: Null actual argument 'NULL()' may not be associated with allocatable dummy argument 'a='
   call foo1(null())

More information about the flang-commits mailing list