Tracking issue / gaps for aarch64 self-hosted backend?

I think I’ve gotten spoiled to the high rate of zig compiler development, I hadn’t realized until I was on an arm machine that there was no self-hosted backend for this arch.

No rush, but as I was diving thru the issues/PRs/milestones on codeberg, I wasn’t seeing any clear signal on what the status was for these features. Is there any ongoing work on the self-hosted backends?

I also follow the devlog/news, but sometimes there’s “dry patches” where I infer what’s going on from the ziggit/PRs, but that’s a bit noisy (its a big project after all). Is there any better way to track the various initiatives, features, goals, etc, if just from a visibility perspective?
Or does that change too much release to release, and therefore not worth automating? Every 3 releases of zig feels like a new system.
Nbd, just curiously lurking.

Tracking issue:

https://codeberg.org/ziglang/zig/issues/36609

Good question. I’ve personally been focused on other areas of the project so I actually don’t know the answer to this question off the top of my head, but I’ll encourage the team to write up issues for the blockers and thereby facilitate contributions.