Rich Felker

This is a mistreatment of the musl target we're trying to get fixed in upstream Rust. Like any other platform with dynamic linking, linux-musl target should produce dynamic binaries by...

Found the bug: the `poly1305_get_tag` function in `chachapoly.c` wrongly uses `(unsigned char *)&len` in an attempt to access the little endian encoding of length. It needs to use a proper...

It's not plausible that allocations by `opendir` are a performance bottleneck. Each `opendir` is an `open` syscall which is multiple orders of magnitude more costly than `malloc`. If a large...

I don't actually know Rust, but I think the quoted code necessitates allocation. It should probably be reusing internal storage or if there's an API contract to keep the object...

That raises another issue, that Rust's API seems to impose an assumption that the platform has a `NAME_MAX`...

I don't know what to add at this point except that, if `malloc` is such a bottleneck here, you'd get much better performance on glibc too by eliminating the gratuitous...

The design facilitates rwlock but was found not to be of any benefit, because the critical section is tiny and the cost is the memory-synchronizing operation itself, not exclusion due...

The original link is dead and wayback machine seems to have no archive of it. :-(

Fair enough, but I was still interested in reading the writeup with it.

What command gave you those errors as output? Are you sure these symbols are supposed to exist?