diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2020-03-26 17:34:01 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2020-03-26 17:34:01 +0100 |
| commit | 775f1686a3df68bd20370f1fabc6273883e2c5d2 (patch) | |
| tree | 2ac4c57922d756e79bfbd0087cceb1940ec03644 /libgo/go/sync | |
| parent | 9ae129017c7fc1fa638d6beedd3802b515ca692b (diff) | |
Really fix og9 "Fix hang when running oacc exec with CUDA 9.0 nvprof"devel/omp/gcc-9
In my yesterday's commit 9ae129017c7fc1fa638d6beedd3802b515ca692b 'Fix og9 "Fix
hang when running oacc exec with CUDA 9.0 nvprof"', I wrongly blamed the og9
"Fix hang when running oacc exec with CUDA 9.0 nvprof" to be responsible for
the hang being back, when in fact it's only the later og9 "OpenACC Profiling
Interface (incomplete)" backport from trunk that introduced the problem.
The confusing thing was that the og9 "Fix hang when running oacc exec with CUDA
9.0 nvprof" commit appears *before* the og9 "OpenACC Profiling Interface
(incomplete)" backport that it relates to.
And, in addition to that, I pushed the wrong (incomplete) version of my fix.
libgomp/
* oacc-init.c (acc_init_1): Move other 'acc_init_state' logic to
where it belongs.
Diffstat (limited to 'libgo/go/sync')
0 files changed, 0 insertions, 0 deletions