File tree 1 file changed +3
-3
lines changed
blog/2024-11-21-optimizing-matrix-mul
1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -260,13 +260,13 @@ Porting to Rust GPU went quickly, as the kernels Zach used were fairly simple. M
260
260
the time was spent with concerns that were not specifically about writing GPU code. For
261
261
example, deciding how much to abstract vs how much to make the code easy to follow, if
262
262
everything should be available at runtime or if each kernel should be a compilation
263
- target, etc. The code is still not _ great_ as it is still blog post code!
263
+ target, etc. The code is not _ great_ as it is still blog post code!
264
264
265
265
My background is not in GPU programming, but I do have Rust experience. I joined the
266
266
Rust GPU project because I tried to use standard GPU languages and knew there must be a
267
267
better way. Writing these GPU kernels felt like writing any other Rust code (other than
268
- debugging, more later) which is a huge win to me. Not only the language itself, but the
269
- entire development experience.
268
+ debugging, more on that later) which is a huge win to me. Not only the language itself,
269
+ but the entire development experience.
270
270
271
271
## Rust-specific party tricks
272
272
You can’t perform that action at this time.
0 commit comments