Concrete optimization targets
Instructions, register pressure, dependency chains, memory access, SIMD width, branches and cycles are directly visible. The distance between generated code and measured hardware behavior is small.
Asmory treats ISA versions, CPU extensions, ABI and object format as real dependency-resolution inputs. Reuse machine-level code without erasing the machine contract.
AVX2, AVX-512, SVE2 and RVV are compatibility constraints, not decorative tags.
One package version can carry several machine implementations and let the resolver choose legally.
The current registry and CLI are static x86-64 ELF programs built with GNU as + ld.
Assembly used to trade maximum control for maximum human cost. AI weakens that trade-off: coding models can generate and tune low-level kernels, while Assembly gives them a brutally short path from edit to benchmark.
Instructions, register pressure, dependency chains, memory access, SIMD width, branches and cycles are directly visible. The distance between generated code and measured hardware behavior is small.
For small kernels, the path can be as short as edit → assemble → run → benchmark → inspect → repeat. Fewer high-level compilation stages means more experiments per minute.
If developers already describe intent, let AI implement it, then validate the result, the old requirement to manually manage every Assembly detail becomes less absolute.
Today, optimized kernels are often scattered across snippets, gists and larger projects. Asmory wants the same find → add → reuse workflow developers expect from Cargo, PyPI and npm - without hiding the machine contract.
$ asmory add fast-memcpy $ asmory add simd-json-scan $ asmory add avx2-dot resolve ISA + ABI + object + OS select compatible Variant link only what survives
In the AI era, Assembly may finally deserve a modern package ecosystem. Asmory exists to find out how far that idea can go.
Source development can live on GitHub, GitLab or anywhere else. Asmory stores the immutable package records that resolvers consume.
The bootstrap client reads CPUID and XGETBV directly, including OS support for AVX extended register state.
$ ./build/asmory target Asmory host target Target arch x86_64 os linux object elf64 abi sysv64 ISA baseline x86-64-v3 features avx2 yes fma yes bmi2 yes avx512f no
A Variant must survive correctness filtering before performance preference is even considered.