From: Nathan Sidwell <nathan@acm.org>
To: Cesar Philippidis <cesar_philippidis@mentor.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
Thomas Schwinge <THOMAS_SCHWINGE@mentor.com>
Subject: Re: [gomp4] Redesign oacc_parallel launch API
Date: Thu, 06 Aug 2015 19:51:00 -0000 [thread overview]
Message-ID: <55C3BAB8.2090201@acm.org> (raw)
In-Reply-To: <55C38C5D.6040602@mentor.com>
On 08/06/15 18:33, Cesar Philippidis wrote:
> Looking at set_oacc_fn_attrib, it appears that const values are also
> considered dynamic. See the attached test case more more info. Is that
> the expected behavior? If not, I could take a look at this after I
> finished my reduction patch.
It's annoying that the offload call is happening too early for that kind of
constant propagation. But I guess it might have been propagated by the time we
get to oacc_xform. And hence that could optimize there.
Anyway, a thing to notice but not get distracted by.
nathan
prev parent reply other threads:[~2015-08-06 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 17:11 Nathan Sidwell
2015-07-28 17:46 ` Nathan Sidwell
2015-07-29 9:57 ` Thomas Schwinge
2015-07-29 12:43 ` Nathan Sidwell
2015-07-29 22:14 ` Nathan Sidwell
2015-07-30 14:46 ` Nathan Sidwell
2015-07-30 15:05 ` Thomas Schwinge
2015-08-06 16:33 ` Cesar Philippidis
2015-08-06 19:51 ` Nathan Sidwell [this message]
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=55C3BAB8.2090201@acm.org \
--to=nathan@acm.org \
--cc=THOMAS_SCHWINGE@mentor.com \
--cc=cesar_philippidis@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).