Assembly package ecosystem

Packages for the instruction level.

Asmory treats ISA versions, CPU extensions, ABI and object format as real dependency-resolution inputs. Reuse machine-level code without erasing the machine contract.

ISA-aware

AVX2, AVX-512, SVE2 and RVV are compatibility constraints, not decorative tags.

Variant-oriented

One package version can carry several machine implementations and let the resolver choose legally.

Assembly-first

The current registry and CLI are static x86-64 ELF programs built with GNU as + ld.

Why Asmory · Why now?

AI changes the economics of low-level programming.

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.

01

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.

02

A tiny feedback loop

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.

03

Vibe coding meets machine code

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.

The missing layer

Assembly still has no modern package ecosystem.

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.
Package-index semantics

Not a Git forge. A distribution registry.

Source development can live on GitHub, GitLab or anywhere else. Asmory stores the immutable package records that resolvers consume.

Projectsimd-dot
Release0.1.0
Variantx86_64-avx2-fma
Artifacttar.gz + SHA-256
Resolververify → build
Working CLI

Ask the machine first.

The bootstrap client reads CPUID and XGETBV directly, including OS support for AVX extended register state.

asmory target
$ ./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
Resolver model

Architecture is only the first coordinate.

A Variant must survive correctness filtering before performance preference is even considered.

Packagesimd-dot
Version0.1.0
Variantx86_64-avx2-fma
TargetELF64 / SysV64
Resolvercompatible → tuned