Release notes

Android SDK types and native floating-point fields.

0.3.5 adds an Android SDK declaration entry point and 25 public NDK structure layouts, including explicit ARM32 variants, nested structures, arrays, unions, and callbacks. Meta/DSL structure and union fields support f32 and f64 with typed defaults, packed or natural alignment, and IEEE-754 byte emission. The catalog holds 22,956 exact provider records for 4,405 names in 25 libraries across five ABIs. Checked imports validate the image ABI, minimum API, library, and symbol kind; object imports use GOT slots with OBJECT dynamic-symbol types. Android tutorials and native demos use these types and imports. Includes backend 0.1.5.

Correct SPIR-V words and safer compile-time state.

0.3.4 follows the current SPIR-V 1.6 grammar and keeps extension schemas separate. It preserves hexadecimal floating-point payloads, corrects half and BFloat16 constants and 64-bit Switch literals, and keeps symbolic IDs and quoted strings separate from Meta expressions. Value-returning Meta functions preserve caller-owned mutable values, and empty writes retain reserve-tail trimming. The generated AArch64 library shares repeated encoding bodies. Includes backend 0.1.5; unsupported floating formats produce diagnostics.

Less repeated work in Meta and DSL evaluation.

Version 0.3.3 removes two pieces of repeated work from Meta and DSL evaluation. A meta_if condition is parsed once and its parsed form reused, instead of being re-parsed on every execution of the statement, and operand.eval borrows the bindings captured with the operand instead of cloning them into a fresh scope on every call. A capture still means the values it was taken with, and the bytes encoded for the same source are unchanged.

SPIR-V IDs you can name, and errors on the line that failed.

0.3.2 lets a SPIR-V module name its result IDs. A numeric ID keeps the number it was written with and nothing is renumbered; a name is numbered from 1 upward in the order it first appears, skipping the numbers literals already use, so an entry point can be named before the function that defines it. A name that is never defined, or that is defined twice, is rejected at the line that caused it, and every SPIR-V text failure now reports the line that failed instead of the first line of the module.

Faster AArch64 macro expansion.

Version 0.3.1 takes two copies out of the AArch64 macro path. A macro capture no longer deep-copies the generated instruction tables, and a read-only built-in borrows the collection it is handed instead of copying it first. The bytes encoded for the same source are unchanged, and the language behaves exactly as before.

The first release ready for real work.

0.3.0 is XIRASM's first release for actual use: source goes straight to runnable output; the documentation matches the assembler and every example in it has been assembled; Android builds an installable APK from native sources alone — no Java, no resource compiler, no third-party runtime.

• Android, from native source to an installable APKA project writes its NativeActivity library, declares its resources and packages the archive without leaving XIRASM. The APK writer emits the ZIP container, the binary AndroidManifest.xml and a resources.arsc compiled from a res/ tree, while the resource table and the native libraries stay uncompressed and aligned the way Android requires.
• Guides that match the assemblerThe format tutorial is rewritten in English and Chinese with one section order and the same examples in both, and a new Android guide carries a complete shared library instead of a stub. Every code block is annotated, and each example in the guides is assembled as a test.
• The platform symbol catalog, checked against real devices25 Android libraries and 4,416 records carry each symbol's first available API level, alongside 1,168 header constants and 161 structure field offsets covering both Android data models. Every number is compiled back against the NDK headers as a static assertion.
• Output read back by independent readersThe manifest, the resource table and the libraries are read back with the Android SDK tools and the LLVM readers, the resource table matching the platform resource compiler byte for byte across four fixtures, and the release packages ship native binaries for Windows, Linux and Apple Silicon.
• Nesting is bounded, and failures say whereA few kilobytes of nested blocks or parentheses used to end the process with a stack overflow and no message at all. Statements now nest 128 levels, expressions and aggregate literals 64, and documents read at compile time 64, each reported with a location and a reason. A configuration file ending in two quotes no longer reads past its buffer, and an out-of-range escape is rejected instead of wrapping into the valid range.
• A segment respects the alignment it declaresA shared object placed segment addresses by page congruence alone, so .bss and .data could land on addresses that broke the 8-byte alignment they declare. The file position now starts at that alignment, which moves the address and the file offset together. Every built-in format fixture is read back with an independent reader that checks extents, overlap, alignment, and the p_vaddr == p_offset (mod p_align) relation.
• The command line says one thing once--isa is the official spelling and --target keeps working; aarch64, arm64, and a64 are all accepted directly; xirasm init --template replaces the previous four flags; an explicit --target x64 is no longer silently overridden by the project file. Passing an init-only option to an assembly points out where the platform is set.
• A listing you can readListing rows lead with the address and keep the file offset as their own column; bytes the file holds but no fragment claims are listed with their contents instead of an empty cell; and a line produced by a macro expansion carries its depth and the call site that produced it.

The Android platform catalog, checked against real devices.

0.2.22 moves the NDK platform into the assembler: sources import platform libraries by name, structure fields use generated offsets, and the renderer example ships both device ABIs in one package.

• 25 platform libraries behind one importThe catalog records which library provides each of 4,137 platform symbols, from which API level, on which ABIs. Importing a library file welds its name onto the import list, so a source never writes libz.so by hand and cannot pick a library that does not export the symbol.
• Header constants and structure offsets1,168 constants and 161 field offsets generated from the NDK headers cover both Android data models — callback slots and stack frames use generated offsets instead of hand counting. Every number is compiled back against the headers as a static assertion.
• Verified on a deviceA smoke library imports one sample symbol from every platform library and the loader resolves them all at load time; comparing the catalog against the symbols a device actually exports lands at 3,906 of 3,916. The renderer example runs on both ABIs, packed in one archive.