b13bca7387
There are cases we end up removing some intructions that use stackified registers after RegStackify. For example, ```wasm bb.0: %0 = ... ;; %0 is stackified br_if %bb.1, %0 bb.1: ``` In this code, br_if will be removed in CFGSort, so we should unstackify %0 so that it can be correctly dropped in ExplicitLocals. Rather than handling this in case-by-case basis, this PR just unstackifies all stackifies register with no uses in the beginning of ExplicitLocals, so that they can be correctly dropped. Fixes #149097.
27 lines
822 B
LLVM
27 lines
822 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py UTC_ARGS: --version 5
|
|
; RUN: llc -O0 -verify-machineinstrs < %s | FileCheck %s
|
|
|
|
target triple = "wasm32-unknown-unknown"
|
|
|
|
define void @test(i1 %x) {
|
|
; CHECK-LABEL: test:
|
|
; CHECK: .functype test (i32) -> ()
|
|
; CHECK-NEXT: # %bb.0:
|
|
; CHECK-NEXT: local.get 0
|
|
; CHECK-NEXT: i32.const -1
|
|
; CHECK-NEXT: i32.xor
|
|
; CHECK-NEXT: i32.const 1
|
|
; CHECK-NEXT: i32.and
|
|
; CHECK-NEXT: drop
|
|
; CHECK-NEXT: # %bb.1: # %exit
|
|
; CHECK-NEXT: return
|
|
%y = xor i1 %x, true
|
|
; This br_if's operand (%y) is stackified in RegStackify. But this terminator
|
|
; will be removed in CFGSort after that. We need to make sure we unstackify %y
|
|
; so that it can be dropped in ExplicitLocals.
|
|
br i1 %y, label %exit, label %exit
|
|
|
|
exit:
|
|
ret void
|
|
}
|