News for hackers. Stuff that matters.
Re:Cap'n'Proto remote vuln: pointer overflow check optimized... by raverbashing on Friday April 21, 2017 @10:19AM (#14165805)
I'm going to be honest here, whenever I read things like this more I'm convinced C belongs in the trash can

I would accept that pointer overflow is implementation dependent. Allowing it to be "undefined behaviour" is sincerely BS.

Every processor has a "pointer register". Increment it until it overflows. What happens then? Most of the time it will roll over. I suspect this happens in even early RISC architectures that faint if you look at it too hard. There's your answer

It's right, it's not a compiler bug. C tries to solve all problems and cops out on the real issues. The language is broken.

Re:Cap'n'Proto remote vuln: pointer overflow check optimized... by banachtarski on Friday April 21, 2017 @03:32PM (#14168640)
No, it's definitely a compiler bug here.