On 2017-12-14 11:35 AM, Michel Dänzer wrote:
> I don't think compilers can reliably warn about all strict aliasing
> violations yet (ever?).
>
> Is this really worth the risk? Do you have any numbers showing tangible
> benefits of this change?
The main benefit is in code cleanliness, not necessarily performance.
The risk if we don't make this change is to those of us with non-gcc
compilers (that don't have -fno-strict-aliasing or an equivalent as an
option). Replacing -fno-strict-aliasing with -Werror=strict-aliasing is
a step in the right direction.
Peter Harris
--
Open Text Connectivity Solutions Group
Peter Harris http://connectivity.opentext.com/
Research and Development Phone: +1 905 762 6001
[email protected] Toll Free: 1 877 359 4866
_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
