> > I'm of the opinion that GCC is the one implementing OpenMP as intended
>
> I'm curious: how does one arrive at this conclusion?
Basically, any implementation for which a (significant) directive becomes a
no-op is either a) not implementing the feature as intended, or b) is
implementing it f
Hi!
... with the usual caveat that I know much more about OpenACC than
OpenMP, and I know (at least a bit) more about nvptx than GCN... ;-)
On 2022-03-02T15:12:30+, "Stubbs, Andrew" wrote:
> Has anyone ever considered having GCC add the "simd" clause to offload (or
> regular) loop nests au
> -Original Message-
> From: Jakub Jelinek
> Sent: 02 March 2022 15:25
> To: Stubbs, Andrew
> Cc: gcc@gcc.gnu.org
> Subject: Re: OpenMP auto-simd
>
> On Wed, Mar 02, 2022 at 03:12:30PM +, Stubbs, Andrew wrote:
> > Has anyone ever considered havin
On Wed, Mar 02, 2022 at 03:12:30PM +, Stubbs, Andrew wrote:
> Has anyone ever considered having GCC add the "simd" clause to offload (or
> regular) loop nests automatically?
>
> For example, something like "-fomp-auto-simd" would transform "distribute
> parallel" to "distribute parallel simd
Hi Jakub, all,
Has anyone ever considered having GCC add the "simd" clause to offload (or
regular) loop nests automatically?
For example, something like "-fomp-auto-simd" would transform "distribute
parallel" to "distribute parallel simd" automatically. Loop nests that already
contain "simd" c
