David Benjamin

Returning NULL when there isn't a symbol name available, and then having the caller handle it then (probably by returning something like `UNKNOWN_ERROR` in their APIs), seems reasonable enough to...

@paulidale That's X25519, not Ed25519. I believe OpenSSL's Ed25519 is indeed always radix 25.5, which leaves a ton of perf on the table on 64-bit platforms.

Webathena should use a similar build system to Roost. It works pretty well.

Hehe, this has been abandoned for quite a while now. Between NaCl and the old filesystem API this thing is pretty much made entirely of deprecated stuff. :-) It should...

Certainly they need to be reported upstream, but as OSS-Fuzz manages the LLVM versions here, they're the next hop. As part of managing that bug, they'll need to temporarily rollback...

Changes in a stable branch can cause problems too. There may also be build problems not caused by LLVM updates. I don't think the frequency of LLVM updates has anything...

The OSV import process has made this a lot more urgent. Some related issues: * https://github.com/google/oss-fuzz/issues/11925 * https://github.com/google/osv.dev/issues/2176 * https://github.com/google/osv.dev/issues/2177 Now that there are systems that consume OSS-Fuzz reports, OSS-Fuzz...

This does suggest that, if we're dealing with bitmasks and the like internally, they probably should be signed. I forget what we did. I think most of it's in our...

The experimental 64-bit Flash plugin seems to work reasonable fine (at least, it loads). So perhaps it's nspluginwrapper's fault. Though one telling thing was that it prints out (:21572): Gdk-CRITICAL...

@kroeckx This isn't about the encoding of some `const char *` API parameter or whatever. It's just pretty-printing of a field in the command-line tool where the encoding is already...