Skip to content
This repository has been archived by the owner on Mar 28, 2022. It is now read-only.

missmatch in enum error values #62

Open
LuisAyuso opened this issue Jul 26, 2019 · 0 comments
Open

missmatch in enum error values #62

LuisAyuso opened this issue Jul 26, 2019 · 0 comments

Comments

@LuisAyuso
Copy link

LuisAyuso commented Jul 26, 2019

Hi there,

I am running a program which contains some error, and the Cuda runtime keeps returning
MissingConfiguration

I can see in the cuda_sys code that this enum value maps to 2, nevertheless
MissingConfiguration in the Cuda runtime maps to 52, while 2 is

    /**
     * The API call failed because it was unable to allocate enough memory to
     * perform the requested operation.
     */
    cudaErrorMemoryAllocation             =      2,
    /**
     * The device function being invoked (usually via ::cudaLaunchKernel()) was not
     * previously configured via the ::cudaConfigureCall() function.
     */
    cudaErrorMissingConfiguration         =      52

In the rust code there are no 52 nor 53 values:

    PeerAccessAlreadyEnabled = 50,
    PeerAccessNotEnabled = 51,
    DeviceAlreadyInUse = 54,
    ProfilerDisabled = 55,

I am using cuda 10.1.

  • is this version supported?
  • is this a version missmatch?
  • Should I generate the bindings myself from the Cuda header?

Cheers

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant