Skip to content

Allow user-provided annotation for kernels generated from Program andObjectCode #1281

Open

Description

@leofang

We have examples like this today

kernel = module.get_kernel("vectorAdd<float>")

which does not tell us what args are expected on the device side, and so when launch(s, config, kernel, ...) is called we cannot do type checking for users.

Activity

  1. added this to the cuda.core backlog milestone on Nov 20, 2025
  2. leofang commented on Nov 21, 2025

    @leofang
    MemberAuthor

    During the meeting the preliminary idea is to allow users to (optionally) register

    • C/C++ types on the device side
    • Python types on the host side

    similar to what cffi does today, ex:

    cpu_prog.cdef(f"{func_sig};")

    We still want to be able to keep the fast path that Python int can be interpreted as pointer addresses.

  3. added
    cuda.coreEverything related to the cuda.core module
    featureNew feature or request
    on Nov 21, 2025
  4. removed this from the cuda.core backlog milestone on Apr 2, 2026
  5. leofang commented on May 1, 2026

    @leofang
    MemberAuthor

    After last November a lot has changed. In particular, as I mentioned in the design meeting yesterday, there is actually a way to retrieve the function signature from CUBINs via driver APIs + CUDA C++ demangler. This is now implemented in cupy/cupy#9801. I hope to reuse/migrate the infrastructure I built there back to cuda-core.

  6. added this to the cuda.core next milestone on May 1, 2026
  7. added
    P1Medium priority - Should do
    on May 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1Medium priority - Should docuda.coreEverything related to the cuda.core modulefeatureNew feature or request

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions