4 ms·
Looks interesting. For someone already comfortable with Triton, what's the strongest argument for choosing cuTile Rust instead? Is the main differentiator the
by wizenheimer 3mo ago
Looks interesting. For someone already comfortable with Triton, what's the strongest argument for choosing cuTile Rust instead?
Is the main differentiator the ownership-based safety model, tighter integration with Rust ecosystems, or idk are there workloads where the Tile IR pipeline has advantages beyond language ergonomics?
- melihelibol 3mo agoYes, the ownership-based safety model and tight Rust integration, plus a pretty fleshed-out host-side tensor API for different workloads (sync, async, replayable CUDA graphs). Though Triton's a Python DSL, so there's no official Triton Rust to do an apples-to-apples comparison. Being pointer-based, it's unclear how one would reason about memory safety and data-race freedom. As a point-of-comparison, cutile-rs supports both pointers and tensors. We're only able to statically reason about safety when folks operate on tensors directly. The pointer path remains unsafe.