projects / gcc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: f721753) | patch
More explicit checking of which OMP constructs we're expecting, part II
authorThomas Schwinge <thomas@codesourcery.com>
Fri, 20 Nov 2020 09:41:46 +0000 (10:41 +0100)
committerThomas Schwinge <thomas@codesourcery.com>
Tue, 24 Nov 2020 09:28:04 +0000 (10:28 +0100)
commit8c3aa359ce33732273bbd61c5f9a2c607779b32e
treebc9415c3a4c19cd2bd319adab417d98203c9f571tree
parentf72175357d04b0e71d2043be48551d7904a233b6commit | diff
More explicit checking of which OMP constructs we're expecting, part II

In particular, more precisely highlight what applies generally vs. the special
handling for the current 'parloops'-based OpenACC 'kernels' implementation.

gcc/
* omp-expand.c (expand_oacc_for): More explicit checking of which
OMP constructs we're expecting.
gcc/omp-expand.c diff | blob | history