All benchmarks are currently built by a Dockerfile located in the
benchmark directory that emits a single benchmark.wasm file. This
leads to some weirdness, like all of the shootout sub-benchmarks
living in separate folders, duplicating a lot of the infrastructure
files. This same issue will affect other multi-file benchmarks, like
libsodium, which I have queued up to submit if this change is merged.
What this change does is modify where the build.sh script expects the
benchmark artifacts to be placed. Whereas previously the Dockerfile
had to place a single file at /benchmark.wasm, we now can place
multiple files in a /benchmark directory. All of these files will be
extracted by build.sh into the benchmark directory.
This commit attempts to change nothing else: only the "where to place
the files" bit. But that apparently requires modifications to several
Dockerfiles with ensuing changes to the emitted WebAssembly. The
binary changes should not be due to any change in logic.
All benchmarks are currently built by a
Dockerfilelocated in the benchmark directory that emits a singlebenchmark.wasmfile. This leads to some weirdness, like all of theshootoutsub-benchmarks living in separate folders, duplicating a lot of the infrastructure files. This same issue will affect other multi-file benchmarks, likelibsodium, which I have queued up to submit if this change is merged.What this change does is modify where the
build.shscript expects the benchmark artifacts to be placed. Whereas previously theDockerfilehad to place a single file at/benchmark.wasm, we now can place multiple files in a/benchmarkdirectory. All of these files will be extracted bybuild.shinto the benchmark directory.This commit attempts to change nothing else: only the "where to place the files" bit. But that apparently requires modifications to several
Dockerfileswith ensuing changes to the emitted WebAssembly. The binary changes should not be due to any change in logic.