Actually, clang has nothing to do with gcc. LLVM's gcc frontend is called llvm-gcc ( http://llvm.org/cmds/llvmgcc.html ) which was dropped for being too high maintenance or something of the sort.
As far as I know llvm-gcc has not been dropped. On Mac OS X it is even installed alongside gcc when you install the developer tools.
Clang is making good progress. From http://clang.llvm.org/index.html:
Clang is considered to be a production quality C and Objective-C compiler when targetting X86-32 and X86-64
See DarkShikari's comment for details on what goes wrong when a compiler tries to be all things to all architectures.
--------
I should clarify. I agree with what you said below, these days GCC is an excellent compiler for x86. It's just that it's near to impossible to be so excellent for all archs.
But isn't this the whole point of LLVM? Separating the compile process into two intermediate steps, one of compiling a programming given language into an intermediate virtual machine and another of compiling that virtual machine code into a binary for the target architecture. Then each module of the LLVM can be worked on and optimized independently with little duplication of labor.
So the promise of LLVM is not just being able to compile to every architecture, but to compile every language to every architecture.
Clang is still in the beggining, IIRC.