[Python-Dev] py3k branch still using -fno-strict-aliasing (original) (raw)
İsmail Dönmez ismail at namtrac.org
Wed Jul 2 07:25:19 CEST 2008
- Previous message: [Python-Dev] Can someone check my lib2to3 change for fix_imports?
- Next message: [Python-Dev] [issue3214] Suggest change to glossary explanation: "Duck Typing"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
I remember discussing this before and coming to conclusion that -fno-strict-aliasing would be removed from py3k CFLAGS. But as of now its still used.
I tested with gcc 4.3.1 on Linux x86_64 and there is no strict aliasing warning when this flag is removed. Also make testall passes. Is there any reason to keep this flag? If not see the attached patch.
Regards, ismail
-- Programmer Excuses number 45: I do object-oriented programming - if the customer objects, I do more programming. -------------- next part -------------- A non-text attachment was scrubbed... Name: strict-aliasing.patch Type: text/x-diff Size: 1064 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20080702/13911566/attachment.patch>
- Previous message: [Python-Dev] Can someone check my lib2to3 change for fix_imports?
- Next message: [Python-Dev] [issue3214] Suggest change to glossary explanation: "Duck Typing"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]