From: Cesar Philippidis <cesar@codesourcery.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [gomp] openacc reduction cleanup
Date: Tue, 30 Jun 2015 18:07:00 -0000 [thread overview]
Message-ID: <5592D982.1020309@codesourcery.com> (raw)
This patch removes a lot of the crufty code which was necessary for an
arbitrary sized vector reductions. The new plan going forward it to fix
vector_length to a size such that vector loops don't require any
synchronization after the loop have terminated. In the case of nvptx
targets, vector_length = warp_sz, which is currently 32 threads. I'll
follow up this patch with another one which adds support for tree
reductions in vector loops in a later date.
This patch has been applied to gomp-4_0-branch.
Cesar
next reply other threads:[~2015-06-30 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 18:07 Cesar Philippidis [this message]
2015-07-01 13:45 ` 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=5592D982.1020309@codesourcery.com \
--to=cesar@codesourcery.com \
--cc=gcc-patches@gcc.gnu.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).