T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Print constants in a comment in CLIF output (#4725)

Browse Source 
When trying to read generated CLIF, it's nice to be able to see at a
glance that some of the operands are defined by `iconst` and similar
instructions, without having to go find each operand's definition
manually.
This commit is contained in:
Jamey Sharp
2022-08-17 09:00:20 -07:00
committed by GitHub
parent 2696462ccb
commit 3629bbbd55
7 changed files with 110 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
cranelift/tests/bugpoint_consts_expected.clif
View File

@@ -21,6 +21,6 @@ block1:
v12 = vconst.b8x16 const2
v13 = vconst.i16x4 const1
v14 = vconst.f32x16 const0
call fn0(v0, v1, v2, v3, v4, v5, v6, v7, v8, v9, v10, v11, v12, v13, v14)
call fn0(v0, v1, v2, v3, v4, v5, v6, v7, v8, v9, v10, v11, v12, v13, v14) ; v0 = 0.0, v1 = 0.0, v2 = 0, v3 = 0, v4 = 0, v5 = 0, v6 = 0, v7 = false, v8 = false, v9 = false, v12 = const2, v13 = const1, v14 = const0
trap user0
}

2
cranelift/tests/bugpoint_test_expected.clif
View File

@@ -30,6 +30,6 @@ block0:
v990 -> v1052
v1051 -> v1052
v1055 -> v1052
call fn0(v0, v105, v1052, v883, v829, v987, v951, v842)
call fn0(v0, v105, v1052, v883, v829, v987, v951, v842) ; v0 = 0, v105 = 0, v1052 = 0, v883 = 0, v829 = 0, v987 = 0, v951 = 0, v842 = 0
trap user0
}