runD 1.0.1 Alpha
Pre-release
Pre-release
runD 1.0.1 Alpha
This alpha restructures repeated Compute execution around a compact,
tile-local nested plan. It removes the intermediate repeated-descriptor memory
layer and keeps execution, replay, and installed-SDK behavior tied to one
canonical plan identity.
Highlights
- Added
tile_repeat<N>for bounded nested repetition without materializing a
descriptor per repeated invocation. - Reworked nested-plan lowering and execution so plan memory is proportional
to the tile structure rather than the expanded repeat count. - Added checked count, offset, and identity arithmetic with deterministic
overflow and capacity failure behavior. - Kept CPU, Metal, and Vulkan on the same public nested-plan contract, with
backend-specific verification and parity coverage. - Updated the installed SDK, exact-version CMake consumers, performance
measurement routes, and API/ABI documentation for version1.0.1.
Darwin ARM64 SDK
The three attached files form one release:
rund-sdk-1.0.1-darwin-arm64.tar.gzrund-sdk-1.0.1-darwin-arm64.sha256rund-verify
Keep them together and verify the sealed producer and host tuple before use:
chmod +x ./rund-verify
sh ./rund-verify \
./rund-sdk-1.0.1-darwin-arm64.tar.gz \
./rund-sdk-1.0.1-darwin-arm64.sha256 \
"$PWD"The archive SHA-256 is:
ed7b59b2a92fce04982306ce84bf979c0558f6284b71b4d7db69cdc718aadc32
Verification
- Clean Release build: 1,947 / 1,947 targets.
- Release and installed-SDK contracts: 25 / 25 passed.
- Exact extracted archive, 337-header closure, package identity, documentation
examples, CPU, Metal, and Vulkan consumer routes passed. - Source commit:
389c036c702458668d0e1b89e06477f1b1d6c3aa.
Alpha scope
- Darwin ARM64 is the supported binary SDK tuple.
- The Linux x64 source-candidate workflow for this tag stopped during the
build because GCC 13 promoted an aggressive-loop-optimization diagnostic in
pre-existingarena.cppcode to an error. No Linux artifact is attached;
see workflow run 30624371425. - Windows x64 is not supported.
- Exact package identity
1.0.1is intentionally not ABI-compatible with
1.0.0because the alpha public by-value plan representation changed. - The Metal warm path still walks frozen descriptors on the host; eliminating
that remaining host loop stays open in issue #1.