Posts by efa

sanitizer

All modern compiler has an option to add runtime code that check data boundary, double free, use after free, miss free, stack overflow, and so on.

At beginning was Clang/LLVM 3.1, but GCC 4.8+ (2013/3) has it from some years now.

That runtime code slow down binary to the level of C#, Java and Rust, so must be used only when build for debug with -g.

Once code is clean, you can remove sanitize address and get fast pure C compiled memory safe code without compromise.

Today we do not need slow memory safe languages, simply informed programmers

sanitizers

all modern compiler has an option to add runtime code that check data boundary, double free, use after free, miss free, stack overflow, and so on.

At beginnig was Clang/LLVM, but GCC 4+ has it from some years now.

That runtime code slow down binary to the level of C#, Java and Rust, so must be used only when build for debug with -g.

Once code is clean, you can remove sanitize address and get fast pure C compiled memory safe code without compromize.

Today we do not need memory sage languages, simply skilled programmers

All modern C compilers (at begin was CLANG/LLVM but from some years now also GCC) has an option to generated runtime code that check boundary violtions, double free, use after free, miss free, stack overflows and so on. This code slow down C to the level of Java, C# and Rust, so must be used only when build for debug with -g. Once code Is clean, remove sanitize address option and get pure fast secure memory safe C cide. So today theres no need for slow memory safe languages