Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-18 Thread Neal Norwitz
On 9/18/06, Tim Peters <[EMAIL PROTECTED]> wrote: > [Neal Norwitz] > >> I'm getting a crash when running test_builtin and test_calendar (at > >> least) with gcc 4.1.1 on amd64. It's happening in pymalloc, though I > >> don't know what the cause is. I thought I tested with gcc 4.1 before, > >> but

Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-18 Thread Tim Peters
[Neal Norwitz] >> I'm getting a crash when running test_builtin and test_calendar (at >> least) with gcc 4.1.1 on amd64. It's happening in pymalloc, though I >> don't know what the cause is. I thought I tested with gcc 4.1 before, >> but probably would have been in debug mode. Neil, in context i

Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-18 Thread Martin v. Löwis
Neal Norwitz schrieb: > I'm getting a crash when running test_builtin and test_calendar (at > least) with gcc 4.1.1 on amd64. It's happening in pymalloc, though I > don't know what the cause is. I thought I tested with gcc 4.1 before, > but probably would have been in debug mode. Can't really ch

Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-17 Thread Neal Norwitz
On 9/17/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > Neal Norwitz schrieb: > > I also tested the fix (see patch below) for the abs() issue and it > > seemed to work for 4.1.1 on 64-bit. I'll apply the patch to head and > > 2.5 and a test after 2.5 is out. > > Please also add it to 2.4. Yes

Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-17 Thread Martin v. Löwis
Neal Norwitz schrieb: > I also tested the fix (see patch below) for the abs() issue and it > seemed to work for 4.1.1 on 64-bit. I'll apply the patch to head and > 2.5 and a test after 2.5 is out. Please also add it to 2.4. > Index: Objects/intobject.c > =

Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-17 Thread Neal Norwitz
I also tested the fix (see patch below) for the abs() issue and it seemed to work for 4.1.1 on 64-bit. I'll apply the patch to head and 2.5 and a test after 2.5 is out. I have no idea how to search for these problems. I know that xrange can't display -sys.maxint-1 properly, but I think it works

Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-17 Thread Martin v. Löwis
> BTW, did anyone try compiling Python with -fwrapv on a box where it > matters? I doubt that Python's speed is affected one way or the > other, and if adding wrapv makes the problems go away, that would be > an easy last-second workaround for all possible such problems (which > of course could ge

Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-17 Thread Tim Peters
[Armin Rigo] >> There are more cases of signed integer overflows in the CPython source >> code base... >> >> That's on a 64-bits machine: >> >> [GCC 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)] on linux2 >> abs(-sys.maxint-1) == -sys.maxint-1 >< >> Humpf! Looks like one person or two need

Re: [Python-Dev] Before 2.5 - More signed integer overflows

2006-09-17 Thread Anthony Baxter
On Saturday 16 September 2006 21:11, Armin Rigo wrote: > Hi all, > > There are more cases of signed integer overflows in the CPython source > code base... > > That's on a 64-bits machine: > > [GCC 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)] on linux2 > abs(-sys.maxint-1) == -sys.maxint-1

[Python-Dev] Before 2.5 - More signed integer overflows

2006-09-16 Thread Armin Rigo
Hi all, There are more cases of signed integer overflows in the CPython source code base... That's on a 64-bits machine: [GCC 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)] on linux2 abs(-sys.maxint-1) == -sys.maxint-1 I'd expect the same breakage everywhere when GCC 4.2 is used. Note t