summaryrefslogtreecommitdiff
path: root/test/unit/input
diff options
context:
space:
mode:
authorDerek Schuff <dschuff@chromium.org>2024-12-06 12:34:19 -0800
committerGitHub <noreply@github.com>2024-12-06 20:34:19 +0000
commit729ea41d145d369b203dca6f70b251ea365cb3d0 (patch)
tree269217c2d17d6e8a4a59eb6b822aa4cdac17aa28 /test/unit/input
parent3f82ffc70362bf967d91d3cb56ee4c8c5ebe1161 (diff)
downloadbinaryen-729ea41d145d369b203dca6f70b251ea365cb3d0.tar.gz
binaryen-729ea41d145d369b203dca6f70b251ea365cb3d0.tar.bz2
binaryen-729ea41d145d369b203dca6f70b251ea365cb3d0.zip
Add bulk-memory-opt feature and ignore call-indirect-overlong (#7139)
LLVM recently split the bulk-memory-opt feature out from bulk-memory, containing just memory.copy and memory.fill. This change follows that, making bulk-memory-opt also enabled when all of bulk-memory is enabled. It also introduces call-indirect-overlong following LLVM, but ignores it, since Binaryen has always allowed the encoding (i.e. command line flags enabling or disabling the feature are accepted but ignored).
Diffstat (limited to 'test/unit/input')
-rwxr-xr-xtest/unit/input/bulkmem_target_feature.wasmbin219 -> 223 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/test/unit/input/bulkmem_target_feature.wasm b/test/unit/input/bulkmem_target_feature.wasm
index 3c69d2323..7a762820c 100755
--- a/test/unit/input/bulkmem_target_feature.wasm
+++ b/test/unit/input/bulkmem_target_feature.wasm
Binary files differ