You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/2025-11-13-1763027191.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,5 +39,5 @@ For fusion, PolyBlocks uses a Polyhedral slicing-based approach in the affine pa
39
39
40
40
Some other random notes:
41
41
- User-facing API: TensorRT-style AOT compiled engine files, or Torch/Mojo/PolyBlocks-style JIT compilers inside Python, or in between (e.g. TensorRT-RTX).
42
-
- For the host-side code (i.e. the code that talks to the driver), it might be a good idea to generate C++ code that people can compile themselves (for power users). But this would add more hoops for the user to jump through, so this might be an option?
42
+
- For the host-side code (i.e. the code that talks to the driver), it might be a good idea to generate C++ code that people can compile themselves (for power users). But this would add more hoops for the user to jump through, so maybe this might be just an option?
43
43
- Quantization hardware-awareness in the compiler is important, so that it can factor that in during tiling and memory layout.
0 commit comments