Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

Mention that GCC 4.1 is also affected, and that 

adding -fwrapv helps.
This commit is contained in:
Martin v. Löwis 2006-09-18 06:23:06 +00:00
parent 885d8e7737
commit cf783eb1db
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README
View File

@ -276,13 +276,16 @@ on these platforms without the special directions mentioned here,
submit a documentation bug report to SourceForge (see Bug Reports submit a documentation bug report to SourceForge (see Bug Reports
above) so we can remove them!) above) so we can remove them!)
GCC 4.1,
GCC 4.2: There is a known incompatibility between Python and GCC, GCC 4.2: There is a known incompatibility between Python and GCC,
where GCC 4.2 takes an interpretation of C different from where GCC 4.1 takes an interpretation of C different from
prior GCC releases, in an area where C has undefined behaviour prior GCC releases, in an area where C has undefined behaviour
(namely, integer arithmetic involving -sys.maxint-1). (namely, integer arithmetic involving -sys.maxint-1).
As a consequence, compiling Python with GCC 4.2 is not As a consequence, compiling Python with GCC 4.1/4.2 is not
recommend. It is likely that this problem will be resolved recommend. It is likely that this problem will be resolved
in future Python releases. in future Python releases. As a work-around, it seems that
adding -fwrapv to the compiler option restores the earlier
GCC behaviour.
Unix platforms: If your vendor still ships (and you still use) Berkeley DB 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 1.85 you will need to edit Modules/Setup to build the bsddb185