public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Nathan Sidwell <nathan@acm.org>, Bernd Schmidt <bschmidt@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Alexander Monakov <amonakov@ispras.ru>
Subject: Ping: Re: OpenMP offloading to NVPTX: backend patches
Date: Thu, 05 May 2016 06:45:00 -0000	[thread overview]
Message-ID: <20160505064533.GV26501@tucnak.zalov.cz> (raw)
In-Reply-To: <alpine.LNX.2.20.1604201922400.14803@monopod.intra.ispras.ru>

Hi!

Now that we are in stage1, I'd like to ping this patch series from
Alexander.  As those are (mostly) patches against the nvptx backend,
they need to be reviewed by NVPTX maintainers, and are needed before the
corresponding generic OpenMP offloading and libgomp changes are reviewed.

On Wed, Apr 20, 2016 at 07:52:07PM +0300, Alexander Monakov wrote:
> Hello!
> 
> In responses to this email, I'll be posting 9 NVPTX-specific patches that are
> required for enabling OpenMP offloading.  I intend to post corresponding
> libgomp and middle-end changes that make these useful a bit later.
> 
> The patches are generated by taking a diff on amonakov/gomp-nvptx git branch,
> and cutting it up into pieces that can be reviewed separately.  I've made an
> effort to provide links to original patch submissions, which are even more
> fine-grained, and provide verbose descriptions.
> 
> In a few places there's some "leakage" where a given hunk contains stuff from
> separated patches. I hope it's obvious where it happens, and does not make
> reviewing harder.
> 
> Even though the patches are posted separately, I think committing them
> separately wouldn't be useful, i.e. I'd like to commit all at once after
> review.
> 
> Please review for trunk.

	Jakub

      reply	other threads:[~2016-05-05  6:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 16:52 Alexander Monakov
2016-05-05  6:45 ` Jakub Jelinek [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=20160505064533.GV26501@tucnak.zalov.cz \
    --to=jakub@redhat.com \
    --cc=amonakov@ispras.ru \
    --cc=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).