public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: OpenMP patch ping
Date: Fri, 27 Nov 2020 17:09:06 +0100	[thread overview]
Message-ID: <bd9eb7c5-1ac9-60a2-503d-2a00c18e4879@codesourcery.com> (raw)

OpenMP-related patch pings:

Kwok's:
* Re: [PATCH] openmp: Implicit 'declare target' for C++ static initializers
   https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559624.html
* RFC:
   Nested declare target support
   https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559758.html

Chung-Lin's:
* [PATCH v2, OpenMP 5, C++] Implement implicit mapping of this[:1] (PR92120)
   https://gcc.gnu.org/pipermail/gcc-patches/2020-November/558975.html

My:
* [Patch] OpenMP: C/C++ parse 'omp allocate'
   https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559930.html

If you have a comment to Julian's
* Re: [PATCH] nvptx: Cache stacks block for OpenMP kernel launch
   https://gcc.gnu.org/pipermail/gcc-patches/2020-November/559044.html

Tobias

-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter

             reply	other threads:[~2020-11-27 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 16:09 Tobias Burnus [this message]
2020-12-03 15:43 ` OpenMP patch ping ** 2 Tobias Burnus
2022-08-16 17:28 OpenMP patch ping Tobias Burnus
2022-09-06 15:01 ` Tobias Burnus
2022-11-24 12:01 OpenMP Patch Ping Tobias Burnus
2023-01-10 11:37 Tobias Burnus

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=bd9eb7c5-1ac9-60a2-503d-2a00c18e4879@codesourcery.com \
    --to=tobias@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).