➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author stutzbach
Recipients alexandre.vassalotti, benjamin.peterson, donmez, stutzbach
Date 2010-03-30.06:13:48
SpamBayes Score 2.476883e-06
Marked as misclassified No
Message-id <1269929631.39.0.708255527435.issue3326@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2010-03-30 06:13:51stutzbachsetrecipients: + stutzbach, alexandre.vassalotti, donmez, benjamin.peterson
2010-03-30 06:13:51stutzbachsetmessageid: <1269929631.39.0.708255527435.issue3326@psf.upfronthosting.co.za>
2010-03-30 06:13:49stutzbachlinkissue3326 messages
2010-03-30 06:13:49stutzbachcreate