On 12/02/2015 02:46 PM, Jakub Jelinek wrote:
Or does the OpenACC execution model not allow anything like that, i.e. have some function with an automatic variable pass the address of that variable to some other function and that other function use #acc loop kind that expects the caller to be at the worker level and splits the work among the threads in the warp, on the array section pointed by that passed in pointer? See the OpenMP testcase I've posted in this thread.
I believe you're making a mistake if you think that the OpenACC "specification" considers such cases.
Bernd
