On Mon, Jun 24, 2013 at 08:02:26PM -0700, Justin Lebar wrote: > Under what circumstances would you expect the code coverage build to break > but all our other builds to remain green?
Anywhere you're using -Werror. I ran into this in a past life with GCC's may-use-uninitialized warning; if it's still an issue, I'd suggest doing coverage builds with -Wno-error. If you have any coverage-specific code, then also changes to anything that depends on -- but this might not be an issue for hosted programs, which don't have to bring their own runtime. And there are some assorted weirdnesses that might indirectly break something: multiprocessor performance falls off a cliff because the counters are global (unless things have change significantly since I last dealt with this), and there are interally generated references to coverage runtime functions that ignore the symbol visibility pragma and possibly other things. But Gecko might not be doing enough "interesting" low-level things to care. --Jed _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
