Posted in static-analysis on January 21st, 2010 2 Comments »
Mozilla has static analyses built into the buildsystem that can be turned on with –with-static-checking= flag. The analyses live in xpcom/analyses directory. The testcases (aka documentation) are in xpcom/tests/static-checker. Analyses are implemented in either Dehydra or Treehydra and run within a patched GCC 4.3. The currently landed checks are: final.js: Java-like “final” keyword for C++ [...]
Posted in startup on January 19th, 2010 26 Comments »
Hunting Down Mythical “Slowness” I recently met a developer who used Chromium instead of Firefox. Chromium’s superior startup speed was his reason for using it.This got me excited because said developer was running Linux, so it was relatively easy to measure cold startup and get a complete IO breakdown. Turned out Firefox took roughly 23 [...]
Posted in dehydra, static-analysis on January 4th, 2010 Comments Off
Cool thing about static analysis is that you can ask painful-for-humans questions about your codebase AND have them answered. Here are two that got answered by Ehren: Where do function bodies continue after return statements (ie obviously dead/broken code)? Bug 535646. How many functions in Mozilla could/should be marked static? Bug 536427. Awesome!
Posted in startup on January 4th, 2010 7 Comments »
I did some digging to figure out if one can setup cold-startup testing in Windows 7 without nasty hacks. My conclusion is: sorta-kinda. The Good – Most of the Ingredients Are Present I haven’t actively used Windows since pre-XP days. It looks like it has come a long way since then: there is now a [...]
