public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cesar Philippidis <cesar@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [gomp4] backport misc OMP 4.5 changes from trunk
Date: Wed, 05 Apr 2017 14:03:00 -0000	[thread overview]
Message-ID: <25ae131b-6081-f339-2927-fe2a62a2c8c1@codesourcery.com> (raw)
In-Reply-To: <87lgs52tu7.fsf@euler.schwinge.homeip.net>

On 03/16/2017 07:13 AM, Thomas Schwinge wrote:

>> --- a/gcc/gimplify.c
>> +++ b/gcc/gimplify.c
> 
>> @@ -6636,9 +6596,9 @@ gimplify_scan_omp_clauses (tree *list_p, gimple_seq *pre_p,
>>    ctx = new_omp_context (region_type);
>>    ctx->clauses = *list_p;
>>    outer_ctx = ctx->outer_context;
>> -  if (code == OMP_TARGET && !(lang_GNU_Fortran () && !(region_type & ORT_ACC)))
>> +  if (code == OMP_TARGET)
>>      {
>> -      if (!lang_GNU_Fortran () || region_type & ORT_ACC)
>> +      if (!lang_GNU_Fortran ())
>>  	ctx->target_map_pointers_as_0len_arrays = true;
>>        ctx->target_map_scalars_firstprivate = true;
>>      }
> 
> Is it intentional that you're now no longer enabling
> target_map_pointers_as_0len_arrays for Fortran OpenACC regions?  If
> that's not intentional, then I guess we're missing some tree-dump
> scanning test cases to verify the expected behavior?

I took a look back at my notes, and it appears that I was working on
optimizing data movement when I did this backport. This should have been
separate patch.

If you want, I can revert it. Otherwise, I'll wait until we after we
update the semantics of the data clauses to match the OpenACC 2.5 spec
prior to creating test cases to scan for tree dumps.

Cesar


  reply	other threads:[~2017-04-05 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 11:42 [committed] Partial OpenMP 4.5 fortran support Jakub Jelinek
2017-03-15 14:21 ` [gomp4] backport misc OMP 4.5 changes from trunk Cesar Philippidis
2017-03-16 14:13   ` Thomas Schwinge
2017-04-05 14:03     ` Cesar Philippidis [this message]
2017-05-17 11:48   ` Thomas Schwinge
2023-10-24  8:55 ` OpenMP/Fortran: Group handling of 'if' clause without and with modifier (was: [committed] Partial OpenMP 4.5 fortran support) Thomas Schwinge
2023-10-24  9:09   ` OpenMP/Fortran: Group handling of 'if' clause without and with modifier Tobias Burnus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=25ae131b-6081-f339-2927-fe2a62a2c8c1@codesourcery.com \
    --to=cesar@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=thomas@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).