Repository navigation
Describe measured CUDA status and archive superseded predictions - #262
Merged
Merged
Conversation
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.
The CUDA README still says no kernel has executed on a device and presents pre-measurement predictions as current limitations, despite the retained October 7 parity and paired-throughput reports. Replace the current README with the actual scope, activation boundary, build instructions and links to those measured results. Preserve the original discussion in an explicitly historical file, including its failed reasoning.
The new text distinguishes hardware-specific results from general guarantees and notes that correcting missing FFN gate/up dispatch superseded the older bottleneck conclusion. No new benchmark or runtime change is claimed.
Validation: checked against the current Rust exports, Java driver loader and retained G1/G4 reports;
spotlessCheck build complianceCheckpasses locally, including Maven/Gradle consumer checks. Relative documentation links resolve.