From: Tom de Vries <tdevries@suse.de>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed][nvptx] Add uniform_warp_check insn
Date: Wed, 14 Sep 2022 11:56:14 +0200 [thread overview]
Message-ID: <72f7d022-033c-db4d-05f7-d9c85acacb97@suse.de> (raw)
In-Reply-To: <87fsgumgxh.fsf@euler.schwinge.homeip.net>
On 9/14/22 11:41, Thomas Schwinge wrote:
> Hi Tom!
>
> On 2022-02-01T19:31:27+0100, Tom de Vries via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> Hi,
>>
>> On a GT 1030, with driver version 470.94 and -mptx=3.1 I run into:
>> ...
>> FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/parallel-dims.c \
>> -DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -foffload=nvptx-none \
>> -O2 execution test
>> ...
>
> This relates to PR99932 "OpenACC/nvptx offloading execution regressions
> starting with CUDA 11.2-era Nvidia Driver 460.27.04". You've fixed that
> for GCC 12+, but testing nvptx offloading for GCC 11, GCC 10 branches on
> a system with current Nvidia Driver, we're still running into the several
> FAILs and annoying 'WARNING: program timed out' reported in PR99932.
>
> GCC 11, GCC 10 only build '.version 3.1' target libraries, and with
> "[nvptx] Add bar.warp.sync" in place (which this patch here thus only
> textually depends on), we've got good test results again.
>
> OK to push to GCC 11, GCC 10 branches the attached
> "[nvptx] Add uniform_warp_check insn"?
>
>
LGTM.
Thanks,
- Tom
next prev parent reply other threads:[~2022-09-14 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 18:31 Tom de Vries
2022-09-14 9:41 ` Thomas Schwinge
2022-09-14 9:56 ` Tom de Vries [this message]
2022-12-15 18:27 ` nvptx: Make 'nvptx_uniform_warp_check' fit for non-full-warp execution (was: [committed][nvptx] Add uniform_warp_check insn) Thomas Schwinge
2023-01-11 11:37 ` [PING] " Thomas Schwinge
2023-01-20 20:23 ` [og12] nvptx: Make 'nvptx_uniform_warp_check' fit for non-full-warp execution 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=72f7d022-033c-db4d-05f7-d9c85acacb97@suse.de \
--to=tdevries@suse.de \
--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).