From: Bernd Schmidt <bschmidt@redhat.com>
To: Nathan Sidwell <nathan@acm.org>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ptx] partitioning optimization
Date: Wed, 11 Nov 2015 12:06:00 -0000 [thread overview]
Message-ID: <56432F50.6000208@redhat.com> (raw)
In-Reply-To: <564270D6.6090303@acm.org>
On 11/10/2015 11:33 PM, Nathan Sidwell wrote:
> I've committed this patch to trunk. It implements a partitioning
> optimization for a loop partitioned over both vector and worker axes.
> We can elide the inner vector partitioning state propagation, if there
> are no intervening instructions in the worker-partitioned outer loop
> other than the forking and joining. We simply execute the worker
> propagation on all vectors.
Patch LGTM, although I wonder if you really need the extra option rather
than just optimize.
> I've been unable to introduce a testcase for this. The difficulty is we
> want to check an rtl dump from the acceleration compiler, and there
> doesn't appear to be existing machinery for that in the testsuite.
> Perhaps something to be added later?
What's the difficulty exactly? Getting a dump should be possible with
-foffload=-fdump-whatever, does the testsuite have a problem finding the
right filename?
Bernd
next prev parent reply other threads:[~2015-11-11 12:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 12:33 [gomp4] loop partition optimization Nathan Sidwell
2015-11-10 22:34 ` [ptx] partitioning optimization Nathan Sidwell
2015-11-10 22:45 ` Ilya Verbin
2015-11-11 13:37 ` Nathan Sidwell
2015-11-11 12:06 ` Bernd Schmidt [this message]
2015-11-11 13:59 ` Nathan Sidwell
2015-11-11 14:19 ` Bernd Schmidt
2015-11-13 20:07 ` Nathan Sidwell
2015-11-13 20:22 ` Bernd Schmidt
2015-11-23 7:47 ` Thomas Schwinge
2015-11-23 8:46 ` Jakub Jelinek
2015-11-11 17:16 ` 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=56432F50.6000208@redhat.com \
--to=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
/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).