pcc is simple, but very old school and a bit contorted.
libfirm is small and clean and generates excellent code. (Despite the name, it's a complete ANSI C compiler, as well as being a LLVM-light.)
The ACK is easy to port and is a complete standalone toolchain including compilers, assemblers and linkers, but (at least on modern processors) produces code so bad that it will make you want to stab yourself in the eyes to make the pain go away.
There's a look-but-don't-touch licensed compiler called vbcc which is by far the best C compiler I've ever seen; small, easy to understand, easy to port, and produces excellent code... but the author doesn't want to release it under an open source license.
Any others?
nwcc: small, slightly unfinished, looks like it's stalled.
sparse: technically this isn't a compiler, it's a code linter --- but it contains a complete ANSI C front end and a reasonable amount of a backend and can be made to generate code without much effort. I've used it to compile C to Java and Perl. There's no optimisation layer and it's a little buggy (it's not really really intended as a compiler).
That said, in practice a large amount of C code out there is not pure standard C so if you want to be able to compile something "interesting" like e.g. a Linux kernel you'll need to implement some.
I disagree; "brevity" and "readability" are unfortunately a tradeoff, and IMO the author's version optimizing the wrong metric.
n->For.init = i; n->For.step = st; ...
This is why it is clear. Though I could change it to be better.
edit:
Compiling my parse.c file, tcc is 34 times faster than gcc -O0 and my compiler is 3-4 times faster than gcc -O0. I should make a post with the actual stats.
(It won.)
- Gcc is unreadable;
- Clang is "advanced", but not readable;
- yours and tcc are clean... But you know it's always a risk to compare yourself to Fabrice Bellard :)