Peter0x44

6 ms·

1. 1.▲
   by Peter0x44 2y ago

   I've found it to have quite poor defaults for its analysis (things like suggesting "use annex k strcpy_s instead of strcpy"). fanalyzer is still by far the easiest to configure.
2. 2.▲
   by Peter0x44 3y ago

   I think their BC is overrated. Wine manages to do a better job.
3. 3.▲
   by Peter0x44 3y ago

   Why would I ever have a debug build without sanitizers? Nothing stops you from removing the asserts in this case, anyway. I don't see what the problem is with using __builtin_unreachable in this context. I think you didn't underst
4. 4.▲
   by Peter0x44 3y ago

   Asserts are to make your code more sensitive to defects, for example, checking function invariants. Ideally the library has more , not less, since they show care and thought has gone in. They should never be used to handle errors. Another
5. 5.▲
   by Peter0x44 3y ago

   Probably it should be stated explicitly, but this is implied if you add `-fsanitize=undefined`, where you will get a diagnostic if the unreachable code is reached. With `-fsanitize-trap=undefined`, you get a trap instruction there, the comp