Re: distutils and -fno-strict-aliasing

2010-12-14 Thread Jakub Wilk
* Jakub Wilk jw...@debian.org, 2010-12-11, 12:27: I noticed a bug/feature of Python 2.7 (and 3.X) distutils that worries me a bit. Just a minor correction: Python 3.X extension are not supposed to be compiled with -fno-strict-aliasing (at least not by default), so let's s/(and 3\.X)//. --

Re: distutils and -fno-strict-aliasing

2010-12-13 Thread Jakub Wilk
* Éric Araujo mer...@netwok.org, 2010-12-12, 23:10: Can you report this behavior on bugs.python.org, if it isn’t already filed? Thanks in advance. It has already been reported over 6 years ago: http://bugs.python.org/issue969718 However, I couldn't trigger this problem with lenny's python2.4

Re: distutils and -fno-strict-aliasing

2010-12-12 Thread Éric Araujo
Hi Jakub, Can you report this behavior on bugs.python.org, if it isn’t already filed? Thanks in advance. Regards -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

distutils and -fno-strict-aliasing

2010-12-11 Thread Jakub Wilk
I noticed a bug/feature of Python 2.7 (and 3.X) distutils that worries me a bit. Let's try to compile a simple extension module: $ python2.7 setup.py build_ext | grep -F .c gcc -pthread -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7