On Sunday 27 August 2006 05:06, Jack Howarth wrote: > I discovered that gcc 4.2 exposes a flaw with > signed integer overflows in python. This bug and the > necessary fix has been discussed in detail on the gcc > mailing list. I have filed a detailed bug report and > the recommended patch proposed by the gcc developers. > This problem should be addressed BEFORE python 2.5 is > released. The bug report is... > > [ 1545668 ] gcc trunk (4.2) exposes a signed integer overflows > > in the python sourceforge bug tracker. Thanks in advance > for attempting to fix this before Python 2.5 is released. > Jack
Regardless of whether we consider gcc's behaviour to be correct or not, I do agree we need a fix for this in 2.5 final. That should also be backported to release24-maint for the 2.4.4 release, and maybe release23-maint, as Barry recently started talking about cutting a 2.3.6. Can I nominate Tim, with his terrifying knowledge of C compiler esoterica, as the person to pick the best fix? Thanks, Anthony _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
