News for hackers. Stuff that matters.
Re:Clang vs. GCC – code coverage checking by rkday on Sunday April 03, 2016 @03:32AM (#11415297)
I can see that it wouldn't always be ideal, but on this (admittedly relatively niche) codebase - core telephone network infrastructure, which we only support on Ubuntu and which we build with GCC - the kind of clang/MSVC incompatibilities you talk about aren't a problem, and the reliability requirements are high enough that it's worth having CI check for 100% test coverage.

I think it's a question of field rather than philosophy - someone else in this thread said they do the same thing in avionics.

Re:Clang vs. GCC – code coverage checking by Too on Sunday April 03, 2016 @09:20AM (#11415999)
Claiming coverage has anything to do with reliability is just fooling yourself, at least if it's done on line or branch level. Will your 100% line coverage catch the divide by zero bug in this function?

    int foo(int x)
    {
        return 1 / (5 - x);
    }