But note that this is not a very useful metric progress will usually cause it to drop, but it will also increase as missing Darwin functionality is added. The size of the diff between the trunk and the branch was 55,852 lines (1.9MB).

So compiler warnings aren’t an issue any more, and I won’t bother tracking them as a metric in the future. Of these, 33 are from #warning declarations, and 10 are from code generated by the Darwin ‘mig’ utility which I have no control over. The number of compiler warnings on Mac was 461. It’s now 10, and all of these are from #warning declarations that mark places where improvement need to be made to the Darwin port, but aren’t actually a problem for Linux. The number of compiler warnings on Linux was 186.This is the most important metric, and it’s improving steadily, but there’s still a long way to go. The total number of tests has gone down because some Linux-specific tests are no longer being (inappropriately) run on Mac. the number of failures went from 380 to 265. The number of regression test failures on Mac was 419/293/58/29.So almost all the Linux functionality broken by the changes has been restored. The other failure is one that also occurs on the trunk. Four of the failures are in Helgrind, the data race detector tool, which I haven’t tracked down yet. the number of failures went from 298 to 5. The number of regression test failures on Linux was: 477 tests, 220 stderr failures, 53 stdout failures, 25 post failures (which I’ll abbreviate as 477/220/53/25).Here are the current (as of r9192) values of the metrics I defined in the first post as a means of tracking progress. In that time I’ve made 85 commits to the DARWIN branch (and a similar number to the trunk). It’s been a month since I first wrote about my work on the Mac OS X port of Valgrind.

2009 macbook os x