One of the many reasons why LLVM is taking off is because it provides an API that lets programs hook into the compiler, which means IDEs can deeply integrate with the compiler. For example, IDEs can highlight errors based on where the compiler says errors are instead of having to run its own parser for the language.
Why doesn't gcc have this feature?
Well, it was proposed, but it was shot down because RMS doesn't want proprietary tools to be able to hook into gcc. In fact, gcc was deliberately designed as a monolithic application with no API specifically to keep third-party tools away from it.
So yet another reason why people are moving away from gcc is because llvm/clang enables you to have better development tools. GNU is being killed by its own religion.
The speaker talks about copyleft and how it's dying, and mentions that he's certain the gcc will one day become irrelevant and die to llvm, due to llvm's commercial support and traction.
The end result being the savannah turning into a reservation.
I enjoy free software, but it is painful to think that I might not be able to use Emacs with software that I consider to be equally free (LLVM) due to political strategies. I know RMS has been through enough of the embrace-extend-extinguish era to be suspicious, but given the quality of free toolchains today and the surrounding communities, I have doubts of this history repeating itself in LLVM.
[1] http://lists.gnu.org/archive/html/emacs-devel/2015-02/msg003...