The One-Line Lie That Crashes Google's AI Compiler (a DoS in XLA)
I found a way to crash Google's AI compiler with a single malformed line of text - by handing it a description that contradicts itself. Instead of noticing, it believed both halves at once, then fell over. Let me explain in plain English. What is XLA? When you run a modern AI model - in TensorFlow, JAX, or the giant models behind today's chatbots - something has to turn that model into fast code for GPUs and TPUs. That something is XLA , Google's AI compiler. To do its job it reads an internal text format called HLO - think of it as the compiler's notebook. Engineers and tools pass HLO around as text all the time: to reproduce bugs, run tests, and feed the compiler work. And reading text from somewhere else is exactly where software tends to trip. The bug: two numbers that were allowed to disagree Big models don't fit on one chip, so XLA splits the work across many devices. The HLO text describes this using two separate pieces : a shape (say “2 by 2”...
