Andrew Kelley

Update: I'm still interested in this but have put the project on ice for the time being. If y'all end up looking into it and figuring out something that works...

This depends on progressing our fuzzing toolchain, and then doing fuzzing against std.http and std.crypto.tls. Otherwise users are looking at security vulnerabilities. I have also rewritten http client and server...

> current Zig tracing interface is exclusively targeted to https://github.com/wolfpld/tracy. To be clear, the current **self-hosted compiler** tracing interface is. There is no tracing interface in the standard library (yet)....

There's an easy way to understand who owns standard in and standard out. Whichever component has the main() function. In the case of zig unit testing, the unit test themselves...

Does it fail? From the log it looks like it timed out at `Building zig2`.

Perhaps a question that can be answered by an LLD developer. Does LLD perhaps lack implementation of some relocations for ppc64le? Or perhaps clang++ is emitting some strange relocations for...

The target `powerpc64le-linux-gnu` is dynamically linked glibc. A static build uses target `powerpc64le-linux-musl` and is the one that the CI tests with every commit. Looks like the dynamic glibc target...

Zig does not integrate with mold since the plan is to provide our own linking functionality for this use case.

Yes, that is the current state of affairs, until Zig's linker surpasses LLD's functionality and adds these relocations.

For ppc64le specifically, I think your best bet is using https://github.com/ziglang/zig-bootstrap to cross-compile. ``` ./build powerpc64le-linux-musl baseline ``` Be sure to read the README and use additional environment variables to...