Open Bug 1640593 Opened 4 years ago Updated 4 years ago

Debugger support for Wasm SIMD

Categories

(DevTools :: Debugger, task, P3)

task

Tracking

(Not tracked)

People

(Reporter: lth, Unassigned)

References

(Blocks 2 open bugs)

Details

The debugger must provide a sensible view of wasm SIMD data (as sensible a view as it provides of other data, whatever the current situation may be). This may be slightly more challenging than for other data, as SIMD data have no standard / direct representation in JS.

Depends on: 1644759

Bug 1644759 introduces a synthetic representation for v128 in ToJSValue: the int32 value of lane 0. Better representations might be array-of-byte, array-of-unsigned-byte, array-of-int32, ArrayBuffer, Int8Array, etc, etc. Discuss.

Blocks: dbg-wasm
Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.