From 93d90219879aed52fb5a3ec191df59867e66240d Mon Sep 17 00:00:00 2001 From: Tobias Burnus Date: Wed, 11 Dec 2019 12:45:49 +0100 Subject: =?UTF-8?q?libgomp=20=E2=80=93=20spelling=20fixes,=20incl.=20omp?= =?UTF-8?q?=5Flib.h.in?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * 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 --- libgomp/ordered.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'libgomp/ordered.c') 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 -- cgit v1.1