diff options
| author | Guido van Rossum <guido@python.org> | 2007-12-13 20:42:33 (GMT) |
|---|---|---|
| committer | Guido van Rossum <guido@python.org> | 2007-12-13 20:42:33 (GMT) |
| commit | d4029c8fda1e6f22d2bb95d248b306dd7d42b038 (patch) | |
| tree | 50bfbed2fedfc2f0a5fde188d9a6936b16486688 /README | |
| parent | 483704508d2e2271e6eb0090ebaec7ae086f3db8 (diff) | |
| download | cpython-d4029c8fda1e6f22d2bb95d248b306dd7d42b038.zip cpython-d4029c8fda1e6f22d2bb95d248b306dd7d42b038.tar.gz cpython-d4029c8fda1e6f22d2bb95d248b306dd7d42b038.tar.bz2 | |
Bug #1608: use -fwrapv when GCC supports it. This is important, newer
GCC versions may optimize away overflow buffer overflow checks without
this option! Thanks to Ismail Donmez. No thanks to the GCC devs.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 13 |
1 files changed, 0 insertions, 13 deletions
@@ -282,19 +282,6 @@ on these platforms without the special directions mentioned here, submit a documentation bug report to SourceForge (see Bug Reports above) so we can remove them!) -GCC 4.1, -GCC 4.2: There is a known incompatibility between Python and GCC, - where GCC 4.1 and later uses an interpretation of C - different to earlier GCC releases in an area where the C - specification has undefined behaviour (namely, integer arithmetic - involving -sys.maxint-1). - - As a consequence, compiling Python with GCC 4.1/4.2 is not - recommended. It is likely that this problem will be resolved - in future Python releases. As a work-around, it seems that - adding -fwrapv to the compiler options restores the earlier - GCC behaviour. - Unix platforms: If your vendor still ships (and you still use) Berkeley DB 1.85 you will need to edit Modules/Setup to build the bsddb185 module and add a line to sitecustomize.py which makes it the |