News for hackers. Stuff that matters.
Re:You Can't Always Hash Pointers in C by jjnoakes on Wednesday June 01, 2016 @02:39PM (#11817007)
Why "must be sensible"? Why not just say "signed integer overflow is implementation-defined" and in a footnote say "for example, it may wrap, trap, saturate, or do anything else documented by your implementation"?

I'm not seeing the big deal here.

Re:You Can't Always Hash Pointers in C by lmm on Wednesday June 08, 2016 @05:07AM (#11860944)
> Why "must be sensible"? Why not just say "signed integer overflow is implementation-defined" and in a footnote say "for example, it may wrap, trap, saturate, or do anything else documented by your implementation"?

I don't think that actually defines anything - I don't think GCC would interpret that as anything other than undefined behaviour.