Not having to ship a toolchain (nvcc, gpucc or whatever equivalent linked as a library)?

It's gpucc, so it builds from LLVM when you enable XLA in the TF configure step.

Trying to understand: you don't want to ship a compiler library on principle, or is it some kind of product requirement, or ? There's lots of cool work to be done in the compiler space so use cases help to prioritize. :-) Thanks!

which from dev POV means having to ship a tool(chain) (for the AoT stuff)!