Hi!
To move us one small step forward:
On 2020-06-25T13:03:53+0200, I wrote:
> Ping, in particular my question about different 'GOMP_MAP_FORCE_FROM' vs.
> 'GOMP_MAP_FROM' handling.
>
> (I have not yet looked whether 'GOMP_MAP_ALWAYS_FROM' may be generate
> nowadays, given your pending front end/m
Hi Julian!
Ping, in particular my question about different 'GOMP_MAP_FORCE_FROM' vs.
'GOMP_MAP_FROM' handling.
(I have not yet looked whether 'GOMP_MAP_ALWAYS_FROM' may be generate
nowadays, given your pending front end/middle end patches.)
On 2020-05-19T17:58:16+0200, I wrote:
> On 2019-12-17T2
Hi!
On 2020-05-19T17:42:22+0200, I wrote:
> On 2019-12-17T22:02:27-0800, Julian Brown wrote:
>> --- a/libgomp/oacc-mem.c
>> +++ b/libgomp/oacc-mem.c
>
>> @@ -571,14 +570,16 @@ present_create_copy (unsigned f, void *h, size_t s,
>> int async)
>>
>>goacc_aq aq = get_goacc_asyncqueue (async
Hi Julian!
On 2019-12-17T22:02:27-0800, Julian Brown wrote:
> --- a/libgomp/oacc-mem.c
> +++ b/libgomp/oacc-mem.c
(Unhelpful diff trimmed.)
> +/* Unmap variables for OpenACC "exit data", with optional finalization
> + (affecting all mappings in this operation). */
> +static void
> +goacc_ex
Hi Julian!
On 2019-12-17T22:02:27-0800, Julian Brown wrote:
> --- a/libgomp/oacc-mem.c
> +++ b/libgomp/oacc-mem.c
(Unhelpful diff trimmed.)
> +/* Some types of (pointer) variables use several consecutive mappings, which
> + must be treated as a group for enter/exit data directives. This func
Hi Julian!
On 2019-12-17T22:02:27-0800, Julian Brown wrote:
> --- a/libgomp/oacc-mem.c
> +++ b/libgomp/oacc-mem.c
> @@ -571,14 +570,16 @@ present_create_copy (unsigned f, void *h, size_t s, int
> async)
>
>goacc_aq aq = get_goacc_asyncqueue (async);
>
> - tgt = gomp_map_vars_async
This is a rebased version of the reference-count overhaul patch last
posted here:
https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02235.html
This version omits parts of the above patch already committed upstream and
merges some recent REFCOUNT_INFINITY changes. This patch causes the newish
PR9284
