Repository navigation
native: each forwarded lane-backend entry calls the family's entry of the same name - #800
Merged
Merged
Conversation
… the same name The test that walks cuda_bound.vtable's fields checks that an entry is present exactly when the family gives it; a forwarder aimed at another inner entry of the same type (unspeculate at prefill, say) would still pass. This one gives the forwarders a backend that records which of its entries ran, calls each forwarded entry once, and checks the name and the count. No change outside the test.
8 tasks done
ThinkOffApp
pushed a commit
to ThinkOffApp/TensorFold
that referenced
this pull request
Oct 14, 2026
Owner
|
Thank you, @Bizuayeu. A host test checks that the native CUDA host forwards each lane-backend entry to the family's entry of the same name, once, so a forwarder can no longer call a neighbour's entry unnoticed. Your commit is in 1.0.10 under your name ( |
This was referenced Oct 14, 2026
Open
8 tasks done
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
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.
What this changes
A test, as suggested on #742: the field-walking test checks that each forwarded entry is present exactly when the
family gives it, so a forwarder aimed at another inner entry of the same type (unspeculate at prefill, say) would
still pass. This one hands
cuda_bound.vtablea backend that records which of its entries ran, calls everyforwarded entry once, and checks the name and that it ran once. No change outside the test.
Receipt
c36b536d) plus this test; one GB10 (DGX Spark, sm_121, CUDA 13.3).zig build test-cuda-host430 passed, 0 failed;zig build test579 passed, 5 skipped, 0 failed;zig fmt --checkclean;lean_check538, as main. Withunspeculate's forwarder pointed at the innerprefill,the new test fails (expected
unspeculate, the spy sawprefill) and the field-walking one still passes (24 ofthe 25
cuda_boundtests).Checklist
"draft": false, a resumed prompt equals a fresh one, and concurrent equals solo.