Get the latest tech news
Improving performance of rav1d video decoder
*on macOS with an M3 chip *slightly more than 1%, on a specific benchmark, without any new unsafe code A while ago, memorysafety.org announced a contest for …
Usually, starting with the “inverted stack” view helps to narrow down interesting options (which we’ll explore in ), but this time we want to focus on the anchors we know should match: the asm functions. Since dav1d never initialized it anyway, we know that logically any data read from this buffer was written beforehand with a valid value (which really helps to drive home the idea that Undefined Behavior deserves a better reputation). You might be wondering why the default implementation of PartialEq results in bad code generation, and a comment on the PR adding these impls pointed to Rust issue #140167, which tracks exactly this type of problem.
Or read this on Hacker News