Clone this repo:
  1. 2da77d3 Remove FastISel expected failures (#217) by jgravelle-google · 3 days ago master
  2. bf7d3da Update run_known_gcc_test_failures.txt (#216) by jgravelle-google · 4 days ago
  3. a709ab3 Pass extras to outname_ctor (#213) by Sam Clegg · 6 days ago
  4. 75120d0 Build musl as wasm object files as well as .s files (#215) by Sam Clegg · 6 days ago
  5. 4277ef7 Build lld from sbc's branch (#214) by Sam Clegg · 6 days ago


༼ ༎ຶ ෴ ༎ຶ༽ If it’s not tested, it’s already broken.

Luckily, this repository has some tests: Build Status

What's this?

This repository holds the code which make the WebAssembly waterfall‘s heart beat. You may want to see the waterfall in action, and if you don’t like what you see you may even want to contribute.

What's a waterfall?

WebAssembly has many moving parts and no central owner. Some of these interact closely, some implement the same thing. A build and test waterfall allows us to:

  • Have simple build instructions for each component.
  • Archive build logs and build artifacts.
  • Identify which build artifacts are known-good.
  • Know which tests matter.
  • Make tests easily executable.
  • Know which configurations matter (build flavor, host OS, host architecture, ...).
  • Cause inadvertent breakage less often.
  • When breakage occurs, identify it quickly and reverted / silenced / fixed easily.
  • When a big change is required, know which moving parts should synchronize.
  • Make the feature implementation status straightforward to check for each component.

We should keep process to a minimum, try things out, see what works.