> The underlying projects support loading at runtime, so you could have as many AOT compiled kernel variants and load the one you want. I'm not sure I understa

> The underlying projects support loading at runtime, so you could have as many AOT compiled kernel variants and load the one you want. I'm not sure I understand. What underlying projects? The only reference to loading at runtime I see on the post is loading the AOT-compiled IR. > There is of course the warmup / stuttering problem, but that is a separate issue and (sometimes) not an issue for compute vs graphics where it is a bigger issue. It should be worth noting that Mojo itself is not JIT compiled; Mojo has a GPU infrastructure that can JIT compile Mojo code at runtime [1]. > One of the issues with GPUs as a platform is runtime probing of capabilities is... rudimentary to say the least. Also not an issue in Mojo when you combine the selective JIT compilation I mentioned with powerful compile-time programming [2]. 1. https://docs.modular.com/mojo/manual/gpu/intro-tutorial#4-compile-and-run-the-kernel https://docs.modular.com/mojo/manual/gpu/intro-tutorial#4-co... - here the kernel "print_threads" will be jit compiled 2. https://docs.modular.com/mojo/manual/parameters/ https://docs.modular.com/mojo/manual/parameters/