Memory flattening cannot be done in the presence of DataDrop (#5521)

Like MemoryInit, this instruction cares about segment identity, so merging
segments into one big one for flattening is disallowed.

1 files changed, 38 insertions, 0 deletions

diff --git a/test/lit/ctor-eval/data_drop.wast b/test/lit/ctor-eval/data_drop.wast
new file mode 100644
index 000000000..eeec5f165
--- /dev/null
+++ b/test/lit/ctor-eval/data_drop.wast
@@ -0,0 +1,38 @@
+;; NOTE: Assertions have been generated by update_lit_checks.py --all-items and should not be edited.
+;; RUN: wasm-ctor-eval %s --ctors=test --kept-exports=test --quiet -all -S -o - | filecheck %s
+
+(module
+  ;; CHECK:      (type $none_=>_none (func))
+
+  ;; CHECK:      (memory $0 1)
+  (memory $0 1)
+  (data (i32.const 0) "__________")
+  (data (i32.const 20) "__________")
+
+  (func "test"
+    ;; A store that can be evalled, but we do not do so because of the
+    ;; instruction after us.
+    (i32.store8
+      (i32.const 4)
+      (i32.const 100)
+    )
+
+    ;; A memory init cannot be evalled since ctor-eval flattens memory segments
+    ;; atm. In fact the module would not validate as we refer to segment 1 here
+    ;; but after flattening only segment 0 exists.
+    (data.drop 1)
+  )
+)
+;; CHECK:      (data (i32.const 0) "__________")
+
+;; CHECK:      (data (i32.const 20) "__________")
+
+;; CHECK:      (export "test" (func $0))
+
+;; CHECK:      (func $0 (type $none_=>_none)
+;; CHECK-NEXT:  (i32.store8
+;; CHECK-NEXT:   (i32.const 4)
+;; CHECK-NEXT:   (i32.const 100)
+;; CHECK-NEXT:  )
+;; CHECK-NEXT:  (data.drop 1)
+;; CHECK-NEXT: )