From: Nathan Sidwell <nathan@codesourcery.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Cesar Philippidis <cesar_philippidis@mentor.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [gomp4] lock/unlock internal fn
Date: Wed, 23 Sep 2015 15:06:00 -0000 [thread overview]
Message-ID: <5602B4E3.4010909@codesourcery.com> (raw)
In-Reply-To: <87mvwdxlug.fsf@kepler.schwinge.homeip.net>
On 09/23/15 10:16, Thomas Schwinge wrote:
> Hi Nathan!
>
> On Wed, 23 Sep 2015 08:40:51 -0400, Nathan Sidwell <nathan@codesourcery.com> wrote:
>> On 09/23/15 05:27, Thomas Schwinge wrote:
>>> On Mon, 17 Aug 2015 15:30:16 -0400, Nathan Sidwell <nathan@acm.org> wrote:
>>>> I've committed this patch to add a new pair of internal functions. These will
>>>> be used in implementing reductions.
>>>>
>>>> They'll be emitted around reduction finalization, and implement the locking
>>>> required for the general case of combining reduction values. They may be
>>>> transformed in the oacc_xform pass, and the default behaviour is to delete them,
>>>> if there is no RTL expander. For PTX we delete them if they are at the vector
>>>> level.
>>>>
>>>> This avoids needing machine-specific builtins to expand to, and thus should
>>>> result in less backend code duplication.
>>>
>>> With the __builtin_nvptx_lock and __builtin_nvptx_unlock builtins
>>> removed, should the gcc.target/nvptx/spinlock-1.c and
>>> gcc.target/nvptx/spinlock-2.c test cases then be removed, too, or should
>>> these be re-written differently?
>>
>> confused. I don't think I remoced those locks. Certainly didn't intend to, and
>> I would have expected massive test fails if I had.
>
> You didn't remove the functionality, but you did remove the
> __builtin_nvptx_lock and __builtin_nvptx_unlock builtins (which the two
> test cases were written for), replacing them with GOACC_LOCK/GOACC_UNLOCK
> internal functions, nvptx_expand_oacc_lock_unlock.
ah, thanks. I expect even these are going to go away soon. the spinlock
testcases should be removed.
nathan
--
Nathan Sidwell
next prev parent reply other threads:[~2015-09-23 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 20:04 Nathan Sidwell
2015-09-23 10:20 ` Thomas Schwinge
2015-09-23 12:58 ` Nathan Sidwell
2015-09-23 14:49 ` Thomas Schwinge
2015-09-23 15:06 ` Nathan Sidwell [this message]
2015-09-23 16:05 ` Thomas Schwinge
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=5602B4E3.4010909@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=cesar_philippidis@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--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).