From 35a237db1b96b37cfa7638d2f8d22aa46a626683 Mon Sep 17 00:00:00 2001
From: Alon Zakai <azakai@google.com>
Date: Mon, 10 Apr 2023 09:48:23 -0700
Subject: Do not flatten memory when array.new_data is present (#5650)

Like data.drop etc., it notices data segment identity.
---
 test/lit/ctor-eval/array_new_data.wast | 38 ++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 test/lit/ctor-eval/array_new_data.wast

(limited to 'test/lit/ctor-eval/array_new_data.wast')

diff --git a/test/lit/ctor-eval/array_new_data.wast b/test/lit/ctor-eval/array_new_data.wast
new file mode 100644
index 000000000..3dca60207
--- /dev/null
+++ b/test/lit/ctor-eval/array_new_data.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:      (type $[i8] (array i8))
+ (type $[i8] (array i8))
+
+ ;; CHECK:      (memory $0 (shared 16 17))
+ (memory $0 (shared 16 17))
+ ;; CHECK:      (data $0 (i32.const 40) "")
+ (data $0 (i32.const 40) "")
+ ;; CHECK:      (data $1 (i32.const 0) "")
+ (data $1 (i32.const 0) "")
+
+ (func "test"
+  ;; An array.new_data 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.
+  (drop
+   (array.new_data $[i8] $1
+    (i32.const 16)
+    (i32.const 8)
+   )
+  )
+ )
+)
+;; CHECK:      (export "test" (func $0))
+
+;; CHECK:      (func $0 (type $none_=>_none)
+;; CHECK-NEXT:  (drop
+;; CHECK-NEXT:   (array.new_data $[i8] $1
+;; CHECK-NEXT:    (i32.const 16)
+;; CHECK-NEXT:    (i32.const 8)
+;; CHECK-NEXT:   )
+;; CHECK-NEXT:  )
+;; CHECK-NEXT: )
-- 
cgit v1.2.3