Looks like the most comprehensive list of differences between clang and gcc. I'm amazed.<p>Apparently, most differences are either because clang and gcc use different standards or interpret them differently.<p>Also, only 9% of the Debian packages have issues, meaning clang is getting more and more worth considering.
This is seriously amazing and will, certainly, improve all the codebases involved. Sylvestre and the others involved deserve a lot of good karma for this.<p>Going a step further, wouldn't it be great if all packages had automated tests that could easily be run on the 91% of the packages that were successfully built?
If there was even an easy way to get involved in OpenSource development in general - this is it. It's pretty much a list of trivial 1-line bugs to fix!
Amazing list.<p>I was frustrated that I didn't manage to figure out how to locate the results for a given package, if there were any.<p>Without that, how should I (as a package upstream owner) know if I need to fix my code, or at least analyze the results with respect to my particular package?