Skip to content

v0.3.0

Choose a tag to compare

@lucialuka lucialuka released this 08 Nov 09:54
· 31 commits to main since this release

Kernel Research

Main Results

  • The full retained control corpus was replayed on an A100. It covered 42 scalar producer/consumer dependency families plus 14 tensor probes. The broader probe generator exposes 541 standalone SM80 PTX forms; those are recorded as inventory-only because a standalone opcode does not define a meaningful dependency edge. The measured minima are mostly S4/S5 for fixed-pipe RAW dependencies, S13 for predicate-to-guard cases, and S1/S2 for the tested store/address cases.
  • The CUTLASS-style load-next/compute-current candidate is implemented. It alternates two fragment register windows, loads the next K fragment between current HMMA groups, preserves the existing async-copy/barrier protocol, and enforces accumulator K-order.

Shape Specific Kernel Optimization

It improved the OA schedule on five shapes:

  • 512×512×2048: about 2.4–2.5% faster.
  • 1024×4096×1024: about 8.2–8.3% faster.
  • 2048×512×512: about 1.8% faster.
  • 4096×1024×1024: about 9.1–9.2% faster.
  • 128×128×128: about 0.7–1.3% faster.
    It regressed 4096×4096×4096 by about 9.8–9.9% and increased register use by 24 registers per thread. The candidate remains shape-specific and experiment-only. Matched ptxas remains faster.
  • Grouped-N CTA traversal was tested against m-fast and Morton-8. All numerical and resource gates passed.
    • 16384×4096×4096: grouped-N improved OA by roughly 6–7% over m-fast and was slightly ahead of Morton.
    • 1024×4096×1024: no stable grouped-N win.
    • 4096×4096×4096: grouped-N was effectively neutral or slightly slower.
      The exact measured results are captured in measured_dispatch_manifest.json. Only exact FP16, 16-byte-aligned, zero-workspace cases are classified as validated-experiment-only; neighboring alignment, workspace, BF16 and shape variants do not inherit the result.
  • The lowered dependency scheduler now runs over actual OA-lowered GEMM blocks in actual_block_schedule.py. HMMA-bearing blocks are accepted only when every physical accumulator group retains K-order. Terminator blocks fail closed. The resulting source-order permutations are recorded in actual-block-schedule.json. No reordered SASS stream has been encoded or promoted.

Engineering CLI

Applied the native-first code changes and added a measured runtime optimization to the production compiler.

Main Production Changes

  • Independent native source files now compile through a bounded ThreadPoolExecutor.
  • Default is four workers, capped at eight.
  • Set OPENASSEMBLER_BUILD_JOBS=1 to restore serial behavior.
  • --dump-ptx stays serial so PTX output remains deterministic and readable.
  • executor.map preserves source order.
  • Each source still passes through the same backend, verification, ptxas, disassembly and manifest gates.
  • Cubin, SASS and manifest publication remains serialized and deterministic.

Compilation Measurements

  • examples/: 5 sources, 14 kernels
    • Serial: 28.42 seconds
    • Four workers: 22.81 seconds
    • Improvement: 1.25×
    • Cubins and manifests: byte-identical
  • Whole repository native scan: 26 candidate sources, 21 compiled entries, 61 OpenAssembler kernels
    • Serial: 29.18 seconds
    • Four workers: 19.62 seconds
    • Improvement: 1.49×
    • Output trees and manifests: byte-identical
    • Five files still fail because they use unsupported constructs such as ld.global.v2, bar.warp.sync, or unsupported FP32 modifiers. These remain explicit failures rather than silent fallbacks.

Native-default Frontend Behavior Validation:

  • The following command now fails clearly because the repository has no native kernels and application capture was not explicitly requested
openassembler compile testcases/test_whole_repo --dry-run 
  • The following command correctly selects the application frontend.
openassembler compile testcases/test_whole_repo --frontend torch --backend modal --verify --dry-run
  • A full explicit Torch capture/replay completed on the A100 with:
    • 2 captured graphs
    • 6 optimizer steps
    • 0 new GPU code generation during replay
    • 77 tensors checked
    • verification status: ok