From: Nathan Sidwell <nathan@codesourcery.com>
To: Bernd Schmidt <bernds@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>,
Julian Brown <julian@codesourcery.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [gomp4] Preserve NVPTX "reconvergence" points
Date: Mon, 22 Jun 2015 16:13:00 -0000 [thread overview]
Message-ID: <55883304.7060409@codesourcery.com> (raw)
In-Reply-To: <5588273C.60109@codesourcery.com>
On 06/22/15 11:18, Bernd Schmidt wrote:
> You can have a hint that it is desirable, but not a hint that it is correct
> (because passes in between may invalidate that). The OpenACC directives
> guarantee to the compiler that the program can be transformed into a parallel
> form. If we lose them early we must then rely on our analysis which may not be
> strong enough to prove that the loop can be parallelized. If we make these
> transformations early enough, while we still have the OpenACC directives, we can
> guarantee that we do exactly what the programmer specified.
How does this differ from openmp's needs to preserve parallelism on a parallel
loop? Is it more than the reconvergence issue?
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2015-06-22 16:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 14:20 Julian Brown
2015-05-28 14:59 ` Jakub Jelinek
2015-05-28 15:14 ` Thomas Schwinge
2015-05-28 15:28 ` Jakub Jelinek
2015-06-19 10:44 ` Bernd Schmidt
2015-06-19 12:32 ` Jakub Jelinek
2015-06-19 13:07 ` Bernd Schmidt
2015-06-19 14:10 ` Jakub Jelinek
2015-06-22 14:04 ` Bernd Schmidt
2015-06-22 14:25 ` Jakub Jelinek
2015-06-24 13:37 ` Bernd Schmidt
2015-06-24 14:08 ` Jakub Jelinek
2015-06-22 14:00 ` Julian Brown
2015-06-22 14:36 ` Jakub Jelinek
2015-06-22 15:18 ` Julian Brown
2015-06-22 15:33 ` Bernd Schmidt
2015-06-22 16:13 ` Nathan Sidwell [this message]
2015-06-22 16:27 ` Jakub Jelinek
2015-06-22 16:35 ` Nathan Sidwell
2015-06-22 17:54 ` Julian Brown
2015-06-22 18:48 ` Jakub Jelinek
2015-05-28 15:02 ` Richard Biener
2015-06-03 11:47 ` Julian Brown
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=55883304.7060409@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=julian@codesourcery.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).