[issue3326] py3k shouldn't use -fno-strict-aliasing anymore

[Daniel Stutzbach]

Daniel Stutzbach <daniel at stutzbachenterprises.com> added the comment:

Attached is a patch for configure.in and configure that implements Benjamin's suggestion.  The patch sets things up to continue to use -fno-strict-aliasing on gcc versions that support -fno-strict-aliasing *and* generate spurious warnings without it.  Effectively, that means it adds -fno-strict-aliasing for gcc versions < 4.3.

I tested it with gcc-3.4.4 and gcc-4.3.2.  It added -fno-strict-aliasing with gcc-3.4.4 and did not with gcc-4.3.2, as desired.  

With the gcc-4.3.2 build, I did a "make test" and no tests failed.  

I also found that pybench ran around 1% faster with the patch.

----------
versions: +Python 3.2, Python 3.3
Added file: http://bugs.python.org/file16696/strict-aliasing.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3326>
_______________________________________