public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/113513] New: [OpenMP] libgomp: cuCtxGetDevice error with OMP_DISPLAY_ENV=true OMP_TARGET_OFFLOAD="mandatory" for libgomp.c/target-52.c Date: Fri, 19 Jan 2024 23:25:50 +0000 [thread overview] Message-ID: <bug-113513-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113513 Bug ID: 113513 Summary: [OpenMP] libgomp: cuCtxGetDevice error with OMP_DISPLAY_ENV=true OMP_TARGET_OFFLOAD="mandatory" for libgomp.c/target-52.c Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: openmp, wrong-code Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org, tschwinge at gcc dot gnu.org Target Milestone: --- When using both OMP_DISPLAY_ENV=true and OMP_TARGET_OFFLOAD="mandatory", the device has to be initiated early as OMP_DEFAULT_DEVICE (either 0 or -4 = omp_invalid_device) needs to be known before printing the ICVs. On my system, this causes libgomp: cuCtxGetDevice error: unknown cuda error. That's with "CUDA Version: 12.3" and "NVIDIA RTX A1000 6GB" with --with-arch=sm_80. I am somewhat sure that I have manually tested it before; our tester wasn't able to remotely set the env vars, hence, I don't know whether it did work there or not - nor whether it is a regression, depends on CUDA, sm_xx, my card or ...
next reply other threads:[~2024-01-19 23:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-19 23:25 burnus at gcc dot gnu.org [this message] 2024-01-20 14:38 ` [Bug libgomp/113513] " burnus at gcc dot gnu.org 2024-01-22 19:45 ` 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-113513-4@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: linkBe 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).