summaryrefslogtreecommitdiff
path: root/test/lit/help/wasm2js.test
diff options
context:
space:
mode:
authorAlon Zakai <azakai@google.com>2022-11-01 17:12:29 -0700
committerGitHub <noreply@github.com>2022-11-02 00:12:29 +0000
commit25e5aa67bd16f277ad32d42bfbbf7cd130ddf028 (patch)
tree6156f359bfc057a6e36b38ba7512d2ba317c98a3 /test/lit/help/wasm2js.test
parenta030cc7f69a00dc0e699b8b580224126650c738b (diff)
downloadbinaryen-25e5aa67bd16f277ad32d42bfbbf7cd130ddf028.tar.gz
binaryen-25e5aa67bd16f277ad32d42bfbbf7cd130ddf028.tar.bz2
binaryen-25e5aa67bd16f277ad32d42bfbbf7cd130ddf028.zip
ReorderGlobals pass (#4904)
This sorts globals by their usage (and respecting dependencies). If the module has very many globals then using smaller LEBs can matter. If there are fewer than 128 globals then we cannot reduce size, and the pass exits early (so this pass will not slow down MVP builds, which usually have just 1 global, the stack pointer). But with wasm GC it is common to use globals for vtables etc., and often there is a very large number of them.
Diffstat (limited to 'test/lit/help/wasm2js.test')
-rw-r--r--test/lit/help/wasm2js.test3
1 files changed, 3 insertions, 0 deletions
diff --git a/test/lit/help/wasm2js.test b/test/lit/help/wasm2js.test
index 0d61348b8..f190c8fed 100644
--- a/test/lit/help/wasm2js.test
+++ b/test/lit/help/wasm2js.test
@@ -314,6 +314,9 @@
;; CHECK-NEXT: --reorder-functions sorts functions by access
;; CHECK-NEXT: frequency
;; CHECK-NEXT:
+;; CHECK-NEXT: --reorder-globals sorts globals by access
+;; CHECK-NEXT: frequency
+;; CHECK-NEXT:
;; CHECK-NEXT: --reorder-locals sorts locals by access frequency
;; CHECK-NEXT:
;; CHECK-NEXT: --rereloop re-optimize control flow using