Document clang C status

[Quuxplusone]

Bugzilla Link	PR3034
Status	RESOLVED FIXED
Importance	P enhancement
Reported by	Török Edwin (edwin+bugs@etorok.eu)
Reported on	2008-11-09 14:01:48 -0800
Last modified on	2009-09-16 01:21:10 -0700
Version	unspecified
Hardware	PC Linux
CC	llvm-bugs@lists.llvm.org, rdivacky@freebsd.org
Fixed by commit(s)
Attachments
Blocks
Blocked by
See also

There is a C++ status page, it would be nice to have a C status.

For example:
- blockers on x86_64: var_arg not implemented in LLVM

[Quuxplusone]

I don't see how this is doable. There is no specific list of "once this is done, we are complete" and bugzilla is great for tracking specific problems.

[Quuxplusone]

Actually, I asked edwin to file this.

I don't see any reason not to have a status page similar to the C++ one showing the known issues and what we expect to work.

Regular users shouldn't need to look at bugzilla to get an idea of what works and what doesn't. Take the multiple emails to the list about designated initializers, for example.

Another useful thing to have on the page would be notable projects which we do build.

[Quuxplusone]

ok, go for it :)

[Quuxplusone]

I plan to do an experimental build of FreeBSD ports (a framework to build some 19500 programs - not all of them in C of course) with clang and post the results somewhere...

that might give some interesting data

[Quuxplusone]

I still haven't done this, but I still think it is a good idea.

What we want isn't something like the C++ page, since C is relatively complete.

However, it would be good to convey information about the compiler status (which platforms have ABI support, known working important programs, etc.) and QOI information (supported flags, warnings).

Basically, a page which should answer the "can I expect to use clang as a working compiler" question for users.

[Quuxplusone]

I've not done this long enough that so much stuff works its unneeded. Most known missing stuff is documented in the users manual.