Skip to content
Branch of the spec repo scoped to discussion of SIMD in WebAssembly
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
document [spec] Add missing UTF-8 side condition (#928) Dec 6, 2018
interpreter [interpreter] Add missing ')' (#931) Dec 11, 2018
papers Rectify licensing (#496) Jun 13, 2017
proposals/simd Add ChakraCore implementation status (#76) May 1, 2019
test Remove tests/html. Dec 11, 2018
.gitattributes Adjust .gitattribute Mar 22, 2017
.gitignore [infra] Update .gitignore Jul 31, 2017
.gitmodules Revising specs in preparation for FPWD. (#626) Feb 12, 2018
.travis.yml Pin sphinx to v1.7.9 to workaround upstream bug (#875) Sep 13, 2018 Fix an obvious broken link. Aug 13, 2015
LICENSE Rectify licensing (#496) Jun 13, 2017 Merge branch 'spec-master' Dec 11, 2018
deploy_key.enc Improve build and fix typos (#628) Jan 3, 2018

SIMD proposal for WebAssembly

This repository holds a proposal for adding 128-bit SIMD support to WebAssembly. It is a copy of the WebAssembly/spec repository with the addition of a proposals/simd directory. The proposal describes how 128-bit packed SIMD types and operations can be added to WebAssembly. It is based on previous work on SIMD.js in the Ecma TC39 ECMAScript committee and the portable SIMD specification that resulted.

The proposed specification has the details.

Design issue

Original README from upstream repo follows...


This repository holds a prototypical reference implementation for WebAssembly, which is currently serving as the official specification. Eventually, we expect to produce a specification either written in human-readable prose or in a formal specification language.

It also holds the WebAssembly testsuite, which tests numerous aspects of conformance to the spec.

View the work-in-progress spec at

At this time, the contents of this repository are under development and known to be "incomplet and inkorrect".

Participation is welcome. Discussions about new features, significant semantic changes, or any specification change likely to generate substantial discussion should take place in the WebAssembly design repository first, so that this spec repository can remain focused. And please follow the guidelines for contributing.

You can’t perform that action at this time.