News for hackers. Stuff that matters.
Re:Boringcc: Proposal for a C compiler for secure software by Pxtl on Monday December 21, 2015 @03:22PM (#10773246)
Um, sounds like the most appropriate response would be a low-performance C compiler/interpreter that enforces crashes on all run-time undefined behaviors, and refuses to compile for any compile-time checkable ones.
Re:Boringcc: Proposal for a C compiler for secure software by nwmcsween on Monday December 21, 2015 @07:11PM (#10774604)
Ubsan already does this, there is a flag that controls abort on UB.
Re:Boringcc: Proposal for a C compiler for secure software by pekk on Tuesday December 22, 2015 @12:12AM (#10775968)
Unfortunately, nobody will use that compiler. They will continue to use the high-performance compilers, because this is what happened decades ago.
Re:Boringcc: Proposal for a C compiler for secure software by kenko on Monday December 21, 2015 @04:32PM (#10773672)
Why is that more appropriate than just defining all the currently undefined/implementation-specific behavior?
Re:Boringcc: Proposal for a C compiler for secure software by CountSessine on Monday December 21, 2015 @04:40PM (#10773721)
IMO both approaches would be useful. One nice thing about outlawing undefined behaviour rather than defining it, though, it that you'll be writing portable code - if you have a code base that's filled with all all sorts of once-was-undefined-but-now-is-defined behaviour, you can never build that code on another compiler.
Re:Boringcc: Proposal for a C compiler for secure software by Pxtl on Monday December 21, 2015 @04:37PM (#10773698)
Because enforcing undefined behavior on this test-compiler means you can build your software on any standards-compliant compiler and have it work the same. In theory.