On Sat, Aug 10, 2019 at 7:32 PM Nikolaus Waxweiler <madig...@gmail.com>

> > Undefined does not mean scary.
> Actually yes. Have you read e.g.
> http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html?

Whether with -wrapv or with the unsigned macros, we simply disable some
compiler optimizations, perhaps some good optimizations too.

Why? Is it because we got scared? There is absolutely no evidence of real
bugs in FreeType. It is reasonable to disable optimizations with  -wrapv,
if scared, but macros are too rigid. Some compilers recognize /* fall
through */  comment to suppress particular warnings. I wish we could just
add a comment to silence these warnings after adjudication.
Freetype-devel mailing list

Reply via email to