From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-po-10v.sys.comcast.net (resqmta-po-10v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:169]) by sourceware.org (Postfix) with ESMTPS id 60EDE38618F1 for ; Wed, 19 Aug 2020 04:35:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 60EDE38618F1 Received: from resomta-po-12v.sys.comcast.net ([96.114.154.236]) by resqmta-po-10v.sys.comcast.net with ESMTP id 8FQLkYvjudcAR8FogkACFE; Wed, 19 Aug 2020 04:35:14 +0000 Received: from [IPv6:2601:640:4100:d0a0:a4d2:aa9f:ce88:df0b] ([IPv6:2601:640:4100:d0a0:a4d2:aa9f:ce88:df0b]) by resomta-po-12v.sys.comcast.net with ESMTPSA id 8Fodki133LNDh8FofkRCMT; Wed, 19 Aug 2020 04:35:14 +0000 X-Xfinity-VMeta: sc=-100.00;st=legit Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.6\)) Subject: Re: [PATCH][testsuite, nvptx] Add effective target sync_int_long_stack From: Mike Stump In-Reply-To: <20200812135722.GA18324@delia> Date: Tue, 18 Aug 2020 21:35:10 -0700 Cc: gcc-patches@gcc.gnu.org Content-Transfer-Encoding: quoted-printable Message-Id: <2D2D9258-7E0C-45F3-B26F-2D2213962184@comcast.net> References: <20200812135722.GA18324@delia> To: Tom de Vries X-Mailer: Apple Mail (2.3445.9.6) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Aug 2020 04:35:16 -0000 On Aug 12, 2020, at 6:57 AM, Tom de Vries wrote: >=20 > The nvptx target currently doesn't support effective target = sync_int_long, > although it has support for 32-bit and 64-bit atomic. >=20 > When enabling sync_int_long for nvptx, we run into a failure in > gcc.dg/pr86314.c: > ... > nvptx-run: error getting kernel result: operation not supported on \ > global/shared address space > ... > due to a ptx restriction: accesses to local memory are illegal, and = the > test-case does an atomic operation on a stack address, which is mapped = to > local memory. >=20 > Fix this by adding a target sync_int_long_stack, wich returns false = for nvptx, > which can be used to mark test-cases that require sync_int_long = support for > stack address. >=20 > Build on nvptx and tested with make check-gcc. >=20 > OK for trunk? Ok.