OpenMP auto-simd

Stubbs, Andrew Andrew_Stubbs@mentor.com
Tue Mar 8 16:47:10 GMT 2022


> > 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 for a device configured differently to the one that inspired the directive. Since I'm pretty sure that (b) is not the case I settled my opinion on (a).

Now, it may be that the original intention is flawed and the deviant implementation is superior, but that's another matter.

Andrew


More information about the Gcc mailing list