News for hackers. Stuff that matters.

A comment on Modern C++ Won't Save Us. Parent comment

Re:Modern C++ Won't Save Us by tpolzer on Tuesday April 23, 2019 @02:43AM (#19726162)
Chrome is in an exceptionally hard place because of its JIT. Your language cannot tell you if it's safe for your JIT to omit a bounds check.
[ Parent | on HN ]
Re:Modern C++ Won't Save Us by comex on Tuesday April 23, 2019 @05:29AM (#19726846)
That post describes two vulnerabilities: one is in the JIT, but the other one is in regular old C++ code. More generally, JIT bugs are a relatively small minority of browser vulnerabilities. More often you see issues like use-after-free in C++ code that interacts with JS, such as implementations of DOM interfaces, but the issues are not directly JIT related and would be avoided in a fully memory-safe language.
[ Parent | on HN ]
Re:Modern C++ Won't Save Us by ncmncm on Tuesday April 23, 2019 @08:22PM (#19734395)
Chrome, like Firefox, is not an example of modern C++ code. Google's and Mozilla's coding standards enforce a late-'90s style. It is astonishing they get it to work at all.
[ Parent | on HN ]