question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Rename NUMBAPRO cuda related environment variables + refactor.

See original GitHub issue

As noted in https://github.com/numba/numba/issues/2849, there are a number of NUMBAPRO prefixed environment variables still in use that could do with a name change:

NUMBAPRO_VERBOSE_CU_JIT_LOG
NUMBAPRO_CUDA_LOG_SIZE
NUMBAPRO_CUDA_DRIVER
NUMBAPRO_LIBDEVICE
NUMBAPRO_CUDALIB
NUMBAPRO_NVVM

and as suggested a NUMBA_CUDA_SDK env var that lets you specify the top-level CUDA directory and infers the rest of the paths needed would be good.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
stuartarchibaldcommented, Jul 13, 2018

@AndiH

  • Anything with NUMBAPRO is from a really long while back and needs looking at for deprecation/updating.
  • CUDA toolkit/runtime etc has changed a bit through time so some things that used to be useful/present now aren’t and the code probably exhibits these artifacts (as noted!).

Agree that NUMBA_CUDA_SDK is the thing to set, and CUDA_PATH/CUDA_ROOT could also be queried as a place to look if the env var and the default locations are fruitless, good idea.

To do the work for this, anything NUMBAPRO + CUDA related would need deprecation marks/warnings applied, then the new behaviour implemented and documented, along with a plan for final removal of the old.

0reactions
seibertcommented, May 23, 2019

Closing this issue as 0.44 contains a reworked CUDA environment detection heuristic. (See #4096 for more details.)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Release Notes — Numba 0.51.0-py3.7-linux-x86_64.egg ...
The CUDA target has more stream constructors available and a new function for compiling to PTX without linking and loading the code to...
Read more >
In-place Rename Refactoring - YouTube
In PhpStorm when you need to rename a variable, parameter, class, method, constant or goto label, you can do it in-place, right in...
Read more >
10. Release Notes — Numba 0.26.0 documentation
Issue #1127: Add a CUDA simulator running on the CPU, enabled with the NUMBA_ENABLE_CUDASIM environment variable. Issue #1086: Allow calling standard Numpy ...
Read more >
目录 - Gitee
#2879: Rename NUMBAPRO cuda related environment variables + refactor. Seems like a good idea, but need to keep old names for compat for...
Read more >
Environment Variables
The System Properties window opens. Click the Environment Variables button. Under System Variables, scroll to see the variables that have CUDA in the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found