Try switching from rustacuda to cust #23
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
rustacuda
is no longer maintained, and includes all ofrustacuda
and most of the custom patches we are using inrust-cuda
.However, the following incompatibilities remain:
cust_core::DeviceCopy
now hasCopy
as a supertrait. This is both too weak and too strong forrust-cuda
. There is no workaround. Ifcust
doesn't change this requirement, no migration can occur.DeviceCopy
should not requireCopy
Rust-GPU/Rust-CUDA#124Stream::wait_event
takes an ownedEvent
andEvent
s cannot be cloned or inspected. This could be fixed by falling back to raw FFI for all usages. wait_event method in Stream Rust-GPU/Rust-CUDA#110Stream::add_callback
no longer provides access to the current stream status. The callback might just not be scheduled anymore if an error occurred (which could result in a never-resolving async future), or do something even worse. This could be fixed by falling back to raw FFI. https://stackoverflow.com/questions/56448390/how-to-recover-from-cuda-errors-when-using-cudalaunchhostfunc-instead-of-cudastr