Python very slow on the Sharp Zaurus
Alexandre Courbot
alexandrecourbot at linuxgames.com
Mon Jul 22 17:30:24 EDT 2002
More information about the Python-list mailing list
Mon Jul 22 17:30:24 EDT 2002
- Previous message (by thread): Python very slow on the Sharp Zaurus - any idea why?
- Next message (by thread): Python very slow on the Sharp Zaurus - any idea why?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Tim Peters <tim.one at comcast.net> writes: > > Python used to use float arithmetic to detect int mult overflow, but > > that didn't work correctly on some 64-bit boxes. > > > > It got replaced by over 100(!) lines of all-integer int mult > > overflow-checking code, and I believe that's still in 2.1.3. > > > > But that had an obscure endcase bug too, and it get replaced in 2.2 > > by a new float method that doesn't make unwarranted assumptions > > about the relative sizes of C longs and C doubles, and usually gets > > out quickly -- provided float arithmetic isn't pig slow. > > Ouch!! That doesn't sound so good for the Zaurus. Yeah, I wonder if it's worth to profile the stuff! :) Guys, I'll first test it with Python 2.1.3. Adonthell (the game I'm porting) works with any Python >= 1.5.2, so if the problem can be solved in the short-term by regressing to 2.1, that'll be fine for now. If the differences are significant, then maybe we could consider to add another interger-only checking method that would suit in the case of Arm processors. I'll try to give you news about it tomorrow. Thanks again for the relevant answers! Alex. -- http://www.gnurou.org
- Previous message (by thread): Python very slow on the Sharp Zaurus - any idea why?
- Next message (by thread): Python very slow on the Sharp Zaurus - any idea why?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list