diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2021-09-28 11:38:03 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2021-09-28 11:38:03 +0200 |
| commit | 4f07769057c45ec9e751ab1c23e0fe4750102840 (patch) | |
| tree | 072fdbebc9cbf4b5dd17cd5630569e6504cf6b07 /gcc/tree-ssa-threadupdate.c | |
| parent | fb8b72ebb5b0bf40f7dfef9154c42320ce46f2a7 (diff) | |
| download | gcc-4f07769057c45ec9e751ab1c23e0fe4750102840.zip gcc-4f07769057c45ec9e751ab1c23e0fe4750102840.tar.gz gcc-4f07769057c45ec9e751ab1c23e0fe4750102840.tar.bz2 | |
openmp: Don't call omp_finish_clause on implicitly added private clauses on simd [PR102492]
The gimplifier adds implicit private clauses on SIMD constructs for local
variables in the SIMD body if they are addressable to make sure they use
the magic arrays with "omp simd array" attribute (such that each SIMD lane
has its own copy), but we actually don't need to default privatize etc. those,
the construction for them is done in the SIMD body and so is destruction.
omp_finish_clause for C++ now requires default constructor (and dtor) for private,
so that OpenMP 5.1 default(private) works, but that will never be needed on
SIMD. So, this patch just doesn't call omp_finish_clause for private on simd.
The C and Fortran langhooks don't do anything for private.
2021-09-28 Jakub Jelinek <jakub@redhat.com>
PR middle-end/102492
* gimplify.c (gimplify_adjust_omp_clauses_1): Don't call the
omp_finish_clause langhook on implicitly added OMP_CLAUSE_PRIVATE
clauses on SIMD constructs.
* g++.dg/gomp/simd-3.C: New test.
Diffstat (limited to 'gcc/tree-ssa-threadupdate.c')
0 files changed, 0 insertions, 0 deletions