[issue1621] Python should compile with -Wstrict-overflow when using gcc

Alexandre Vassalotti added the comment: I compiled Python using gcc 4.3.0 with the -Wstrict-overflow, and that's the only warning I got: Objects/doubledigits.c: In function ‘_PyFloat_Digits’: Objects/doubledigits.c:313: error: assuming signed overflow does not occur when assuming that (X + c)

[issue1621] Python should compile with -Wstrict-overflow when using gcc

Changes by Marc-Andre Lemburg: -- nosy: -lemburg __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue1621] Python should compile with -Wstrict-overflow when using gcc

Marc-Andre Lemburg added the comment: Whatever you change regarding the compiler options for Python, please make sure that this doesn't effect the default settings used by distutils to compile external modules (it normally takes the options straight from the Makefile used for compiling Python).

[issue1621] Python should compile with -Wstrict-overflow when using gcc

Martin v. Löwis added the comment: Using ansi is out of scope of this issue, and should not be mixed with it. -ansi is about disabling certain GCC extensions. This report is about C code in Python which has undefined behavior. I think there is disagreement on whether Python should stop relying o

[issue1621] Python should compile with -Wstrict-overflow when using gcc

Christian Heimes added the comment: Socket and SSL are using bluetooth.h which defines some functionas as inline. Inline isn't part of C89. Linuxaudiodev depends on the 'linux' macro which is not defined in C89. The Python core can be compiled with -ansi but the extension modules require -std=g

[issue1621] Python should compile with -Wstrict-overflow when using gcc

Christian Heimes added the comment: Should we use -ansi (C90 aka C89 standard) option, too? Python core compiles fine with -ansi but together with -Werror it breaks several extensions: _bsddb_codecs_iso2022 _ctypes _socket _ssl linuxaudiodev

[issue1621] Python should compile with -Wstrict-overflow when using gcc

Christian Heimes added the comment: My gcc 4.1 doesn't have the -Wstrict-overflow option. gcc-Version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) -- nosy: +tiran __ Tracker <[EMAIL PROTECTED]> _

[issue1621] Python should compile with -Wstrict-overflow when using gcc

New submission from Gregory P. Smith: The resolution to http://bugs.python.org/issue1608 looks like it'll add a -fwrapv gcc flag when building python. This works around the issue nicely on one compiler (gcc) but doesn't fix our fundamentally broken code. We should fix all dependencies on intege