From: Cesar Philippidis <cesar@codesourcery.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>, Tom de Vries <tdevries@suse.de>
Subject: [patch] various OpenACC reduction enhancements
Date: Fri, 29 Jun 2018 18:20:00 -0000 [thread overview]
Message-ID: <ae587152-072d-52b0-0129-99de0ed40d03@codesourcery.com> (raw)
The following patch set includes various OpenACC reduction enhancements
present in og8. These include the following individual og8 commits:
* (4469fc4) [Fortran] Permit reductions in gfc_omp_clause_copy_ctor
* (704f1a2) [nxptx, OpenACC] vector reductions
* (8a35c89) [OpenACC] Fix a reduction bug involving
GOMP_MAP_FIRSTPRIVATE_POINTER variables
* (16ead33) [OpenACC] Update error messages for c and c++ reductions
* (65dd9cf) Make OpenACC orphan gang reductions errors
* (5d60102) [PR80547] Handle parallel reductions explicitly
initialized by the user
The nvptx vector reduction enhancement is a prerequisite for the
forthcoming variable-length patches.
This patch as a whole is somewhat large, so I've split it into three
pieces, 1) ME and nvptx changes, FE changes, and test cases. I'll reply
to this message with the individual patches.
Thanks,
Cesar
next reply other threads:[~2018-06-29 18:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 18:20 Cesar Philippidis [this message]
2018-06-29 18:22 ` [patch] various OpenACC reduction enhancements - ME and nvptx changes Cesar Philippidis
2018-10-05 14:09 ` Tom de Vries
2018-10-30 20:09 ` Cesar Philippidis
2018-12-04 12:29 ` Jakub Jelinek
2018-12-04 15:54 ` Tom de Vries
2018-12-13 15:56 ` Julian Brown
2018-06-29 18:23 ` [patch] various OpenACC reduction enhancements - FE changes Cesar Philippidis
2018-12-04 12:57 ` Jakub Jelinek
2018-12-13 14:12 ` Julian Brown
2018-12-18 13:06 ` Jakub Jelinek
2018-06-29 18:38 ` [patch] various OpenACC reduction enhancements - test cases Cesar Philippidis
2018-12-04 12:59 ` Jakub Jelinek
2018-12-13 14:14 ` 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=ae587152-072d-52b0-0129-99de0ed40d03@codesourcery.com \
--to=cesar@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tdevries@suse.de \
/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).