Alex Rønne Petersen

Thinking about it more, I can sort of see what's going on here: BN is essentially reasoning that `(this + 0x10) != 0` can be simplified to `this != -0x10`....

Has the team had a chance to contemplate this one? :eyes:

Looks like this needs an update for current master.

The main blocker here is going to be the fact that LLD just doesn't support ELFv1 for PPC64 at all, and glibc only supports ELFv2 for little endian, so we...

https://github.com/ziglang/zig/issues/5927#issuecomment-3369326298 > and glibc only supports ELFv2 for little endian, so we can't just simply force ELFv2. (This turns out not to be true.)

`uname -mr`?

The `AT_HANDLE_FID` flag requires Linux kernel 6.5+. We support 5.10+: https://ziglang.org/download/0.15.1/release-notes.html#OS-Version-Requirements I'm not sure if there's a meaningful fallback we can do here though.

Stack trace: ``` ❯ zig4 build-exe test.zig Compiler crash context: Generating function 'test.crasher' thread 90926 panic: reached unreachable code /home/alexrp/Source/ziglang/zig/lib/std/debug.zig:416:14: 0x1c9d6c9 in assert (std.zig) if (!ok) unreachable; // assertion failure...

> WASI and Haiku aren't unix-y either. WASI seems to be partially Unix-y, though obviously nowhere near full POSIX. Haiku seems to be POSIX-compatible, as far as I can find?...

Status quo already punishes users who want to target Windows. See #6600. `std.posix` is not a good Windows wrapper. The right way to do this is to have well-designed abstractions...