G++ still doesn't support all of the C++11 standard library so that is not entirely true. (Clang's standard library implementation, libc++, is C++11 feature complete as well)

STL is ambiguous. You mean standard library or stdlib if it must be shortened. Helpless pedantry I know but freenode's #c++ has beat this into me.

fair enough

As far as I know, libc++ is at the moment feature complete on OS X. Work still has to be done for other platforms.

You should be able to use LLVMs libc++ with GCC, just like you can currently use GNU libstdc++ with Clang.

And? It isn't like this is a competition.

There's definitely a sense of friendly competition between GCC and Clang developers.

Perhaps, but I don't see the need for the gcc did it first responses. A simple gcc and clang both have ful c11 support now would seem more appropriate is basically all I'm trying to convey.

Competition is good when it means better language support.

and better error messages!

This is totally a competition, although the bar is probably pretty low.

If Clang is feature complete, compiler and library, and GCC takes ~N years more to be feature complete, compiler and library, then Clang could win. People might say, "I'm tired of not being able to use feature X, it's been implemented in Clang for two years", drop GCC, and install Clang.