[WebAssembly] Enable register coloring and register stackifying.
This also takes the push/pop syntax another step forward, introducing stack
slot numbers to make it easier to see how expressions are connected. For
example, the value pushed in $push7 is popped in $pop7.
And, this begins an experiment with making get_local and set_local implicit
when an operation directly uses or defines a register. This greatly reduces
clutter. If this experiment succeeds, it may make sense to do this for
const instructions as well.
And, this introduces more special code for ARGUMENTS; hopefully this code
will soon be obviated by proper support for live-in virtual registers.
llvm-svn: 253465
diff --git a/llvm/test/CodeGen/WebAssembly/memory-addr64.ll b/llvm/test/CodeGen/WebAssembly/memory-addr64.ll
index 6b9ac04..3def042 100644
--- a/llvm/test/CodeGen/WebAssembly/memory-addr64.ll
+++ b/llvm/test/CodeGen/WebAssembly/memory-addr64.ll
@@ -11,9 +11,8 @@
; CHECK-LABEL: memory_size:
; CHECK-NEXT: .result i64{{$}}
; CHECK-NEXT: .local i64{{$}}
-; CHECK-NEXT: memory_size
-; CHECK-NEXT: set_local 0, $pop{{$}}
-; CHECK-NEXT: return (get_local 0){{$}}
+; CHECK-NEXT: memory_size $0{{$}}
+; CHECK-NEXT: return $0{{$}}
define i64 @memory_size() {
%a = call i64 @llvm.wasm.memory.size.i64()
ret i64 %a
@@ -21,9 +20,8 @@
; CHECK-LABEL: grow_memory:
; CHECK-NEXT: .param i64
-; CHECK-NEXT: .local i64{{$}}
-; CHECK: grow_memory (get_local 0)
-; CHECK-NEXT: return
+; CHECK: grow_memory $0{{$}}
+; CHECK-NEXT: return{{$}}
define void @grow_memory(i64 %n) {
call void @llvm.wasm.grow.memory.i64(i64 %n)
ret void