Andrew Kelley

Do we have an upstream bug report to link to? I think this is LLVM not reporting the libraries in llvm-config. This like the third time this same thing has...

Oh that's really interesting with the defers in yellow. The number tells you how many different ways there were to exit the block, and it only goes green if you...

I tried this using `zig test` on the std lib. It's really quite useful, but I see some confusing output. In my test results I see: ``` Test 341/466 os.path.join...OK...

On which system do you observe `/usr/bin/env` not being an ELF file? And what is it instead?

@ifreund can you double check with `valgrind` that zig is not doing anything fishy?

```diff --- a/src/stage1/codegen.cpp +++ b/src/stage1/codegen.cpp @@ -8815,7 +8815,7 @@ Buf *codegen_generate_builtin_source(CodeGen *g) { buf_append_str(contents, "/// Deprecated: use `std.Target.current.cpu.arch.endian()`\n"); buf_append_str(contents, "pub const endian = Target.current.cpu.arch.endian();\n"); buf_appendf(contents, "pub const output_mode = OutputMode.Obj;\n");...

The regression should be fixed in 2de53592a1d84a1476f662e20d7339d25d4716fe. I'd like to leave this issue open until the logic is improved to match ld behavior that @LemonBoy posted above.

@ifreund one thing I still want to figure out, is why did zig get the wrong OS version? 3.16.0...5.5.5 means it failed to extract the value from the `uname` syscall.

> A simpler detection method would be to invoke `ldd --version` and scrape the output, No. I veto adding a dependency on `ldd`.

> How do I debug this? In order of increasing pain, 1. Run the test locally 2. Run the test locally with Valgrind 3. Get the other CI runs to...