- Host: Google Hangouts
- Dates: Tuesday August 22, 2017
- Times: 9:00am–10:00am Pacific Time
- Location: same Google Hangouts link as before
- Contact:
- Name: JF Bastien
- Email: [email protected]
None required if you've attended before. Email JF Bastien to sign up if it's your first time. The meeting is open to CG members only.
The meeting will be a Google Hangouts call.
- Opening, welcome and roll call
- Opening of the meeting
- Introduction of attendees
- Find volunteers for note taking (Luke Wagner to volunteer)
- Adoption of the agenda
- Proposals and discussions
- Upcoming meetings (Luke Wagner)
- Presentation on JS/wasm modules integration, mostly stage-setting (Domenic Denicola)
- State of WebAssembly tooling (Derek Schuff and Alon Zakai)
- WebAssembly/JS integration specification (Daniel Ehrenberg) (5 minutes; early draft of Bikeshed conversion)
- Closure
Ben Smith won't be able to attend this meeting. Delaying his presentation.
- Bulk Memory Instructions (Ben Smith)
- WIP proposal
- Some initial performance numbers
- Option to skip data segment initialization (Ben Smith)
None.
Dates | Location | Host |
---|---|---|
2017-11-01 to 2017-11-02 | Santa Clara, CA | Intel |
2017-11-06 to 2017-11-07 | Burlingame, CA | TPAC |
- Alon Zakai
- Dan Ehrenberg
- Deepti Gandluri
- Derek Schuff
- Domenic Denicola
- Edgar Pek
- Heejin Ahn
- Jacob Gravelle
- Keith Miller
- Limin Zhu
- Mark Nottingham
- Martin Becze
- Michael Holman
- Patrick Hickey
- Peter Jensen
- Sam Clegg
- Thomas Nattestad
- Tyler McMullen
- Unbug Lee
- Venkat Josyula
- 于 航 (Hang Yu)
- 徐朝逸 (Chao Yi)
- Mingfei Fan
- Sergey Rubanov
- Robert Hitchcock
- Patrick Hickey
- Saam Barati
- Yury Delendik
- Derek Schuff seconds adoption
- LW: See 2017/CG-11.md
- DD: Yay! Excited about use of Web IDL and Bikeshed
-
KM: Toolchain integration?
-
DD: Mostly this would be work around establishing toolchain conventions.
-
LW: Some work on this already with SystemJS and webpack folks. More work ongoing.
-
MH: Adding new core types for TypedArray in slide example?
-
LW: No, these come with the JS Binding Section proposal. Concrete proposal forthcoming from Brad
-
General status:
-
Emscripten MVP support is pretty complete. It also still supports asm.js.
- Emscripten has JS loader and module interface code, as well as some JS/Wasm interop/marshaling tools (e.g. embind, WebIDL binder). These are just libraries and conventions, it would be good to ensure they work well with proposed module/JS conventions.
- There's been a big uptick in interest in wasm the last few months, reflected in user interest and discussion on emscripten mailing list, new users trying it out, bugs filed, etc.
- Rust has experimental wasm support currently via fastcomp (but working on switching to wasm backend). Still plenty of library/runtime stuff left to do.
-
Current work/upcoming features:
- Effort to replace asm2wasm pipeline (which uses asm.js “fastcomp” out-of-tree LLVM backend, and converts the result to wasm) with direct WebAssembly backend in upstream LLVM. Performance and feature support is close, and we (Mozilla and Google) are working to stamp out the remaining bugs and blockers. This is mostly a maintainability thing, and will hopefully be transparent to emscripten users, but good for non-C interoperability and other tool authors.
- Threads support to go along with wasm atomics proposal.
- Zerocost C++ exceptions support to go along with wasm exceptions proposal.
- Wasm object files and linking via lld
-
KM: Exception handling work going on in mainline LLVM or Emscripten branch?
-
DS: LLVM work is in mainline LLVM. Also some work in Emscripten’s non-LLVM parts (e.g. libcxxabi and the JS module wrapper). Some explanation of Exception Handling.
-
Fuzzing and Reducer tools now available! They’ve found lots of bugs, if you make a wasm tool, you should try them!
-
MH: Does fuzzer work on Windows?
-
AZ: Fuzzer does, Reducer doesn’t b/c system call usage.