Comments (2)
I was thinking about this recently actually - I was thinking we would have bindgens for all the major versions in the repo, and add feature flags for which one to activate.
E.g. you'd put cudarc = { version = "...", default-features = false, features = ["cuda-12.1"] }
And then each of the different bindgens would only be activated for it's specific version.
Thoughts?
from cudarc.
I think that’s probably a reasonable approach, although linking would still use the version of CUDA present on the machine, regardless of the feature flag, I think?
There may be some parts of the safe API that need to be modified or disabled if they depend on code from certain versions, and since you can’t (at least last time I looked at something like this) have a <=
operator on feature flags in a cfg macro, it can get a little unwieldy to specify as versions grow. Possibly solvable with some indirection in build.rs? This issue would still exist even if bindgen reran against the locally installed CUDA, too.
from cudarc.
Related Issues (20)
- Error searching for cublasHgemmStridedBatched HOT 3
- Fully static binaries HOT 1
- Discovering the cuda libraries with dynamic loading HOT 3
- `CudaSlice` equivalent of `Slice::split_at_mut`
- building error inside official cuda docker image for 11.4.3 version
- Unsupported cuda toolkit version: `12050`. Please raise a github issue.
- Are there any break changes soon? HOT 1
- Issue for building my rust application with cudarc v0.11.1 (Unsupported cuda toolkit version: `10010`) HOT 1
- Unable to find curand lib under the names ... HOT 1
- how to specify the following features cuda-version-from-build-system, cuda-12040, cuda-12030, cuda-12020, cuda-12010, cuda-12000, cuda-11080, cuda-11070 HOT 3
- Error: unsupported CUDA toolkit 11.5 HOT 4
- Unable to find nvrtc lib under the names ["nvrtc", "nvrtc64", "nvrtc64_12", "nvrtc64_125", "nvrtc64_125_0", "nvrtc64_120_5", "nvrtc64_10"]. Please open GitHub issue. HOT 1
- Safe API call to get device name and compute capability? HOT 2
- CUDA_ERROR_NO_DEVICE "no CUDA-capable device is detected" HOT 1
- Unable to find cuda lib under the names ["cuda", "nvcuda"] on WSL HOT 1
- Is there a way to get this to compile on a Mac? HOT 3
- Unified memory support HOT 1
- In-Place Reduction for NCCL HOT 1
- Cannot find cudnn libs/headers HOT 2
- Not able to include <stddef.h> + etc. when compiling? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cudarc.