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

Remove references to the old postopt pass

Browse Source
This commit is contained in:
Nick Fitzgerald
2021-10-07 14:43:36 -07:00
parent a986cf2438
commit dbe01ff51e
2 changed files with 8 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
cranelift/codegen/src/timing.rs
View File

@@ -55,7 +55,6 @@ define_passes! {
flowgraph: "Control flow graph", flowgraph: "Control flow graph",
domtree: "Dominator tree", domtree: "Dominator tree",
loop_analysis: "Loop analysis", loop_analysis: "Loop analysis",
postopt: "Post-legalization rewriting",
preopt: "Pre-legalization rewriting", preopt: "Pre-legalization rewriting",
dce: "Dead code elimination", dce: "Dead code elimination",
legalize: "Legalization", legalize: "Legalization",

23
cranelift/docs/testing.md
View File

@@ -299,13 +299,6 @@ Test the preopt pass.
The preopt pass is run on each function, and then results are run The preopt pass is run on each function, and then results are run
through filecheck. through filecheck.
### `test postopt`
Test the postopt pass.
The postopt pass is run on each function, and then results are run
through filecheck.
### `test compile` ### `test compile`
Test the whole code generation pipeline. Test the whole code generation pipeline.
@@ -321,16 +314,16 @@ Cranelift IR right before binary machine code emission.
Compile and execute a function. Compile and execute a function.
This test command allows several directives: This test command allows several directives:
- to print the result of running a function to stdout, add a `print` - to print the result of running a function to stdout, add a `print`
directive and call the preceding function with arguments (see `%foo` in directive and call the preceding function with arguments (see `%foo` in
the example below); remember to enable `--nocapture` if running these the example below); remember to enable `--nocapture` if running these
tests through Cargo tests through Cargo
- to check the result of a function, add a `run` directive and call the - to check the result of a function, add a `run` directive and call the
preceding function with a comparison (`==` or `!=`) (see `%bar` below) preceding function with a comparison (`==` or `!=`) (see `%bar` below)
- for backwards compatibility, to check the result of a function with a - for backwards compatibility, to check the result of a function with a
`() -> b*` signature, only the `run` directive is required, with no `() -> b*` signature, only the `run` directive is required, with no
invocation or comparison (see `%baz` below); a `true` value is invocation or comparison (see `%baz` below); a `true` value is
interpreted as a successful test execution, whereas a `false` value is interpreted as a successful test execution, whereas a `false` value is
interpreted as a failed test. interpreted as a failed test.
Currently a `target` is required but is only used to indicate whether the host Currently a `target` is required but is only used to indicate whether the host
@@ -417,19 +410,19 @@ See the diagram below, on how the `vmctx` struct ends up if with multiple heaps:
``` ```
┌─────────────────────┐ vmctx+0 ┌─────────────────────┐ vmctx+0
│heap0: start address │ │heap0: start address │
├─────────────────────┤ vmctx+8 ├─────────────────────┤ vmctx+8
│heap0: end address │ │heap0: end address │
├─────────────────────┤ vmctx+16 ├─────────────────────┤ vmctx+16
│heap1: start address │ │heap1: start address │
├─────────────────────┤ vmctx+24 ├─────────────────────┤ vmctx+24
│heap1: end address │ │heap1: end address │
├─────────────────────┤ vmctx+32 ├─────────────────────┤ vmctx+32
│etc... │ │etc... │
└─────────────────────┘ └─────────────────────┘
``` ```
With this setup, you can now use the global values to load heaps, and load / store to them. With this setup, you can now use the global values to load heaps, and load / store to them.
Example: Example: