Guido van Rossum added the comment: It would actually be better to use -fno-strict-overflow instead of -fwrapv, if it exists (GCC 4.2 and later).
See also http://bugs.python.org/issue1621 which suggests there aren't actually many places that need this; gcc -Wstrict-overflow should help auditing the code. __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1608> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
