summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorAlon Zakai <azakai@google.com>2024-10-17 14:27:55 -0700
committerGitHub <noreply@github.com>2024-10-17 14:27:55 -0700
commit245d9156d8bd52ce9bc50c554aa3a9cd42cd0e6b (patch)
treea10719f035a6e6e5800df968eae5bfdcf11de2af /test
parent6566329fecd36c8cd8e2ab29f89dafde0d2e9304 (diff)
downloadbinaryen-245d9156d8bd52ce9bc50c554aa3a9cd42cd0e6b.tar.gz
binaryen-245d9156d8bd52ce9bc50c554aa3a9cd42cd0e6b.tar.bz2
binaryen-245d9156d8bd52ce9bc50c554aa3a9cd42cd0e6b.zip
[GC] Ignore public types in GlobalTypeOptimization (#7017)
TypeUpdater which it uses internally already does so, but we must also ignore such types earlier, and make no other modifications to them. Helps #7015
Diffstat (limited to 'test')
-rw-r--r--test/lit/passes/gto-removals.wast90
1 files changed, 90 insertions, 0 deletions
diff --git a/test/lit/passes/gto-removals.wast b/test/lit/passes/gto-removals.wast
index c2ac66a57..61396cf8f 100644
--- a/test/lit/passes/gto-removals.wast
+++ b/test/lit/passes/gto-removals.wast
@@ -1405,3 +1405,93 @@
)
)
)
+
+;; Public types cannot be optimized. The function type here is public as the
+;; function is exported, and so the entire rec group is public, and cannot be
+;; modified. We cannot even optimize $child3 which is outside of the rec group,
+;; because its parent is inside. However, we can optimize $unrelated which is
+;; unrelated to them (and so we can remove the field there).
+(module
+ (rec
+ ;; CHECK: (rec
+ ;; CHECK-NEXT: (type $parent (sub (struct (field (ref func)))))
+ (type $parent (sub (struct (field (ref func)))))
+ ;; CHECK: (type $child1 (sub $parent (struct (field (ref func)))))
+ (type $child1 (sub $parent (struct (field (ref func)))))
+ ;; CHECK: (type $child2 (sub $parent (struct (field (ref func)))))
+ (type $child2 (sub $parent (struct (field (ref func)))))
+
+ ;; CHECK: (type $func (func (param (ref $child2))))
+ (type $func (func (param $child2 (ref $child2))))
+ )
+
+ ;; CHECK: (rec
+ ;; CHECK-NEXT: (type $unrelated (sub (struct)))
+
+ ;; CHECK: (type $child3 (sub $parent (struct (field (ref func)))))
+ (type $child3 (sub $parent (struct (field (ref func)))))
+
+ (type $unrelated (sub (struct (field (ref func)))))
+
+ ;; CHECK: (elem declare func $func)
+
+ ;; CHECK: (export "func" (func $func))
+
+ ;; CHECK: (func $func (type $func) (param $child2 (ref $child2))
+ ;; CHECK-NEXT: (drop
+ ;; CHECK-NEXT: (struct.new $parent
+ ;; CHECK-NEXT: (ref.func $func)
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: (drop
+ ;; CHECK-NEXT: (struct.new $child1
+ ;; CHECK-NEXT: (ref.func $func)
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: (drop
+ ;; CHECK-NEXT: (struct.new $child2
+ ;; CHECK-NEXT: (ref.func $func)
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: (drop
+ ;; CHECK-NEXT: (struct.new $child3
+ ;; CHECK-NEXT: (ref.func $func)
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: (drop
+ ;; CHECK-NEXT: (struct.new_default $unrelated)
+ ;; CHECK-NEXT: )
+ ;; CHECK-NEXT: )
+ (func $func (export "func") (type $func) (param $child2 (ref $child2))
+ ;; Create all the types. Note that the value here is non-nullable, as is the
+ ;; field, so if we remove the field by mistake in GTO but leave it during
+ ;; TypeUpdater, we'd error (on providing a default value for a non-nullable
+ ;; field).
+ (drop
+ (struct.new $parent
+ (ref.func $func)
+ )
+ )
+ (drop
+ (struct.new $child1
+ (ref.func $func)
+ )
+ )
+ (drop
+ (struct.new $child2
+ (ref.func $func)
+ )
+ )
+ (drop
+ (struct.new $child3
+ (ref.func $func)
+ )
+ )
+ ;; We can optimize this one, and no other.
+ (drop
+ (struct.new $unrelated
+ (ref.func $func)
+ )
+ )
+ )
+)