[kitsunesoba]

The switch to llvm/clang was about more than just avoiding gcc… it was also about filling holes in gcc’s functionality. Swift for example is heavily rooted in llvm/clang because at least at the time, llvm/clang was capable of a lot of things that gcc simply wasn’t, and the arcane nature of gcc’s innards made it unnecessarily difficult to add missing features to. Of course, GPLv3 poses issues too, but that’s only a single factor among several in Apple’s decision to deeply invest into llvm/clang.