Skip to content

Fix typo #46

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 24, 2024
+2 −3
Merged

Fix typo #46

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions blog/2024-11-21-optimizing-matrix-mul/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -414,9 +414,8 @@ Testing the kernel in isolation is useful, but it does not reflect how the GPU e
it with multiple invocations across workgroups and dispatches. To test the kernel
end-to-end, I needed a test harness that simulated this behavior on the CPU.

Building the harness was straightforward due to due to Rust. By enforcing the
same invariants as the GPU I could validate the kernel under the same conditions the GPU
would run it:
Building the harness was straightforward due to Rust. By enforcing the same invariants
as the GPU I could validate the kernel under the same conditions the GPU would run it:

import { RustCpuBackendHarness } from './snippets/party.tsx';

Expand Down