Lines Matching refs:test

13 each of these forms of test.
20 gets unwieldy to generate test data programmatically. File-level tests make it
24 hierarchy. Each file has a header describing what to test followed by a number
32     test_command  : "test" test_name { option } "\n"
34 The available test commands are described below.
36 Many test commands only make sense in the context of a target instruction set
37 architecture. These tests require one or more ISA specifications in the test
60     test legalizer
70 This example will run the legalizer test twice. Both runs will have
74 The filetests are run automatically as part of `cargo test`, and they can
75 also be run manually with the `clif-util test` command.
77 By default, the test runner will spawn a thread pool with as many threads as
80 limit the test runner to a single thread, use:
83 $ CRANELIFT_FILETESTS_THREADS=1 clif-util test path/to/file.clif
88 Many of the test commands described below use *filecheck* to verify their
95 entities) and scan them for filecheck directives. The test output for each
104 directives in the test file. LLVM's :command:`FileCheck` command has a
108 ### `test cat`
111 from textual IR. The `test cat` command simply parses each function and
132 ### `test verifier`
142     test verifier
144     function %test(i32) {
151 This example test passes if the verifier fails with an error message containing
155 If a function contains no `error:` annotations, the test passes if the
158 ### `test print-cfg`
166     test print-cfg
167     test verifier
188 ### `test domtree`
194     test domtree
196     function %test(i32) {
209 *immediate dominator* which is a jump or branch instruction. This test passes
213 This test also sends the computed CFG post-order through filecheck.
215 ### `test legalizer`
218 function through filecheck. This test command can be used to validate the
222 ### `test regalloc`
236 ### `test simple-gvn`
243 ### `test licm`
250 ### `test dce`
257 ### `test shrink`
264 ### `test simple_preopt`
271 ### `test compile`
276 which is normally used to compile code. This type of test often depends
281 ### `test run`
285 This test command allows several directives:
295  interpreted as a successful test execution, whereas a zero value is
296  interpreted as a failed test.
299 platform can run the test and currently only the architecture is filtered. The
300 host platform's native target will be used to actually compile the test.
305     test run