Werner LEMBERG <[email protected]> wrote:

> My preferred solution would be to use something similar to the fix in
> issue #27441, given that unions is not the right way to go for C++,
> according to advice I've seen in the internet – and I want to preserve
> the ability that a C++ compiler can compile FreeType.

Probably a most easy and effective "fix" for this kind of bugs is to add
-fno-strict-aliasing flag, just like other system level libraries do.

-- 
Dmitry.

_______________________________________________
Freetype-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype-devel

Reply via email to