Cranelift: Print and parse cold flag for blocks #3701
Comments
cfallin
added a commit
to cfallin/wasmtime
that referenced
this issue
Jan 20, 2022
This commit adds support for denoting cold blocks in the CLIF text
format as follows:
```plain
function %f() {
block0(...):
...
cold block1:
...
cold block2(...):
...
block3:
...
```
With this syntax, we are able to see the cold-block flag in CLIF, we can
write tests using it, and it is preserved when round-tripping.
Fixes bytecodealliance#3701.
cfallin
added a commit
to cfallin/wasmtime
that referenced
this issue
Jan 21, 2022
This commit adds support for denoting cold blocks in the CLIF text
format as follows:
```plain
function %f() {
block0(...):
...
cold block1:
...
cold block2(...):
...
block3:
...
```
With this syntax, we are able to see the cold-block flag in CLIF, we can
write tests using it, and it is preserved when round-tripping.
Fixes bytecodealliance#3701.
cfallin
added a commit
to cfallin/wasmtime
that referenced
this issue
Jan 21, 2022
This commit adds support for denoting cold blocks in the CLIF text
format as follows:
```plain
function %f() {
block0(...):
...
block1 cold:
...
block2(...) cold:
...
block3:
...
```
With this syntax, we are able to see the cold-block flag in CLIF, we can
write tests using it, and it is preserved when round-tripping.
Fixes bytecodealliance#3701.
alexcrichton
pushed a commit
to alexcrichton/wasmtime
that referenced
this issue
Feb 2, 2022
This commit adds support for denoting cold blocks in the CLIF text
format as follows:
```plain
function %f() {
block0(...):
...
block1 cold:
...
block2(...) cold:
...
block3:
...
```
With this syntax, we are able to see the cold-block flag in CLIF, we can
write tests using it, and it is preserved when round-tripping.
Fixes bytecodealliance#3701.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This flag was introduced in #3698, but round tripping between the in memory ir and textual ir format currently loses the flag.
The text was updated successfully, but these errors were encountered: