[NFC] Trim trailing whitespace in *.rst

[platform/upstream/llvm.git] / openmp / docs / remarks / OMP110.rst

diff --git a/openmp/docs/remarks/OMP110.rst b/openmp/docs/remarks/OMP110.rst
index 6d69d6d..ae01b4d 100644 (file)
--- a/openmp/docs/remarks/OMP110.rst
+++ b/openmp/docs/remarks/OMP110.rst
@@ -1,15 +1,15 @@
+.. _omp110:
+
 Moving globalized variable to the stack. [OMP110]
 =================================================
 
-.. _omp110:
-
 This optimization remark indicates that a globalized variable was moved back to
 thread-local stack memory on the device. This occurs when the optimization pass
-can determine that a globalized variable is not possibly be shared between
-threads and globalization was unnecessary. Using stack memory is the best-case
-scenario for data globalization as the variable can now be stored in fast
-register files on the device. This optimization requires full visibility of each
-variable.
+can determine that a globalized variable cannot possibly be shared between
+threads and globalization was ultimately unnecessary. Using stack memory is the
+best-case scenario for data globalization as the variable can now be stored in
+fast register files on the device. This optimization requires full visibility of
+each variable.
 
 Globalization typically occurs when a pointer to a thread-local variable escapes
 the current scope. The compiler needs to be pessimistic and assume that the
@@ -31,12 +31,12 @@ Fortunately, this optimization can undo this by looking at its usage.
 .. code-block:: c++
 
   void use(int *x) { }
-  
+
   void foo() {
     int x;
     use(&x);
   }
-  
+
   int main() {
   #pragma omp target parallel
     foo();
@@ -56,9 +56,9 @@ the current scope, but they can again be removed once the usage is visible.
 .. code-block:: c++
 
   #include <complex>
-  
+
   using complex = std::complex<double>;
-  
+
   void zaxpy(complex *X, complex *Y, const complex D, int N) {
   #pragma omp target teams distribute parallel for firstprivate(D)
     for (int i = 0; i < N; ++i)