News for hackers. Stuff that matters.
Re:Why Python's Integer Division Floors (2010) by rcfox on Wednesday February 28, 2024 @01:26PM (#39541838)
Didn't they specify two's complement signed integers somewhat recently? What's the rationale for leaving these behaviours undefined?
Re:Why Python's Integer Division Floors (2010) by kazinator on Wednesday February 28, 2024 @05:26PM (#39544277)
Because the shift operations are arithmetically defined, and the situations that are undefined correspond to overflow. v << 1 means the same thing as v * 2 and is undefined if v * 2 is undefined.
Re:Why Python's Integer Division Floors (2010) by Findecanor on Thursday February 29, 2024 @08:14AM (#39548854)
On some CPUs architectures, the operand size for some instructions could be larger than an `int`, in which case the upper part of a CPU register would become invalid on overflow instead of containing an extension of the sign bit.

There are also CPUs that do "saturating arithmetic" where overflow results in INT_MAX instead of wrapping.