4 ms·
Isn't that what asan/ubsan is for? Granted, it's not static analysis, but it should catch most aliasing related errors, no?
by xxpor 6y ago
Isn't that what asan/ubsan is for?
Granted, it's not static analysis, but it should catch most aliasing related errors, no?
- Ar-Curunir 6y agoonly if your tests exercise that code path
- identity0 6y agoYou can't do compile time bounds checking, if that's what you're implying.
- fizixer 6y agoI'm fully in the camp of C plus powerful analysis tools, plus a high-level language (Python or Scheme).
- pjmlp 6y agoSince powerful analysis tools aren't defined by ISO what they are supposed to be, there are plenty of C compilers that will never get them.
- nsajko 6y agoNo. There has been some effort in that direction, somebody proposed a Clang "type sanitizer" patch, but it wasn't merged.
- saagarjha 6y agoMost, but not all. They are excellent tools but not perfect by any means.