cuda: name the missing entry point in load_function errors#10
Open
haixuanTao wants to merge 1 commit into
Open
cuda: name the missing entry point in load_function errors#10haixuanTao wants to merge 1 commit into
haixuanTao wants to merge 1 commit into
Conversation
A failed load_function previously surfaced as a bare DriverError with no hint of WHICH kernel was missing — the common cause being a stale prebuilt module or a shader/host build mismatch, where the missing entry's name is exactly the diagnostic you need. Add a LoadFunction error variant carrying the entry-point name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01U2n9RqmxTJb8UG5d1Sjw4W
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A failed
load_functioncurrently surfaces as a bareDriverError(CUDA_ERROR_NOT_FOUND) with no hint of which kernel was missing. The common causes — a stale prebuilt module, or a shader/host build mismatch where the host expects a kernel the module predates — are exactly the situations where the missing entry's name is the diagnostic you need (we've lost real time to this while iterating on nexus shader kernels).This adds a
LoadFunctionvariant toCudaBackendErrorcarrying the entry-point name:No behavior change on the success path;
cargo check -p khalandcargo fmt --checkclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01U2n9RqmxTJb8UG5d1Sjw4W