commit 5e67e5c19fd337d1b7e5601d162d3e21d01e11e5
author Mike Klein <mtklein@google.com> Mon Mar 04 13:45:10 2019 -0600
committer Skia Commit-Bot <skia-commit-bot@chromium.org> Wed Mar 06 18:10:46 2019 +0000
tree dbbe4b50b8c5dc75e2d23b31e47719015852c166
parent 10736f2da359a4adf7545795351fd904d0ad4133

add emscripten builds, with and without SIMD

These build, and hit each side of __wasm_simd128__.
I can disassemble the wasm and see v128 used where appropriate:

    ~/skcms (emcc↑1|✔) $ wasm-objdump -d out/emscripten/skcms.o | grep -q v128 && echo ok || echo no
    no
    ~/skcms (emcc↑1|✔) $ wasm-objdump -d out/emscripten.simd/skcms.o | grep -q v128 && echo ok || echo no
    ok

I should note that in order to build the .simd version,
I had to follow these directions to get a bleeding-edge toolchain:

    https://brionv.com/log/2019/03/03/simd-in-webassembly-tales-from-the-bleeding-edge/

Setting exe=.html creates some handy html/js/wasm files as
the output that you can serve up locally (python -m SimpleHTTPServer)
and run.  Currently failing due to filesystem IO, but it's a start.

    expect(load_file(filename, &buf, &len)) failed at tests.c:615

Change-Id: Ib9473584b43ec35ea2bb81d9765c6814b5084e89
Reviewed-on: https://skia-review.googlesource.com/c/skcms/+/197180
Reviewed-by: Mike Klein <mtklein@google.com>
Commit-Queue: Mike Klein <mtklein@google.com>