mirror of
https://github.com/odin-lang/Odin.git
synced 2026-09-02 18:23:35 +00:00
A tsz of zero has no set bit, so it names no element size at all; the architecture reserves it and llvm-mc calls the word invalid. We decoded it as `xar z0.b, z0.b, z0.b, #16` -- a shift of 16 on a byte, which is not a thing. No single mask says "tsz is not zero", but four do, the same way the cset aliases exclude AL and NV: 1xxx, 01xx, 001x, 0001 cover every non-zero value between them and nothing else. Splitting it that way broke encode at first, because the four forms have the same operand types and the matcher took whichever came first, ORing its fixed tsz bit onto a value meant for a different element size. Each pattern pins exactly the bit its own element size sets, though, so typing the operands by size makes the matcher pick the right one and the OR consistent. SVE/SME2 against llvm-mc: 707 of 707 byte-exact, nothing mismatched and nothing it cannot assemble. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UmHLRF11EoWwNWCJ7JGaA