You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WebAssembly SIMD: memory, lane, shuffle, and bitwise operations #280
15343076 implements v128.const, scalar/vector splats, every extract/replace lane form, shuffle/swizzle, bitselect, any_true, and v128 bitwise operations.
2d27127b implements v128 load/store, load-extend, load-splat, load-zero, and every lane load/store form with portable little-endian behavior and pre-mutation bounds checks.
Focused evidence is green: the lane/bitwise and memory suites each run with the shared root/private checks (3/3). Memory coverage includes unaligned+offset addressing, exact 128-bit round trips, signed widening, zero loads, lane preservation, and atomic OOB traps.
Next I am tightening the width-specific lane-immediate validator, then wiring the pinned official SIMD corpus so this issue closes on auditable totals rather than only hand-built modules.
Pinned SIMD corpus scoring is now reproducible on main in f44e364d. The runner uses the exact WebAssembly/simd revision a78b98a6899c9e91a13095e560767af6e99d98fd, WABT 1.0.39 / ad75c5edcdff96d73c245b57fbc07607aaca9f95, the raw u128 conformance boundary, and a declared 20-file #280 selection from the 56-file proposal suite.
Current transparent audit: 2,069 / 2,253 applicable pass, 184 fail, 351 explicit text-format n/a, 0 runner errors (2,604 total commands). Fully green owned files already include address, alignment, bitwise, every lane load/store width, load-extend, load-splat, load-zero, and store. simd_bitwise.wast is 169/169 and simd_align.wast is 66/66 applicable.
The remaining 184 failures are not hidden runner gaps: they are execution traps from later integer/float operation families used as contextual operands inside simd_boolean, simd_const, simd_lane, simd_load, and simd_splat. I am leaving #280 open until those shared official files turn fully green through #281/#282, then I will check in the zero-failure inventory and update README/docs with terminal totals.
README and WebAssembly status now publish the live pinned score in 1fc8c91c. After the three portable integer checkpoints, the declared 20-file audit is 2,240/2,253 applicable, 13 fail, 351 explicit text-format n/a, 0 runner errors. Eighteen files are fully green. The only remaining shared-file failures are float/conversion contexts assigned to #282; no #280 memory/lane/bitwise failure remains.
execution: 15343076, 2d27127b, 7e3bb69f, plus shared integer/float context checkpoints through 6306ed59
pinned runner: f44e364d
checked-in terminal inventory and README/docs: 9aa42500
exact result: 2,253/2,253 applicable pass, 0 fail, 351 explicit text-format n/a, 0 runner errors, across the declared 20-file selection from all 56 pinned proposal files
verifier locks repository/commit, 56 available files, 20 scored files, command totals, terminal zero-failure state, and detailed file count
All six acceptance items are checked. Later arithmetic/conversion families remain explicitly owned by #281/#282; terminal whole-SIMD score/performance remains #283.
Activity
feat(wasm): execute SIMD lane and bitwise ops (#280)
feat(wasm): execute SIMD memory and lane access (#280)
chrisbbreuer commentedon Jul 18, 2026
Two small execution checkpoints are now on
main:15343076implementsv128.const, scalar/vector splats, every extract/replace lane form, shuffle/swizzle, bitselect, any_true, and v128 bitwise operations.2d27127bimplements v128 load/store, load-extend, load-splat, load-zero, and every lane load/store form with portable little-endian behavior and pre-mutation bounds checks.Focused evidence is green: the lane/bitwise and memory suites each run with the shared root/private checks (3/3). Memory coverage includes unaligned+offset addressing, exact 128-bit round trips, signed widening, zero loads, lane preservation, and atomic OOB traps.
Next I am tightening the width-specific lane-immediate validator, then wiring the pinned official SIMD corpus so this issue closes on auditable totals rather than only hand-built modules.
fix(wasm): validate SIMD memory lane widths (#280)
test(wasm): add pinned SIMD corpus profile (#280)
chrisbbreuer commentedon Jul 18, 2026
Pinned SIMD corpus scoring is now reproducible on
maininf44e364d. The runner uses the exactWebAssembly/simdrevisiona78b98a6899c9e91a13095e560767af6e99d98fd, WABT 1.0.39 /ad75c5edcdff96d73c245b57fbc07607aaca9f95, the rawu128conformance boundary, and a declared 20-file #280 selection from the 56-file proposal suite.Current transparent audit: 2,069 / 2,253 applicable pass, 184 fail, 351 explicit text-format n/a, 0 runner errors (2,604 total commands). Fully green owned files already include address, alignment, bitwise, every lane load/store width, load-extend, load-splat, load-zero, and store.
simd_bitwise.wastis 169/169 andsimd_align.wastis 66/66 applicable.The remaining 184 failures are not hidden runner gaps: they are execution traps from later integer/float operation families used as contextual operands inside
simd_boolean,simd_const,simd_lane,simd_load, andsimd_splat. I am leaving #280 open until those shared official files turn fully green through #281/#282, then I will check in the zero-failure inventory and update README/docs with terminal totals.docs(wasm): publish live SIMD corpus score (#280)
chrisbbreuer commentedon Jul 18, 2026
README and WebAssembly status now publish the live pinned score in
1fc8c91c. After the three portable integer checkpoints, the declared 20-file audit is 2,240/2,253 applicable, 13 fail, 351 explicit text-format n/a, 0 runner errors. Eighteen files are fully green. The only remaining shared-file failures are float/conversion contexts assigned to #282; no #280 memory/lane/bitwise failure remains.docs(wasm): publish terminal SIMD movement score (#280)
chrisbbreuer commentedon Jul 18, 2026
Closed with terminal evidence on
main:15343076,2d27127b,7e3bb69f, plus shared integer/float context checkpoints through6306ed59f44e364d9aa42500All six acceptance items are checked. Later arithmetic/conversion families remain explicitly owned by #281/#282; terminal whole-SIMD score/performance remains #283.