public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Stubbs <ams@codesourcery.com>
To: Tobias Burnus <tobias@codesourcery.com>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] GCN: Implement __atomic_compare_exchange_{1, 2} in libgcc [PR102215]
Date: Wed, 9 Mar 2022 16:36:12 +0000	[thread overview]
Message-ID: <1354cbd1-259d-e946-07a6-ae72e252f4e4@codesourcery.com> (raw)
In-Reply-To: <f36f7738-dba4-0934-56b8-63775dce63ad@codesourcery.com>

On 09/03/2022 16:29, Tobias Burnus wrote:
> This shows up with with OpenMP offloading as libgomp since a couple
> of months uses __atomic_compare_exchange (see PR for details),
> causing link errors when the gcn libgomp.a is linked.
> It also shows up with sollve_vv.
> 
> The implementation does a bit copy'n'paste from the current
> implementation + calls the existing word/uint32_t-wide version
> of the atomic intrinsic. The semantic is described at
> https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html
> 
> In terms of the args, the _4 has:
> DEF_SYNC_BUILTIN (BUILT_IN_ATOMIC_COMPARE_EXCHANGE_4,
>                    "__atomic_compare_exchange_4",
>                    BT_FN_BOOL_VPTR_PTR_I4_BOOL_INT_INT,
>                    ATTR_NOTHROWCALL_LEAF_LIST)
> and the arg names try to match the GCC manual.
> 
> 
> OK for mainline?
> Tested with libgomp + sollve_vv and -march=gfx908.

OK.

Andrew

      reply	other threads:[~2022-03-09 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 16:29 [Patch] GCN: Implement __atomic_compare_exchange_{1,2} " Tobias Burnus
2022-03-09 16:36 ` Andrew Stubbs [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=1354cbd1-259d-e946-07a6-ae72e252f4e4@codesourcery.com \
    --to=ams@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tobias@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).