public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chung-Lin Tang <chunglin_tang@mentor.com>
To: Cesar Philippidis <cesar@codesourcery.com>,
	gcc-patches	<gcc-patches@gcc.gnu.org>,
	Thomas Schwinge <thomas@codesourcery.com>
Subject: Re: [gomp4] OpenACC async re-work
Date: Tue, 25 Jul 2017 15:03:00 -0000	[thread overview]
Message-ID: <8b5aab06-99a6-6cb9-475c-11e7366b5f96@mentor.com> (raw)
In-Reply-To: <3fbd22b8-e946-c391-08b3-0f9c53b849c3@codesourcery.com>

On 2017/7/25 10:09 PM, Cesar Philippidis wrote:
> On 07/25/2017 05:51 AM, Chung-Lin Tang wrote:
>> On 2017/6/29 6:31 AM, Cesar Philippidis wrote:
> 
>> Attached is the updated version of the patch, re-tested.
>>
>> Thomas, do you need some more time to look over it? Or should I commit it first?
> 
> I'm not too concerned about the profiling stuff because that should be
> considered beta quality (because it's still not fully implemented).
> 
> We'll probably need to revisit the locking stuff later, but this patch
> is OK for og7. I suspect that we may have to make other locking tweaks
> in the nvptx plugin anyway.
> 
> Cesar
> 

Patch has been committed to gomp-4_0-branch.

Chung-Lin

  reply	other threads:[~2017-07-25 15:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24  7:54 Chung-Lin Tang
2017-06-26 22:45 ` Cesar Philippidis
2017-06-27 10:56   ` Chung-Lin Tang
2017-06-28 22:31     ` Cesar Philippidis
2017-07-25 12:51       ` Chung-Lin Tang
2017-07-25 14:09         ` Cesar Philippidis
2017-07-25 15:03           ` Chung-Lin Tang [this message]
2017-10-10 18:37         ` Thomas Schwinge
2017-10-10 21: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=8b5aab06-99a6-6cb9-475c-11e7366b5f96@mentor.com \
    --to=chunglin_tang@mentor.com \
    --cc=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).