mattdesl / mattdesl/mp4-wasm-encoder
Compiling code with NEON intrinsics to Wasm SIMD
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 76
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
> Ensure that WASM version of minih264 library is indeed taking advantage of SIMD (lots of NEON code that doesn't compile there)
Really cool work :)
I'm wondering if you tried https://emscripten.org/docs/porting/simd.html#compiling-simd-code-targeting-arm-neon-instruction-set. @seanptmaher did some work in SIMDe + Emscripten (cc @tlively), which transparently supports a subset of ARM NEON intrinsics. This might get you over some of the compilation errors, and could help with performance too.
Also, I work on WebAssembly SIMD in V8, if you have questions or bug reports, please file an issue on me (zhin@chromium.org) at https://bugs.chromium.org/p/v8/issues/entry. Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or build entry points are named. Start with the Emscripten SIMD documentation linked in the issue, then inspect how the WebAssembly build handles the minih264 NEON code. Done means the WASM build compiles successfully and the resulting library demonstrably uses SIMD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- compilers, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100