People might argue that it's a stretch (and there'd be some rationale to the argument, although it's ultimately wrong), but LLVM would be aptly considered a spl

People might argue that it's a stretch (and there'd be some rationale to the argument, although it's ultimately wrong), but LLVM would be aptly considered a split, and it's a split that has had a huge impact. Lattner begins working on LLVM, a code generator. He and his advisor publish a paper "Architecture for a Next-Generation GCC" <https://llvm.org/pubs/2003-05-01-GCCSummit2003.html https://llvm.org/pubs/2003-05-01-GCCSummit2003.html>. When he considers this work sufficiently mature, Lattner attempts to donate it to the FSF and get it into mainline GCC, but he gets rebuffed. Apple, who has taken an interest and is his employer by that point, really wants LLVM to be a thing, though, so two years later, they announce Clang and eventually turn out an entire compiler toolchain. It transforms from the original LLVM per se into what people mean when they say "LLVM" today: the work at llvm.org—which, again, all started from what was expected to be a replacement for GCC's code generator.