Mention that GCC 4.1 is also affected, and that

adding -fwrapv helps.

diff --git a/README b/README
index 70e4d231d8f99d1a898ee6d3123addea934ec599..b91e229115c9491675d8fcdc9d20d04db45be122 100644 (file)
--- a/README
+++ b/README
@@ -276,13 +276,16 @@ 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.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
         (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
-        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
         1.85 you will need to edit Modules/Setup to build the bsddb185