summaryrefslogtreecommitdiff
path: root/third_party/llvm-project/include/llvm/ObjectYAML/DWARFYAML.h
diff options
context:
space:
mode:
authorAlon Zakai <azakai@google.com>2020-08-06 19:17:13 -0700
committerGitHub <noreply@github.com>2020-08-06 19:17:13 -0700
commitcdc38d3162eb62cb313704f264f17d230989084b (patch)
tree9bc8ba453e5030ee9371f28af6782ea20e1649f5 /third_party/llvm-project/include/llvm/ObjectYAML/DWARFYAML.h
parent1b102f2ca87d54781b10110c375ea7d0cf5da837 (diff)
downloadbinaryen-cdc38d3162eb62cb313704f264f17d230989084b.tar.gz
binaryen-cdc38d3162eb62cb313704f264f17d230989084b.tar.bz2
binaryen-cdc38d3162eb62cb313704f264f17d230989084b.zip
Fuzzing: Compare wasm2js to the interpreter (#3026)
Comparing to the interpreter, and not just wasm2js to itself (which we've done on the same file before and after opts) ensures wasm2js has the right semantics. To do this, we need to make sure the wasm doesn't contain things where wasm2js semantics diverge from normal wasm, which includes: * Legalize so that there are no i64 exports. * Remove operations JS can't handle with full precision, like i64 -> f32. * Force all loads/stores to be 1-byte, as unexpectedly-unaligned operations fail in wasm2js. This also requires ignoring subnormals when comparing between JS VMs and the interpreter.
Diffstat (limited to 'third_party/llvm-project/include/llvm/ObjectYAML/DWARFYAML.h')
0 files changed, 0 insertions, 0 deletions