public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: Cesar Philippidis <cesar@codesourcery.com>,
	Thomas Schwinge	<thomas@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Jakub Jelinek	<jakub@redhat.com>
Subject: Re: [openacc] tile, independent, default, private and firstprivate support in c/++
Date: Fri, 06 Nov 2015 13:42:00 -0000	[thread overview]
Message-ID: <563CAE42.1060908@codesourcery.com> (raw)
In-Reply-To: <563C0C29.6040209@codesourcery.com>

On 11/05/15 21:10, Cesar Philippidis wrote:
> I've applied this patch to trunk. It also includes the fortran and
> template changes. Note that there is a new regression in
> gfortran.dg/goacc/combined_loop.f90. Basically, the gimplifier is
> complaining about reduction variables appearing in multiple clauses.
> E.g. 'acc parallel reduction(+:var) copy(var)'. Nathan's upcoming
> gimplifier changes should address that.
>
> Also, because of these reduction problems, I decided not to merge
> combined_loops.f90 with combined-directives.f90 yet because the latter
> relies on scanning which would fail with the errors detected during
> gimplfication. I'm planning on adding a couple of more test cases once
> acc reductions are working on trunk.

Reductions are already on trunk.  do you mean one or both of:
1) firstprivate
2) default handlinng (depends on #1)

I expect to post #1 today.  #2 (a smaller patch) may not make it today, as I 
have to rebase it on the reworking of #1 I did to remove the two enums I 
disucssed with Jakub.

nathan
-- 
Nathan Sidwell

  parent reply	other threads:[~2015-11-06 13:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 22:17 Cesar Philippidis
2015-11-04 10:24 ` Jakub Jelinek
2015-11-04 17:55   ` Cesar Philippidis
2015-11-05 16:31     ` Jakub Jelinek
2015-11-05  4:58   ` Cesar Philippidis
2015-11-05  7:29     ` Jakub Jelinek
2015-11-05 14:58       ` Cesar Philippidis
2015-11-05 12:15 ` Thomas Schwinge
2015-11-05 14:48   ` Cesar Philippidis
2015-11-05 17:02     ` Thomas Schwinge
2015-11-05 17:13       ` Nathan Sidwell
2015-11-05 17:27         ` Cesar Philippidis
2015-11-06  2:11         ` Cesar Philippidis
2015-11-06  6:50           ` Jakub Jelinek
2015-11-06 13:44             ` Nathan Sidwell
2015-11-06 13:42           ` Nathan Sidwell [this message]
2015-11-09 11:31           ` [gomp4] " Thomas Schwinge
2021-07-21 22:06           ` Thomas Schwinge
     [not found]         ` <563D0735.7070601@mentor.com>
     [not found]           ` <87h9lqaofq.fsf@schwinge.name>
2015-11-06 23:31             ` [gomp4] backport trunk FE changes Cesar Philippidis
2015-11-07 11:45               ` Combined constructs' clause splitting (was: [gomp4] backport trunk FE changes) Thomas Schwinge
2015-11-07 16:14                 ` Combined constructs' clause splitting Cesar Philippidis
2015-11-08 15:46                 ` Tom de Vries
2015-11-19  0:03                   ` Cesar Philippidis
2015-11-19  0:09                     ` Tom de Vries
2015-11-07 12:30               ` [gomp4] backport trunk FE changes Thomas Schwinge
2015-11-07 16:05                 ` Cesar Philippidis

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=563CAE42.1060908@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=cesar@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --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).