public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99932] OpenACC/nvptx offloading execution regressions starting with CUDA 11.2-era Nvidia Driver 460.27.04
Date: Thu, 22 Apr 2021 13:17:49 +0000	[thread overview]
Message-ID: <bug-99932-4-5Z5WZ3aLoq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99932-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #0)
> We're seeing OpenACC/nvptx offloading execution regressions (including a lot
> of timeouts) starting with CUDA 11.2-era Nvidia Driver 460.27.04.  Confirmed
> with: CUDA 11.2-era 460.27.04, 460.32.03, 460.39, 460.56, 460.67, and CUDA
> 11.3-era 465.19.01, across several variants of GPU hardware.
> 
> Explicitly (re-)confirmed good are older versions such as CUDA 9.1-era
> 390.12, and CUDA 11.1-era 455.38, 455.45.01.
> 
> Most of these are in the 'vector_length > 32' testcases, but also a few
> others.
> 

Confirmed, I see on ubuntu 18.04.5 with dirver version 460.67:
...
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
...

  reply	other threads:[~2021-04-22 13:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 10:45 [Bug target/99932] New: " tschwinge at gcc dot gnu.org
2021-04-22 13:17 ` vries at gcc dot gnu.org [this message]
2021-04-23  8:35 ` [Bug target/99932] " vries at gcc dot gnu.org
2021-04-23 12:49 ` vries at gcc dot gnu.org
2021-04-23 15:45 ` vries at gcc dot gnu.org
2021-04-24 20:27 ` vries at gcc dot gnu.org
2021-04-27  6:58 ` vries at gcc dot gnu.org
2021-12-10  6:46 ` vries at gcc dot gnu.org
2022-01-24  9:59 ` vries at gcc dot gnu.org
2022-01-24 10:04 ` vries at gcc dot gnu.org
2022-01-24 15:46 ` vries at gcc dot gnu.org
2022-01-25 10:42 ` vries at gcc dot gnu.org
2022-01-25 11:02 ` vries at gcc dot gnu.org
2022-01-25 15:00 ` vries at gcc dot gnu.org
2022-01-26 12:19 ` vries at gcc dot gnu.org
2022-01-26 12:30 ` vries at gcc dot gnu.org
2022-02-02 12:31 ` vries at gcc dot gnu.org

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=bug-99932-4-5Z5WZ3aLoq@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).