News for hackers. Stuff that matters.
Re:Integer Overflow Bug in Boeing 787 Dreamliner by Dylan16807 on Saturday May 02, 2015 @08:46AM (#9476855)
3/4 of that 15M is drivers and filesystems you won't be using, and this is not including the entertainment systems.

They should be able to keep it under 10M lines pretty easily if they actually cared about bloat.

Re:Integer Overflow Bug in Boeing 787 Dreamliner by CHY872 on Saturday May 02, 2015 @09:00AM (#9476885)
A complicating factor is that you really should include your compiler as part of your codebase (if you're doing lots of formal method work, you will usually do it on the source code, and the compiler can invalidate all of the guarantees you carefully program in), and this will be millions of lines of code (where you can't simply factor a tonne out).

Think GCC 5 is about 15 million or so now.

Re:Integer Overflow Bug in Boeing 787 Dreamliner by oldmanjay on Saturday May 02, 2015 @12:45PM (#9477643)
it's always easy when you're not the one making the changes on the system you don't understand. is there a name for that? I feel like it's a common enough thing people do that it should have a catchy name.
Re:Integer Overflow Bug in Boeing 787 Dreamliner by Dylan16807 on Saturday May 02, 2015 @04:01PM (#9478350)
Eh. To say that something that used to be mechanical should be possible with a mere few million lines of code seems pretty obvious to me.

Or compare to the Apollo missions and the space shuttle being well under a million.

I'm not saying that it would be easy to redo the entire system from scratch now, I'm just saying that if it was a design goal from the start it wouldn't have been very onerous.