4 ms·
Nice way to put down the amazing work of compiler authors. It's not malware you just don't understand how to use it. If you don't want the compilers to do crazy
by bluecalm 4y ago
Nice way to put down the amazing work of compiler authors. It's not malware you just don't understand how to use it. If you don't want the compilers to do crazy optimisations turn down the optimisation level. If you want then to check for things like null pointers or integer overflow or array bounds at runtime then just turn on the sanitizers those compiler writers kindly provided to you.
You just want all of it: fast optimizing compiler, one that checks for your mistakes but also one that knows when it's not a mistake and still generates fast code. It's not easy to write such a compiler. You can tell it how to behave though if you care.
- a1369209993 4y ago> If you want then to check for things like null pointers or integer overflow or array bounds I specificly don't want them to check for those things; that is the fucking problem in the first place! When I write: x = *p; I want it compiled to a damn memory access. If I meant: x = *p; __builtin_assume_non_null(p); I'd have damn well written that.