Lines Matching +full:docs +full:- +full:clang +full:- +full:tools +full:- +full:html

26 // CHECK-LABEL: test_add:
40 [LLVM's Filecheck](https://llvm.org/docs/CommandGuide/FileCheck.html)
50 bits of assembly. ([`CHECK-NEXT`](https://llvm.org/docs/CommandGuide/FileCheck.html#the-check-next-…
53 * The tests are compiled with `-O3 -g0`. So we're only testing the
56 * The assembly output is further cleaned up using `tools/strip_asm.py`.
61 `<build-directory>/test/<test-name>.s`
63 … supports using [`CHECK` prefixes](https://llvm.org/docs/CommandGuide/FileCheck.html#cmdoption-che…
65 The Benchmark tests use `CHECK-CLANG` and `CHECK-GNU` for lines that
66 are only expected to match Clang or GCC's output respectively. Normal
67 `CHECK` lines match against all compilers. (Note: `CHECK-NOT` and
68 `CHECK-LABEL` are NOT prefixes. They are versions of non-prefixed
78 inherently non-portable. Different compilers and even different compiler
83 …g using regular expressions](https://llvm.org/docs/CommandGuide/FileCheck.html#filecheck-pattern-m…
84 …ing the creation of [named variables](https://llvm.org/docs/CommandGuide/FileCheck.html#filecheck-…
85 … later matching, and [checking non-sequential matches](https://llvm.org/docs/CommandGuide/FileChec…
89 For example, say GCC stores a variable in a register but Clang stores
95 // CHECK-LABEL: test_div_no_op_into_shr:
114 <!-- {% raw %} -->
119 // CHECK-LABEL: test_store_point:
125     // CHECK: movl %eax, -{{[0-9]+}}(%rsp)
126     // CHECK: movl %eax, -{{[0-9]+}}(%rsp)
127     // CHECK: movl %eax, -{{[0-9]+}}(%rsp)
131 <!-- {% endraw %} -->
139 inherently non-portable. Currently the tests are limited to:
142 * Compiled with GCC or Clang
148 that modify code generation, including `--coverage` or `-fsanitize=`.