You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
See discussion in #1743, we have an allocation_handle_type enum that re-exports enum values from cudart. In the past we copied values because the symbols didn't appear in cudart 11.2. It may be that they now exist in all supported versions.
This would mean that we don't accidentally end up with mismatching values between cudart and rmm. One hopes that the enum values are fowards compatible forever, but ...
The text was updated successfully, but these errors were encountered:
Yes, this is a good idea. For any enum values that are now present in all supported CUDA versions, we can do this. That would mean CUDA 11.2+ for sure, and possibly 11.4+. (We currently have some inconsistency in RMM around what our minimum CUDA version really is.)
Is your feature request related to a problem? Please describe.
See discussion in #1743, we have an
allocation_handle_type
enum that re-exports enum values from cudart. In the past we copied values because the symbols didn't appear in cudart 11.2. It may be that they now exist in all supported versions.This would mean that we don't accidentally end up with mismatching values between cudart and rmm. One hopes that the enum values are fowards compatible forever, but ...
The text was updated successfully, but these errors were encountered: