diff options
Diffstat (limited to 'test')
| -rw-r--r-- | test/lit/passes/vacuum-global-effects.wast | 45 | ||||
| -rw-r--r-- | test/lit/passes/vacuum_all-features.wast | 23 |
2 files changed, 63 insertions, 5 deletions
diff --git a/test/lit/passes/vacuum-global-effects.wast b/test/lit/passes/vacuum-global-effects.wast new file mode 100644 index 000000000..1bd44ce17 --- /dev/null +++ b/test/lit/passes/vacuum-global-effects.wast @@ -0,0 +1,45 @@ +;; NOTE: Assertions have been generated by update_lit_checks.py and should not be edited. +;; RUN: wasm-opt %s --generate-global-effects --vacuum -all -S -o - | filecheck %s + +(module + ;; CHECK: (func $nop (type $i32_=>_none) (param $0 i32) + ;; CHECK-NEXT: (nop) + ;; CHECK-NEXT: ) + (func $nop (param $0 i32) + (nop) + ) + + ;; CHECK: (func $test (type $none_=>_none) + ;; CHECK-NEXT: (local $x i32) + ;; CHECK-NEXT: (nop) + ;; CHECK-NEXT: ) + (func $test + (local $x i32) + (local.set $x + (i32.const 0) + ) + ;; After we compute global effects, we see that this call has no effects. We + ;; can then remove it, and all of its contents have no effects as well. The + ;; rest of the function is also removable and the entire body can be a nop. + ;; + ;; This is a regression testcase for a crash in TypeUpdater, which involved + ;; the call being discovered as having no effects, and then when we started + ;; to remove its children we'd remove the br first; that removal would make + ;; the block seem to have no brs that reach it any more (since the only one + ;; was removed). But as the br was still in the tree, and had type + ;; unreachable, we thought the block should become unreachable, which then + ;; propagated out to the call and the toplevel block. (Users of TypeUpdater + ;; should first remove things from the tree, and then do the update.) + (call $nop + (block $block (result i32) + (br $block + (i32.const 4) + ) + ) + ) + (drop + (local.get $x) + ) + ) +) + diff --git a/test/lit/passes/vacuum_all-features.wast b/test/lit/passes/vacuum_all-features.wast index 36074af30..1a64521ed 100644 --- a/test/lit/passes/vacuum_all-features.wast +++ b/test/lit/passes/vacuum_all-features.wast @@ -627,7 +627,7 @@ ;; CHECK: (func $drop-if-both-unreachable (type $1) (param $0 i32) ;; CHECK-NEXT: (block $out ;; CHECK-NEXT: (drop - ;; CHECK-NEXT: (if (result i32) + ;; CHECK-NEXT: (if ;; CHECK-NEXT: (local.get $0) ;; CHECK-NEXT: (br $out) ;; CHECK-NEXT: (br $out) @@ -635,7 +635,7 @@ ;; CHECK-NEXT: ) ;; CHECK-NEXT: ) ;; CHECK-NEXT: (drop - ;; CHECK-NEXT: (if (result i32) + ;; CHECK-NEXT: (if ;; CHECK-NEXT: (local.get $0) ;; CHECK-NEXT: (unreachable) ;; CHECK-NEXT: (unreachable) @@ -701,6 +701,12 @@ ;; CHECK-NEXT: ) ;; CHECK-NEXT: (return) ;; CHECK-NEXT: ) + ;; CHECK-NEXT: (block $out2 + ;; CHECK-NEXT: (block $in2 + ;; CHECK-NEXT: (br $in2) + ;; CHECK-NEXT: ) + ;; CHECK-NEXT: (return) + ;; CHECK-NEXT: ) ;; CHECK-NEXT: ) (func $block-resize-br-gone (block $out @@ -711,6 +717,8 @@ ) (return) ) + ;; The second br will be removed. (The entire expression after us can also + ;; be removed, which will be done by --remove-unused-brs --vacuum.) (block $out2 (block $in2 (br $in2) @@ -758,14 +766,16 @@ ) ) ;; CHECK: (func $leave-block-even-if-br-not-taken (type $none_=>_f64) (result f64) - ;; CHECK-NEXT: (block $label$0 (result f64) + ;; CHECK-NEXT: (block $label$0 ;; CHECK-NEXT: (f64.store align=1 ;; CHECK-NEXT: (i32.const 879179022) - ;; CHECK-NEXT: (br_if $label$0 + ;; CHECK-NEXT: (block ;; CHECK-NEXT: (loop $label$9 ;; CHECK-NEXT: (br $label$9) ;; CHECK-NEXT: ) - ;; CHECK-NEXT: (i32.const 677803374) + ;; CHECK-NEXT: (drop + ;; CHECK-NEXT: (i32.const 677803374) + ;; CHECK-NEXT: ) ;; CHECK-NEXT: ) ;; CHECK-NEXT: ) ;; CHECK-NEXT: ) @@ -775,6 +785,9 @@ (f64.store align=1 (i32.const 879179022) (br_if $label$0 + ;; This loop never exits, so it is unreachable. We don't have much to + ;; optimize here, but we can remove the br_if and leave an unreachable + ;; block with the other contents for dce to clean up. (loop $label$9 (br $label$9) ) |