wai-quantum 0.5.0: provenance, sampling members, device programs, OpenCL, a simulated FPGA, f64 on accelerators, and QPU clients #253
Loading…
Reference in a new issue
No description provided.
Delete branch "wai/quantum-0.5.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
wai-quantum 0.5.0, and a new crate, wai-quantum-qpu 0.1.0. The changelog entry in
wai/CHANGELOG.mdlists everything; in short:Certificategains a public field, hence 0.5.0.Sampler, statistical certification on theqpu-v1corpus, a virtual QPU, and a virtual device that compiles each circuit for its coupling map and native basis and charges noise for the program it would run.rz/sx/x/cz,prx/czandgpi/gpi2/zz(angles in turns), routed over a coupling map; every program verified against its circuit by simulation.quantum_fabric_opencl).quantum_fabric_fpga): a Verilog datapath, each 32×32 product from four 16-bit partial products, compiled at run time by Verilator.quantum_fabric::sv64, withquantum_sv): the CPU's own launches, each an IEEE binary64 operation with no fused multiply-add, on CUDA and on OpenCL devices with binary64.QpuSampler, and thewai-qpucommand (device, bit-order probe, certification).Verified before the push
On the build host (macOS, M4 Max):
cargo test --release --features full: every test passes; the default, no-default, wasm32 and wasip2 builds; the f64 planner and replay against the CPU, bit for bit, with the pinned digest; every dependent crate (wai-rs,wai-pack,wai-quantum-serve,wai-webfor wasm32,quantum-meter,quantum-wgsl-check) checks against its lockfile.On the hardware host (x86_64 Linux):
Clippy reports no warning or error in the code this change adds. With every feature on, it reports seven errors in
repro.rsandquantum_spd.rs, untouched here and present on main.After the merge
The hardware host's jobs now read their device lists from the host (
WAI_QUANTUM_HW_WEBGPU_EXPECT,WAI_QUANTUM_HW_OPENCL_EXPECT), defaulting to today's. Once this merges, the host gains the integrated GPU in one step: the declarations in its runner environment, render-node access for the runner's user, and a runner restart.🤖 Generated with Claude Code