| /llvm-project-15.0.7/openmp/runtime/test/affinity/format/ |
| H A D | check.py | 11 self.checks = []
29 self.checks.append(match.group(2))
33 if len(self.checks) == 0 and not self.check_no_output:
47 for c in self.checks:
70 checks = Checks(command_args.filename, command_args.prefix) variable
71 checks.readStdin()
72 checks.readChecks()
73 checks.check()
|
| /llvm-project-15.0.7/clang-tools-extra/docs/ |
| H A D | ReleaseNotes.rst | 144 New checks
167 <clang-tidy/checks/misc/const-correctness>` check.
172 <clang-tidy/checks/modernize/macro-to-enum>` check.
189 <clang-tidy/checks/modernize/macro-to-enum>` was added.
191 Changes in existing checks
198 <clang-tidy/checks/bugprone/branch-clone>` when the branches
209 <clang-tidy/checks/bugprone/use-after-move>`:
218 <clang-tidy/checks/cert/dcl58-cpp>` check.
246 <clang-tidy/checks/misc/redundant-expression>`:
254 <clang-tidy/checks/misc/unused-parameters>`
[all …]
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/ |
| H A D | index.rst | 12 The list of clang-tidy checks <checks/list>
20 interface for writing new checks.
36 checks. Each check has a name and the checks to run can be chosen using the
48 The ``-list-checks`` option lists all the enabled checks. When used without
49 ``-checks=``, it shows checks enabled by default. Use ``-checks=*`` to see all
50 available checks or with any other value of ``-checks=`` to see which checks are
93 the ``-checks=`` option. However, the ``-checks=`` option does not affect
106 supported by corresponding checks.
125 --checks=<string> -
217 --list-checks -
[all …]
|
| H A D | Integrations.rst | 20 … | On-the-fly inspection | Check list configuration (GUI) | Options to checks (GUI) | Configura…
52 .. _integrates clang-tidy: https://www.jetbrains.com/help/clion/clang-tidy-checks-support.html
57 performed on the fly, and checks can be configured in standard command line
61 options for particular checks.
78 choose the checks to be performed. Since QtCreator 4.7 project-wide analysis is
90 integration: checks and quick-fixes run alongside native inspections. Apart
96 :program:`clang-tidy` checks and runs them during compilation or as a separate
|
| H A D | Contributing.rst | 6 checks, but its power is in the ability to easily write custom checks.
34 ``clang-analyzer-*`` checks or the ``mpi-*`` checks.
56 + *clang-tidy check* is a good choice for linter-style checks, checks that are
163 ``docs/clang-tidy/checks/list.rst``.
285 Most checks will interact with C++ source code via the AST. Some checks will interact
578 It's advised to make the checks as specific as possible to avoid checks matching
655 names of the checks to enable.
659 $ clang-tidy --checks=-*,my-explicit-constructor -list-checks -load myplugin.so
684 * The default set of checks can be overridden using the ``-checks`` argument,
701 On checks profiling
[all …]
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | FaultMaps.rst | 2 FaultMaps and implicit checks
12 Code generated by managed language runtimes tend to have checks that
16 exploited by folding such safety checks into operations that can be
20 For example, Java requires null checks on objects before they are read
31 Information about implicit checks generated by LLVM are put in a
101 ``-enable-implicit-null-checks`` is passed to ``llc``.
109 Making null checks implicit is an aggressive optimization, and it can
112 ensure that only a negligible number of implicit null checks actually
114 of doing this is by healing failed implicit null checks into explicit
115 null checks via code patching or recompilation. It follows that there
[all …]
|
| /llvm-project-15.0.7/llvm/test/Transforms/GlobalDCE/ |
| H A D | comdats.ll | 5 ; First test checks that if one function in a comdat group is used, both other
10 ; Second test checks that if one function in a comdat group is used, both other
15 ; Third test checks that calling a function in a comdat group with an alias
20 ; Fourth test checks that calling an alias in a comdat group with a function
26 ; Fifth test checks that calling a function in a comdat group that is used as
33 ; Sixth test checks that calling an ifunc whose resolver is in a comdat group
39 ; Seventh test checks that we can eliminate a comdat when it has only one dead function participant.
43 ; Eighth test checks that we can eliminate a comdat when it has only one dead global participant.
47 ; Ninth test checks that we can eliminate a comdat when there are multiple
52 ; Tenth test checks that we can eliminate a comdat when it has multiple
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/ |
| H A D | gen-static-analyzer-docs.py | 91 checks = check_text.split("\n")
93 if((" %s" % checker["FullPackageName"]) not in checks):
94 checks.append(" %s" % checker["FullPackageName"])
95 checks.sort()
101 for check in checks:
|
| /llvm-project-15.0.7/libcxx/docs/DesignDocs/ |
| H A D | DebugMode.rst | 13 Libc++ provides a debug mode that enables special debugging checks meant to detect
14 incorrect usage of the standard library. These checks are disabled by default, but
28 The debug mode provides various checks to aid application debugging.
30 Comparator consistency checks
32 Libc++ provides some checks for the consistency of comparators passed to algorithms. Specifically,
38 Iterator debugging checks
|
| /llvm-project-15.0.7/clang/docs/ |
| H A D | UndefinedBehaviorSanitizer.rst | 22 See the full list of available :ref:`checks <ubsan-checks>` below.
52 You can enable only a subset of :ref:`checks <ubsan-checks>` offered by UBSan,
74 .. _ubsan-checks:
76 Available checks
79 Available checks are:
142 invalid pointers. These checks are made in terms of
163 This includes all the checks covered by ``-ftrapv``, as well as checks for
188 of checks.
266 You disable UBSan checks for particular functions with
311 most of UBSan checks are recoverable by default.
[all …]
|
| H A D | ControlFlowIntegrity.rst | 28 To allow the checks to be implemented efficiently, the program must
33 The compiler will only produce CFI checks for a class if it can infer hidden
41 CFI checks for classes without visibility attributes. Most users will want
57 - ``-fsanitize=cfi-cast-strict``: Enables :ref:`strict cast checks
129 This scheme checks that pointer casts are made to an object of the correct
131 of the pointee type of the cast. The checks are currently only introduced
165 This scheme checks that non-virtual calls take place using an object of
168 call. The checks are currently only introduced where the object is of a
312 This scheme checks that indirect calls via a member function pointer
356 # Disable only unrelated cast checks for this function
[all …]
|
| /llvm-project-15.0.7/llvm/test/Transforms/LoopVectorize/ |
| H A D | interleaved-accesses-2.ll | 10 ; the wrapping checks are necessary. Here this cannot be done statically so
11 ; runtime checks are needed, but with Assume=false getPtrStride cannot add
12 ; runtime checks and as a result we can't create the interleave-group.
15 ; with proper threshold checks. Once we do that the candidate interleave-group
16 ; will not be invalidated by the wrapping checks.
|
| /llvm-project-15.0.7/mlir/utils/clang-tidy/ |
| H A D | apply-clang-tidy.sh | 55 tmpfile=$(mktemp /tmp/mhlo-temp-checks.XXXXXX)
65 CHECKS=$($CLANG_TIDY $file -p $BUILD_DIR --list-checks \
93 { $TIMING_TIDY $CLANG_TIDY -p $BUILD_DIR $file --checks="-*,$check" -fix ; } 2>&1
|
| /llvm-project-15.0.7/llvm/test/Transforms/IRCE/ |
| H A D | only-lower-check.ll | 1 ; RUN: opt -irce-print-range-checks -irce-print-changed-loops -verify-loop-info -irce < %s 2>&1 | F…
2 ; RUN: opt -irce-print-range-checks -irce-print-changed-loops -verify-loop-info -passes='require<br…
4 ; CHECK: irce: loop has 1 inductive range checks:
|
| H A D | only-upper-check.ll | 1 ; RUN: opt -verify-loop-info -irce -irce-print-range-checks -irce-print-changed-loops %s -S 2>&1 | …
2 ; RUN: opt -verify-loop-info -passes='require<branch-prob>,irce' -irce-print-range-checks -irce-pri…
4 ; CHECK: irce: loop has 1 inductive range checks:
|
| /llvm-project-15.0.7/llvm/test/CodeGen/ARM/ |
| H A D | a15-mla.ll | 4 ; This test checks that the VMLxForwarting feature is disabled for A15.
15 ; This tests checks that VMLA FP patterns can be matched in instruction selection when targeting
25 ; This tests checks that FP VMLA instructions are not expanded into separate multiply/addition
|
| H A D | cfguard-checks.ll | 4 ; Test that Control Flow Guard checks are correctly added when required.
10 ; Test that Control Flow Guard checks are not added on calls with the "guard_nocf" attribute.
29 ; Test that Control Flow Guard checks are added even at -O0.
54 ; Test that Control Flow Guard checks are correctly added in optimized code (common case).
76 ; Test that Control Flow Guard checks are correctly added on invoke instructions.
|
| /llvm-project-15.0.7/clang-tools-extra/clangd/test/ |
| H A D | diagnostics-tidy.test | 1 # REQUIRES: clangd-tidy-checks
2 # RUN: clangd -lit-test -clang-tidy-checks=bugprone-sizeof-expression < %s | FileCheck -strict-whit…
12 # CHECK-NEXT: "href": "https://clang.llvm.org/extra/clang-tidy/checks/bugprone/sizeof-expr…
|
| /llvm-project-15.0.7/cmake/Modules/ |
| H A D | EnableLanguageNolink.cmake | 3 # in the compiler sanity checks. When bootstrapping the toolchain,
4 # the toolchain itself is still incomplete and sanity checks that include
|
| /llvm-project-15.0.7/llvm/test/CodeGen/AArch64/ |
| H A D | cfguard-checks.ll | 4 ; Test that Control Flow Guard checks are correctly added when required.
10 ; Test that Control Flow Guard checks are not added on calls with the "guard_nocf" attribute.
28 ; Test that Control Flow Guard checks are added even at -O0.
51 ; Test that Control Flow Guard checks are correctly added in optimized code (common case).
72 ; Test that Control Flow Guard checks are correctly added on invoke instructions.
|
| H A D | cfguard-module-flag.ll | 5 ; Test that Control Flow Guard checks are not added in modules with the
6 ; cfguard=1 flag (emit tables but no checks).
|
| /llvm-project-15.0.7/llvm/test/Verifier/ |
| H A D | non-integer-gep-index.ll | 3 ; Test that verifier checks that gep indexes has correct type
7 ; IR parser checks for this pattern independently from the verifier, so it's
|
| /llvm-project-15.0.7/llvm/test/CodeGen/X86/ |
| H A D | pseudo_cmov_lower-fp16.ll | 3 ; This test checks that only a single je gets generated in the final code
17 ; This test checks that only a single ja gets generated in the final code
62 ; This test checks that only a single jne gets generated in the final code
73 ; This test checks that only a single jne gets generated in the final code
84 ; This test checks that only a single jne gets generated in the final code
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/readability/ |
| H A D | identifier-naming.rst | 322 Identifier naming checks won't be enforced for class member names
420 Identifier naming checks won't be enforced for constant names
826 Identifier naming checks won't be enforced for function names
1386 Identifier naming checks won't be enforced for member names
1436 Identifier naming checks won't be enforced for method names
1480 Identifier naming checks won't be enforced for namespace names
1524 Identifier naming checks won't be enforced for parameter names
2092 Identifier naming checks won't be enforced for struct names
2260 Identifier naming checks won't be enforced for typedef names
2342 Identifier naming checks won't be enforced for union names
[all …]
|
| /llvm-project-15.0.7/clang-tools-extra/test/clang-tidy/checkers/google/ |
| H A D | runtime-int.m | 1 // RUN: clang-tidy -checks=-*,google-runtime-int %s 2>&1 -- | count 0
2 // RUN: clang-tidy -checks=-*,google-runtime-int %s 2>&1 -- -x objective-c++ | count 0
|