Re: [PATCH] OpenACC "present" subarrays: runtime API return value and unmapping fixes

2019-12-09 Thread Thomas Schwinge
Hi! On 2019-11-14T17:02:02+0100, I wrote: > [...] I couldn't really find wording in the > OpenACC specification that explicitly permits such things. But given > that, for example, in OpenACC 2.7, 3.2.20. "acc_copyin", 'acc_copyin' is > described to be "equivalent to the 'enter data' directive

Re: [PATCH] OpenACC "present" subarrays: runtime API return value and unmapping fixes

2019-11-14 Thread Thomas Schwinge
Hi Julian! On 2019-11-09T01:04:21+, Julian Brown wrote: > This patch fixes an issue I noticed when investigating an answer > for Thomas's question about device pointer return values in: > > https://gcc.gnu.org/ml/gcc-patches/2019-10/msg02260.html > > It looks to me like the return value for

[PATCH] OpenACC "present" subarrays: runtime API return value and unmapping fixes

2019-11-08 Thread Julian Brown
Hi, This patch fixes an issue I noticed when investigating an answer for Thomas's question about device pointer return values in: https://gcc.gnu.org/ml/gcc-patches/2019-10/msg02260.html It looks to me like the return value for the present case is wrong in the existing code: in case of a