I stumbled across -fno-strict-aliasing when building gssproxy. Typically this is needed for very old code or code which tries to use weird pointer stunts to squeeze out more performance, but neither is true for gssproxy (whose code is mostly a good ISO C99/C1X citizen).
So I am going to remove -fno-strict-aliasing and replace it with -Werror=strict-aliasing to ensure that if anything creeps up the build will just fail (this requires in gcc4.x's case the use of -fstrict-aliasing, too).
References:
Patch gssproxy_use_c99_aliasing001.diff
Fixed in: bcea066
Metadata Update from @gisburn: - Issue assigned to gisburn - Issue set to the milestone: 2014 April
Login to comment on this ticket.