[gcc/devel/omp/gcc-11] Fix typo; remove XFAIL

[gcc/devel/omp/gcc-11] Fix typo; remove XFAIL

[Kwok Yeung]

https://gcc.gnu.org/g:c602d1435368be5bb6f82fb7236c9203d28ea753

commit c602d1435368be5bb6f82fb7236c9203d28ea753
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Mon Aug 24 11:00:51 2020 +0200

    Fix typo; remove XFAIL
    
    gcc/
    2020-08-24  Tobias Burnus  <tobias@codesourcery.com>
    
            * omp-sese.c: Fix comment typo.
    
    gcc/testsuite/
    2020-08-24  Tobias Burnus  <tobias@codesourcery.com>
                Sandra Loosemore  <sandra@codesourcery.com>
    
            * testsuite/gfortran.dg/goacc/kernels-decompose-2.f95:
            Fix typo; remove XFAIL.

Diff:
---
 gcc/ChangeLog.omp                                       | 4 ++++
 gcc/omp-sese.c                                          | 2 +-
 gcc/testsuite/ChangeLog.omp                             | 6 ++++++
 gcc/testsuite/gfortran.dg/goacc/kernels-decompose-2.f95 | 2 +-
 4 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/gcc/ChangeLog.omp b/gcc/ChangeLog.omp
index 77d163266ee..d207a8eef18 100644
--- a/gcc/ChangeLog.omp
+++ b/gcc/ChangeLog.omp
@@ -1,3 +1,7 @@
+2020-08-24  Tobias Burnus  <tobias@codesourcery.com>
+
+	* omp-sese.c: Fix comment typo.
+
 2020-08-19  Sandra Loosemore  <sandra@codesourcery.com>
 
 	Add a "combined" flag for "acc kernels loop" etc directives.
diff --git a/gcc/omp-sese.c b/gcc/omp-sese.c
index ad80316f735..af63e70d9ec 100644
--- a/gcc/omp-sese.c
+++ b/gcc/omp-sese.c
@@ -1836,7 +1836,7 @@ oacc_do_neutering (unsigned HOST_WIDE_INT bounds_lo,
    Single-Entry-Single-Exit regions.  Some of those regions will be
    trivial ones consisting of a single BB.  The blocks of a
    partitioned region might form a set of disjoint graphs -- because
-   the region encloses a differently partitoned sub region.
+   the region encloses a differently partitioned sub region.
 
    We use the linear time algorithm described in 'Finding Regions Fast:
    Single Entry Single Exit and control Regions in Linear Time'
diff --git a/gcc/testsuite/ChangeLog.omp b/gcc/testsuite/ChangeLog.omp
index 00cc4332d00..f0f48bc978f 100644
--- a/gcc/testsuite/ChangeLog.omp
+++ b/gcc/testsuite/ChangeLog.omp
@@ -1,3 +1,9 @@
+2020-08-24  Tobias Burnus  <tobias@codesourcery.com>
+	    Sandra Loosemore  <sandra@codesourcery.com>
+
+	* testsuite/gfortran.dg/goacc/kernels-decompose-2.f95:
+	Fix typo; remove XFAIL.
+
 2020-08-23   Sandra Loosemore  <sandra@codesourcery.com>
 
 	* gfortran.dg/goacc/kernels-loop-annotation-1.f95: Update
diff --git a/gcc/testsuite/gfortran.dg/goacc/kernels-decompose-2.f95 b/gcc/testsuite/gfortran.dg/goacc/kernels-decompose-2.f95
index 826838d27a1..80907bebfdf 100644
--- a/gcc/testsuite/gfortran.dg/goacc/kernels-decompose-2.f95
+++ b/gcc/testsuite/gfortran.dg/goacc/kernels-decompose-2.f95
@@ -117,7 +117,7 @@ program main
   end if
   !$acc end kernels
 
-  !$acc kernels
+  !$acc kernels  ! { dg-warning "region contains gang partitioned code but is not gang partitioned" }
   y = f_g (a(5)) ! { dg-line l_part[incr c_part] }
   !TODO If such a construct is placed in its own part (like it is, here), can't this actually use gang paralelism, instead of "gang-single"?
   ! { dg-message "note: beginning 'gang-single' part in OpenACC 'kernels' region" "" { target *-*-* } l_part$c_part }