airbus-seclab/c-compiler-security

about "disable the warnings that have too much false positives"

Closed this issue · 1 comments

Strongly disagree with that statement: if you used early in the development phase (and not compiling the code with security flags just before going into production), the false positive rate should not be that high

trou commented

I was thinking about existing code bases, and some warnings are not fool proof and can have false positives (even if on well written code this should not be the case).

Maybe I could add a note about pragma to selectively disable some warnings in some specific functions ?