You can get that behaviour (mostly) already today by simply not enabling optimizations.

The resulting performance difference is basically the price to pay for such a 'strict' compiler which translates the input source code straight into machine code instructions without attempting to simplify the output code via inlining, constant folding and dead code removal.

▲ vbezhenar an hour ago | parent [-]

-O0 program is useless and should be written with any other language. The whole point of C is to use compiler with optimizations. I'm not against optimizations. I'm against optimizations that perform things unexpected by the programmer. Dead code removal is unexpected by the programmer, because programmer does not write dead code.

	▲	flohofwoe an hour ago \| parent [-]
		Well you can't have your cake and eat it too ;) > Dead code removal is unexpected by the programmer, because programmer does not write dead code. Of course it is expected, because the optimizations leading to dead code are fundamental for the performance you get out of a release-mode binary (and that's also true for languages with less UB like Rust btw). When you have a function: `static int add(int a, int b) { return a + b; }` And you call that function with const parameters: `int c = add(2, 3);` Then you want that entire function call to be removed and "folded" into its result 5, and when this was the only place the function was called, you'd also want the actual function to be removed from the binary (because what's the point of lugging code around in the binary that's guaranteed to never be executed).