News for hackers. Stuff that matters.
Re:Boringcc: Proposal for a C compiler for secure software by ZoF on Monday December 21, 2015 @03:03PM (#10773109)
This makes zero sense to me. Where would this be beneficial?

Why not just fuzz inputs if this is your goal?

Re:Boringcc: Proposal for a C compiler for secure software by tacostakohashi on Monday December 21, 2015 @03:10PM (#10773168)
That's what this is, keeping in mind that the compiler's implementation of undefined behavior is an input that should be fuzzed.

Think of, say, integer overflow. The problem is that typical compilers have a consistent (but non-standard) implementation, so it can't be fuzzed without some compiler help.

Re:Boringcc: Proposal for a C compiler for secure software by ufo on Monday December 21, 2015 @03:18PM (#10773215)
Tests can show the presence of bugs but not their absence. The idea here is to create a compiler for C (or perhaps a C dialect) so that nasty undefined behavior is guaranteed to not occur.