Alex Rønne Petersen

> How would it look to say that a `try` expression is likely to throw? That seems like a rare enough use case that it's fine for it to be...

Has an upstream LLVM issue been filed for whatever it is that's causing this to be necessary?

Can you go into detail regarding the `R_LARCH_B26` problem you mentioned? Just trying to understand why the default code model is not sufficient for Zig. Is it just that the...

Ok, so it's an issue specific to building the `zig` binary because it's so big. Then editing `build.zig` seems to be the right call to me; editing `src/Package/Module.zig` would, AFAICT,...

> It seems like any project could hit this limitation if its code grows beyond a certain threshold. Yes, but that's true of code models on all architectures, not just...

The order of evaluation is working the way I'd expect it to here.

z/OS is closed-source, has no publicly downloadable image, only runs on "if you have to ask, you can't afford it" hardware, has significantly different toolchain and ABI conventions from mainstream...

It would be nice to know exactly [which of these registers](https://github.com/ziglang/zig/blob/11176d22f82861b4b6967b77f753414f214bc632/lib/std/zig/system/linux.zig#L396-L407) are problematic on that machine. It would be fairly surprising if the `mrs` instruction is just blocked wholesale.

Well, you can just try editing that array of registers, replacing calls with `0` until you narrow down which work and which don't. Armed with that info, I think it'd...

Now that I take a closer look, I actually have no idea how this ever worked? EL0 is user space and EL1 is kernel mode; of course these registers will...