public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kwok Cheung Yeung <kcy@codesourcery.com>
To: Tom de Vries <tdevries@suse.de>, GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	Jakub Jelinek <jakub@redhat.com>,
	Catherine Moore <clm@codesourcery.com>
Subject: [PING] Re: [PATCH] nvptx: Add support for subword compare-and-swap
Date: Tue, 4 Aug 2020 15:56:40 +0100	[thread overview]
Message-ID: <3d7c1ca9-47a1-c5b8-fdf1-6f864e9d749d@codesourcery.com> (raw)
In-Reply-To: <8097cf6c-0044-77e6-d216-2abd63779754@codesourcery.com>

Hello

I posted a revised patchset about two weeks ago at:

https://gcc.gnu.org/pipermail/gcc-patches/2020-July/550291.html

Are you able to take a look at it?

Thanks

Kwok

  reply	other threads:[~2020-08-04 14:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:28 Kwok Cheung Yeung
2020-06-23 16:44 ` Thomas Schwinge
2020-06-23 16:51   ` Jakub Jelinek
2020-06-30 16:35     ` Kwok Cheung Yeung
2020-06-24 11:13   ` Kwok Cheung Yeung
2020-06-30 14:37   ` Tom de Vries
2020-07-01 14:28 ` Tom de Vries
2020-07-15 19:08   ` Kwok Cheung Yeung
2020-07-20 13:19   ` Kwok Cheung Yeung
2020-08-04 14:56     ` Kwok Cheung Yeung [this message]
2020-08-13  9:27     ` Tom de Vries
2020-09-01 11:41       ` [patch][nvptx] libgomp: Split testcase in order to XFAIL __sync_val_compare_and_swap_16 (was: [PATCH] nvptx: Add support for subword compare-and-swap) Tobias Burnus
2020-09-01 12:58         ` Tom de Vries
2020-09-02  7:56           ` Tom de Vries
2020-09-02 10:22             ` [RFC][nvptx, libgomp] Add 128-bit atomic support Tom de Vries
2020-09-02 10:44               ` Jakub Jelinek
2020-09-02 11:30                 ` Tobias Burnus
2020-09-02 11:48                 ` Tom de Vries
2020-09-11 14:24                   ` Tom de Vries
2020-09-11 14:25                     ` Tom de Vries
2020-09-11 14:48                       ` Andrew Stubbs
2020-09-11 15:03                         ` tdevries
2020-09-11 15:29                           ` Tobias Burnus
2020-09-11 14:37                     ` Jakub Jelinek

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=3d7c1ca9-47a1-c5b8-fdf1-6f864e9d749d@codesourcery.com \
    --to=kcy@codesourcery.com \
    --cc=clm@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=tdevries@suse.de \
    --cc=thomas@codesourcery.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).