diff options
author | Tobias Burnus <burnus@gcc.gnu.org> | 2019-12-11 12:45:49 +0100 |
---|---|---|
committer | Tobias Burnus <burnus@gcc.gnu.org> | 2019-12-11 12:45:49 +0100 |
commit | 93d90219879aed52fb5a3ec191df59867e66240d (patch) | |
tree | 2622e8d5fd6fe09a9c69249428ac6b697bf37519 /libgomp/ordered.c | |
parent | a0221aeebd5bbe9ba097490b4b916495f2fe163e (diff) | |
download | gcc-93d90219879aed52fb5a3ec191df59867e66240d.zip gcc-93d90219879aed52fb5a3ec191df59867e66240d.tar.gz gcc-93d90219879aed52fb5a3ec191df59867e66240d.tar.bz2 |
libgomp – spelling fixes, incl. omp_lib.h.in
* omp_lib.h.in: Fix spelling of function declaration
omp_get_cancell(l)ation.
* libgomp.texi (acc_is_present, acc_async_test, acc_async_test_all):
Fix typos.
* env.c: Fix comment typos.
* oacc-host.c: Likewise.
* ordered.c: Likewise.
* task.c: Likewise.
* team.c: Likewise.
* config/gcn/task.c: Likewise.
* config/gcn/team.c: Likewise.
* config/nvptx/task.c: Likewise.
* config/nvptx/team.c: Likewise.
* plugin/plugin-gcn.c: Likewise.
* testsuite/libgomp.fortran/jacobi.f: Likewise.
* testsuite/libgomp.hsa.c/tiling-2.c: Likewise.
* testsuite/libgomp.oacc-c-c++-common/enter_exit-lib.c: Likewise.
From-SVN: r279218
Diffstat (limited to 'libgomp/ordered.c')
-rw-r--r-- | libgomp/ordered.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libgomp/ordered.c b/libgomp/ordered.c index 6d07fd4..60e310e 100644 --- a/libgomp/ordered.c +++ b/libgomp/ordered.c @@ -214,7 +214,7 @@ gomp_ordered_sync (void) Either way we get correct results. However, there is an implicit flush on entry to an ordered region, so we do need to have a barrier here. If we were taking a lock - this could be MEMMODEL_RELEASE since the acquire would be coverd + this could be MEMMODEL_RELEASE since the acquire would be covered by the lock. */ __atomic_thread_fence (MEMMODEL_ACQ_REL); @@ -246,7 +246,7 @@ GOMP_ordered_start (void) However, the current implementation has a flaw in that it does not allow the next thread into the ORDERED section immediately after the current - thread exits the ORDERED section in its last iteration. The existance + thread exits the ORDERED section in its last iteration. The existence of this function allows the implementation to change. */ void |