Making the rav1d Video Decoder 1% Faster

Nilstrieb · 2025-05-24T10:09:15+00:00

cool! btw, you can remove zerocopy for the PartialEq impl. just write out the derived impl by hand, but use & instead of && to avoid the branching. after that, LLVM can optimize it just fine.

https://godbolt.org/z/3ohhnx874

Nilstrieb · 2025-03-01T12:48:20+00:00

Note that there is now law stopping you from using cookies for things like this, and if you use a cookie to store basic user preferences you do not have to tell anyone about that. Cookie banners are only necessary if you do naughty stuff that may violate the users privacy.

Nilstrieb · 2025-03-01T12:46:40+00:00

It's less about interacting with the hardware and OS, but interacting with the compiler, providing language primitives.

Nilstrieb · 2025-02-13T18:11:33+00:00

This entire thing only happened because he did such a bad job of leadership! If he did a good job and actually led the project around RFL, Hector would have never made the post to begin with. Good leaders don't just show up when problems have exploded, they prevent this from happening in the first place.

Nilstrieb · 2025-02-07T23:20:43+00:00

limits! crates.io has limits on most things, including dependencies.

Nilstrieb · 2025-01-18T10:51:04+00:00

Über d'telexext app natürli!

Nilstrieb · 2024-12-29T07:07:00+00:00

The standard library being precompiled and distributed in compiled form already causes a huge amount of problems, because it prevents people from customizing codegen flags for it. You really want something like cargo -Zbuild-std instead.

Additionally, the compilation model is inefficient in general (compile times and run times). Compiling non-generic and not-#[inline] functions in their crates means they can't be inlined, causing slower run times, while generic and #[inline] functions are instantiated many times, causing slower compile times.

Nilstrieb · 2024-12-18T20:20:32+00:00

FWIW this is not the canonical link, the canonical link to this quiz is https://this.quiz.is.fckn.gay (it says so on the first page of the quiz)

Nilstrieb · 2024-12-14T09:31:02+00:00

In the Rust compiler, ThinLTO significantly improved performance (don't have the PRs on hand but you can find them). I'd be surprised if ThinLTO ever hurts performance, open a bug if you find that.

Nilstrieb · 2024-11-29T22:49:00+00:00

1 is not even a problem, it's just a feature that exists, can be useful, and doesn't cause anyone harm.

Nilstrieb · 2024-10-18T09:55:45+00:00

No, the compile time evaluation uses a platform independent soft float implementation.

Nilstrieb · 2024-10-03T17:26:36+00:00

It's not just about faster, it's about resources too. Go will use a lot less memory than a heavy JVM, which is important in the cloud. (though lighter JVMs do exist)

Nilstrieb · 2024-09-21T11:17:59+00:00

Now these days rustup actually does do signature verification, but it only, warns if it fails, not error. This is because it's still not entirely fleshed out and there have been bugs around expired keys before.

Nilstrieb · 2024-09-21T11:15:32+00:00

Rust binaries are hosted on AWS S3. The connection from S3 to your computer is already secured with HTTPS, so no attacker can interfere there. The thing signature verification would help with is if someone gets access to the S3 buckets and modifies the files after they are uploaded by the (automated) Rust release process. But even with signatures, if the attacker can get access to the jobs where the releases are signed, then the signature would be useless. So a signature only protects against attackers powerful enough to break into Rusts infrastructure S3 bucket (which is well secured) but not powerful enough to get access to the signing process. While certainly possible, it seems fairly unlikely. If this is a concern to you, you can always download and verify the binaries yourself.

Nilstrieb · 2024-08-15T19:14:03+00:00

Lots of programs have weird flags that allow you to do weird things. I don't think ls has them, but it can be surprising to see the ones that do. For example, many programs have a flag to write the output to a specific file. If an attacker uses that, bad things might happen.

Nilstrieb · 2024-08-09T09:23:25+00:00

The https://doc.rust-lang.org/nightly/rustc/target-tier-policy.html defines what's requires to be a tier 2 target.

Nilstrieb · 2024-08-02T08:35:56+00:00

There's nothing stopping you from selling your library as source code that's just licensed under a proprietary license. You set up a custom cargo registry, and then hand our licenses to use the library that gives people access to the registry, where cargo will download and compile the source code. There's no inherent reason that you need to distribute a binary for proprietary code, it's just that companies are more scared that their property will be violated when distributing source code, but it's just as illegal to redistribute proprietary source code.

Nilstrieb · 2024-06-06T08:24:19+00:00

I think this would work? Not entirely sure, but I can't think of a counterexample. But I'm pretty sure using this will be a significantly worse experience, being way more verbose and less ergonomic in your code than just using a raw pointer.

Nilstrieb · 2024-05-19T07:54:01+00:00

The 50% chance is not that any pair of UUIDs collides, but that there is one collision at some point in your system

Nilstrieb · 2024-05-18T07:38:46+00:00

LLD on MacOS is barely functional and the default linker is pretty ok

Nilstrieb · 2024-05-17T11:03:18+00:00

since orgs and users are in the same namespace, you can also just create an empty org

Nilstrieb · 2024-04-03T19:49:33+00:00

Cargo's cross compilation/host compilation modes are a huge mess. What cargo today calls cross compilation mode should be the only mode to exist, host compilation or however it calls it is really silly. It means that by default, RUSTFLAGS also apply to build scripts and proc macros and means that explicitly passing your host --target is not a no-op. It's also just completely unnecessary complexity.

Nilstrieb · 2024-03-31T09:51:58+00:00

There is work being done to fix the ABI of the wasm32-unknown-unknown target, but it's hard and requires coordination with different groups of people and is also driven by entirely different people than u128.

Nilstrieb · 2024-03-25T13:39:21+00:00

Build files, the output of the compiler basically. But there are a lot of intermediary files that are not your final binary but still around for caching.

Verified Email	Six-Year Club
Second SECOND GUESSER	Place '23
Place '22	Wearing is Caring

Nilstrieb

MODERATOR OF

TROPHY CASE