5996b03abb
Some checks failed
wai-det-jpegai WAISM float-level module of record / does this change touch it (push) Successful in 38s
wai-det-jpegai WAISM float-level module of record / linux · both checkers, F1, F2 on wasmtime (Cranelift, Winch, Pulley) and Wasmi, the planted faults (push) Has been cancelled
wai-det-jpegai WAISM float-level module of record / linux-arm64 · both checkers, F1, F2 on wasmtime (Cranelift, Winch, Pulley) and Wasmi, the planted faults (push) Has been cancelled
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (push) Has been cancelled
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (push) Has been cancelled
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (push) Has been cancelled
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Has been cancelled
The JPEG AI exact decoder at WAISM's float level follows the decoder's new scope (D74): the module corpus (corpus.py) adds every configuration vector over the jpegai/v1 bundle, each in scope to the native exact decoder's pinned RGB8, the two the reference leaves to the machine to the refusal configuration_undetermined, and each the decoder does not implement to the sink's module_trap, which the host now lets a case expect. The module of record (record/) is rebuilt from this tree on Linux x86_64 (673,221 bytes, fdef6d19...); both checkers hold it at the float level and refuse it R3 at the integer level. The workflow runs every case on Cranelift and Winch and the jpegai/v1 cases on the two interpreters, which take minutes a configuration vector; the README records every case on all four. Co-Authored-By: Claude Opus 5.5 <[email protected]>
16 lines
1.3 KiB
JSON
16 lines
1.3 KiB
JSON
{
|
|
"format": "waism-module-record/1",
|
|
"about": "The module of record of wai-det-jpegai, the JPEG AI exact decoder: WAISM's float level (extensions/waism.md, waism/1-det), held there by both of the profile's checkers and refused R3 at the integer level. The file is named by its SHA-256; the CI step module-check.sh holds this directory to it.",
|
|
"level": "waism/1-det",
|
|
"files": {
|
|
"wai_det_jpegai.wasm": {
|
|
"sha256": "e13ebb9640dec9d576df61cb834c6e4c5fdd8c271c60a7b4dc343fa6987fa2bb",
|
|
"bytes": 673165,
|
|
"build": "scalar"
|
|
}
|
|
},
|
|
"source": "wai/wai-det-jpegai, wai/wai-rs and wai/wai-ops as main had them at f218af5ac0f364df5d8af1d6755df59bac99e778 (the commit that adds this file changes none of the module's sources), with the crates Cargo.lock pins",
|
|
"cargo_lock_sha256": "b9029677a6e96468855f21d1388979c706aa47870eac6554037b57f7df2620e0",
|
|
"toolchain": "rustc 1.99.1 (58cf8f9c3 2026-10-13) on Linux x86_64, target wasm32-unknown-unknown",
|
|
"build": "build.sh's build, its cargo command and RUSTFLAGS: release, one codegen unit, fat LTO, panic=abort, the memory's maximum 8,192 pages; the checkout, the Cargo home and the toolchain remapped to /open-standards, /cargo and /rustup. Held at the float level, and refused R3 at the integer level, by the Rust checker on the host that built it and by both checkers in module-check.sh"
|
|
}
|