enh-google

> You fundamentally can't dlopen() from a static binary for a bunch of reasons... (note that those are just implementation details --- there's no theoretical reason you couldn't make dlopen()...

> The fundamental constraint is that it's broken to have two versions of libc my assumption there, when i've [only very idly] thought about this for bionic is that we'd...

almost two whole years ... probably time to just do it without attribution?

(we won't be adding support for risc-v to the long-deprecated ndk cpufeatures library. i've filed https://github.com/google/android-riscv64/issues/101 for the updates to the text on https://developer.android.com/ndk/guides/cpu-features though.)

(i've unlinked #87 because i don't think that's really related, nor is there any dependency in either direction, but i've created new bugs for the specific CDD and d.a.c changes...

(interestingly, that also links to some openssl pull requests that might be useful for boringssl later...)

(TIL there's also a CTS test you can't pass without AES instructions: cts/tests/tests/security/native/encryption/FileBasedEncryptionPolicyTest.cpp)

nice! being a kernel n00b, am i interpreting ``` +# This symbol indicates that the toolchain supports all v1.0 vector crypto +# extensions, including Zvk*, Zvbb, and Zvbc. LLVM added...

yes. hilarious that i missed filing this one, despite the fact that i spend more time on dealing with zlib optimizations myself than with any of the other projects. (though...

chromium is the upstream[1] for both Chrome (unsurprisingly) and Android (so "we" [=Google] only have to deal with these optimizations once). they in turn do sync with zlib but --...