As an aside, it is really interesting to see a computational package that, while supporting multiple GPU vendors, was first vetted on AMD, not NVidia. It is encouraging to see ROCM finally shaking off its reputation for poor support.
The vendor-agnostic GPU approach via KernelAbstractions
is great to see. The Vulkan compute path is underrated
for this — it runs on AMD, NVIDIA, and Intel without
needing ROCm or CUDA, just whatever driver ships with
the GPU.
Re: the compilation latency discussion — it's a real
tension. JIT gives you expressiveness but kills startup.
AOT gives you instant start but limits flexibility.
Interesting that most GPU languages went JIT when the
GPU itself runs pre-compiled SPIR-V/PTX anyway.
mr_octopus|10 days ago
Re: the compilation latency discussion — it's a real tension. JIT gives you expressiveness but kills startup. AOT gives you instant start but limits flexibility. Interesting that most GPU languages went JIT when the GPU itself runs pre-compiled SPIR-V/PTX anyway.
simondanisch|11 days ago