Closed Bug 1659900 Opened 4 years ago Closed 3 years ago

[meta] Track SIMD instruction renamings and renumberings

Categories

(Core :: JavaScript: WebAssembly, task, P2)

task

Tracking

()

RESOLVED FIXED

People

(Reporter: lth, Assigned: yury)

References

(Blocks 1 open bug)

Details

(Keywords: meta)

There are some fairly superficial SIMD instruction renamings probably on the way as the spec is being firmed up:

https://github.com/WebAssembly/simd/issues/297
https://github.com/WebAssembly/simd/issues/316

Mostly these change in wasmparser/wat, and here the changes are important so as to be interoperable.

But it would be good for us to rename also throughout the engine to stay more in sync with the source level names. (In fairness, we've diverged a bit on Wasm opcode names over time and could benefit from general cleanup.)

The naming changes have landed in the spec interpreter, so I guess we're not compliant now.

Assignee: nobody → lhansen
Status: NEW → ASSIGNED
Type: task → defect

SIMD renaming is landing in wasm-tools: https://github.com/bytecodealliance/wasm-tools/pull/105. It'll likely be hellish to merge this as we'll have to update instruction names in many of our (currently private) simd tests. Let's hope we don't need an emergency fix for wasm-tools...

Depends on: 1669668

Renamings for the three tickets mentioned in comment 0, comment 2 will be landed as part of bug 1669668. The present bug will remain open to track further renamings.

Keywords: meta
Summary: Track SIMD instruction renamings → [meta] Track SIMD instruction renamings
Severity: S3 → N/A
Type: defect → enhancement
Type: enhancement → task

There's a Final Renumbering coming once the instruction set is frozen, any day now.

Priority: P3 → P2
Summary: [meta] Track SIMD instruction renamings → [meta] Track SIMD instruction renamings and renumberings
Assignee: lhansen → ydelendik
Blocks: 1695585

I think this is done?

Flags: needinfo?(ydelendik)
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(ydelendik)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.