On 01/22/2016 09:36 AM, Jakub Jelinek wrote:
I think it is a bad idea to go against what the user wrote. Warning that some code might not be efficient? Perhaps (if properly guarded with some warning option one can turn off, either on a per-source file or using pragmas even more fine grained). But by default not offloading? That is just wrong.
I'm leaning more towards Thomas' side of the argument. The kernels construct is a hint, a "do your best" request to the compiler. If the compiler sees that it can't parallelize a loop inside a kernels region, it's probably best not to offload it.
Bernd
