Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use driver API error enum values whenever applicable #306

Closed
eyalroz opened this issue Mar 24, 2022 · 0 comments
Closed

Use driver API error enum values whenever applicable #306

eyalroz opened this issue Mar 24, 2022 · 0 comments
Assignees
@eyalroz
Labels
resolved-on-development task

Comments

@eyalroz
Copy link
Owner

eyalroz commented Mar 24, 2022

Our named errors use the Runtime API error enum values whenever they exist, since originally we only wrapped the runtime API. This actually doesn't matter as of CUDA 10.2 at least, since NVIDIA aligned the driver and runtime error codes to use the same numbers for the same errors - but for earlier versions of CUDA this was not the case. So, in order to restore compatibilty with them (see #304), and seeing how we now use driver API calls whenever possible, we should use the driver API error enum values as much as possible.
@eyalroz eyalroz added the task label Mar 24, 2022
@eyalroz eyalroz self-assigned this Mar 24, 2022
eyalroz added a commit that referenced this issue Mar 24, 2022
@eyalroz
Fixes #304, #305, #306:
d24ae5b 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
eyalroz added a commit that referenced this issue Mar 24, 2022
@eyalroz
Fixes #305, #306, regards #304.
527b808 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
* Now (apparently) fully-compatible with CUDA 9.2.
eyalroz added a commit that referenced this issue Mar 24, 2022
@eyalroz
Fixes #305, #306, regards #304.
fe41171 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
* Now (apparently) fully-compatible with CUDA 9.2.
eyalroz added a commit that referenced this issue Mar 24, 2022
@eyalroz
Fixes #305, #306, regards #304.
d819872 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
* Now (apparently) fully-compatible with CUDA 9.2.
eyalroz added a commit that referenced this issue Mar 24, 2022
@eyalroz
Fixes #305, #306, regards #304.
7e63ac9 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
* Now (apparently) fully-compatible with CUDA 9.2.
eyalroz added a commit that referenced this issue Mar 24, 2022
@eyalroz
Fixes #305, #306, regards #304.
6dde596 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
* Renamed some named errors for clarity, based on their Doxygen comment in the CUDA headers.
* Now (apparently) fully-compatible with CUDA 9.2.
eyalroz added a commit that referenced this issue Mar 24, 2022
@eyalroz
Fixes #305, #306, regards #304.
1d63770 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
* Renamed some named errors for clarity, based on their Doxygen comment in the CUDA headers.
* Now (apparently) fully-compatible with CUDA 9.2.
eyalroz added a commit that referenced this issue Mar 24, 2022
@eyalroz
Fixes #305, #306, regards #304.
f782a22 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
* Renamed some named errors for clarity, based on their Doxygen comment in the CUDA headers.
* Now (apparently) fully-compatible with CUDA 9.2.
@eyalroz eyalroz closed this as completed May 16, 2022
eyalroz added a commit that referenced this issue Jun 20, 2022
@eyalroz
Fixes #305, #306, regards #304.
8b3e93b 
* Now using CUDA driver API error enum values wherever possible.
* Added all missing CUDA driver and runtime API error enum values to our own named error enum.
* Renamed some named errors for clarity, based on their Doxygen comment in the CUDA headers.
* Now (apparently) fully-compatible with CUDA 9.2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eyalroz eyalroz

Labels
resolved-on-development task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eyalroz