[Python-Dev] gcc 4.2 exposes signed integer overflows (original) (raw)
Thomas Wouters thomas at python.org
Sun Aug 27 01:54:08 CEST 2006
- Previous message: [Python-Dev] gcc 4.2 exposes signed integer overflows
- Next message: [Python-Dev] gcc 4.2 exposes signed integer overflows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 8/26/06, David Hopwood <david.nospam.hopwood at blueyonder.co.uk> wrote:
CPython should be fixed anyway. The correct fix is "if (y == -1 && x < 0 && (unsigned long)x == -(unsigned long)x)".
Why not just "... && x == LONG_MIN"?
-- Thomas Wouters <thomas at python.org>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20060826/11fa9509/attachment.html
- Previous message: [Python-Dev] gcc 4.2 exposes signed integer overflows
- Next message: [Python-Dev] gcc 4.2 exposes signed integer overflows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]