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 libgomp/108098] OpenMP/nvptx reverse offload execution test FAILs
Date: Thu, 15 Dec 2022 09:09:03 +0000	[thread overview]
Message-ID: <bug-108098-4-n40twjpuru@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108098-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #0)
>     $ nvidia-smi
>     [...]
>     | NVIDIA-SMI 440.33.01    Driver Version: 440.33.01    CUDA Version: 10.2
>     [...]
>     |   0  Tesla K80  [...]
>     [...]
>     |   1  Tesla K80  [...]
> 

I'm not sure if it matters for triggering this problem, but if I look at this
board at nvidia drivers download and select cuda 10.2 and production branch, I
get :
...
version:        440.118.02
Release Date:   2020.9.30
...

Then using the "Beta and Older Drivers" I find the version you're using is:
...
version: 440.33.01
Release date:  November 19, 2019
...

Please always use the latest drivers when reporting a problem.

  reply	other threads:[~2022-12-15  9:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 11:48 [Bug libgomp/108098] New: " tschwinge at gcc dot gnu.org
2022-12-15  9:09 ` vries at gcc dot gnu.org [this message]
2022-12-16  9:40 ` [Bug libgomp/108098] " tschwinge at gcc dot gnu.org
2022-12-16 13:13 ` burnus at gcc dot gnu.org
2022-12-16 15:06 ` burnus at gcc dot gnu.org
2023-05-05  9:28 ` cvs-commit at gcc dot gnu.org
2023-05-08 21:15 ` cvs-commit at gcc dot gnu.org
2023-05-08 21:16 ` burnus 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-108098-4-n40twjpuru@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).