From: Nathan Sidwell <nathan@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [gomp4] expand acc_on_device earlier
Date: Mon, 03 Aug 2015 12:00:00 -0000 [thread overview]
Message-ID: <55BF57E4.3050005@codesourcery.com> (raw)
In-Reply-To: <874mkgob6j.fsf@kepler.schwinge.homeip.net>
On 08/03/15 07:37, Thomas Schwinge wrote:
> Hi!
>
> On Sun, 2 Aug 2015 21:23:30 -0400, Nathan Sidwell <nathan@acm.org> wrote:
>> I've committed this to gomp4 branch. It expands the acc_on_device builtin
>> earlier in the new oacc_xform pass. This will allow more optimization earlier on.
>
> Thanks!
>
>> The existing expansion point now only needs to deal with the host-side case.
>
> Actually, no; committed to gomp-4_0-branch in r226498:
Please clarify. This suggests a logic fault elsewhere.
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2015-08-03 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 1:23 Nathan Sidwell
2015-08-03 11:37 ` Thomas Schwinge
2015-08-03 12:00 ` Nathan Sidwell [this message]
2015-08-03 12:41 ` Thomas Schwinge
2015-08-03 12:03 ` Thomas Schwinge
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=55BF57E4.3050005@codesourcery.com \
--to=nathan@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).