| /llvm-project-15.0.7/clang/test/Sema/ |
| H A D | attr-enforce-tcb.m | 13 …[self notInAnyTCB]; // expected-warning{{calling 'notInAnyTCB' is a violation of trusted computing… 25 …[self notInAnyTCB]; // expected-warning{{calling 'notInAnyTCB' is a violation of trusted comput… 33 …[object notInAnyTCB]; // expected-warning{{calling 'notInAnyTCB' is a violation of tru… 34 …tInAnyTCB]; // expected-warning{{calling 'classMethodNotInAnyTCB' is a violation of trusted compu… 36 …rtyNotInAnyTCB; // expected-warning{{calling 'propertyNotInAnyTCB' is a violation of trusted compu…
|
| H A D | attr-enforce-tcb-errors.m | 34 foo(); // expected-warning{{calling 'foo' is a violation of trusted computing base 'test'}} 69 foo(); // expected-warning{{calling 'foo' is a violation of trusted computing base 'x'}} 76 foo(); // expected-warning{{calling 'foo' is a violation of trusted computing base 'y'}} 82 foo(); // expected-warning{{calling 'foo' is a violation of trusted computing base 'x'}} 87 foo(); // expected-warning{{calling 'foo' is a violation of trusted computing base 'y'}}
|
| /llvm-project-15.0.7/compiler-rt/test/fuzzer/ |
| H A D | fork.test | 14 # access-violation is the error thrown on Windows. Address will be smaller on i386. 15 CRASH: {{SEGV|access-violation}} on unknown address 0x00000000
|
| H A D | fork_corpus_groups.test | 14 # access-violation is the error thrown on Windows. Address will be smaller on i386. 15 CRASH: {{SEGV|access-violation}} on unknown address 0x00000000
|
| H A D | fuzzer-segv.test | 8 LIBFUZZER_ASAN_SEGV_HANDLER: ERROR: AddressSanitizer: {{SEGV|access-violation}} on unknown address
|
| H A D | null-deref.test | 5 NullDerefTest: ERROR: AddressSanitizer: {{SEGV|access-violation}} on unknown address
|
| /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Darwin/ |
| H A D | objc-odr.mm | 22 // CHECK-NOT: AddressSanitizer: odr-violation
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | ReportingGuide.rst | 12 Conduct<CodeOfConduct>` violation, we encourage you to still report it. We 14 miss a report of an actual violation. There is no harm in reporting an incident 15 which is later determined not to be a violation, and knowing about incidents
|
| H A D | CodeOfConduct.rst | 28 amounts to an egregious violation of this code. 110 If the violation occurs at an event such as a Developer Meeting and requires
|
| H A D | ResponseGuide.rst | 40 but no commitment should be made on whether this is a violation or which action 43 For in-person events that have a violation reported, the report should be sent 185 violation.
|
| /llvm-project-15.0.7/llvm/test/Transforms/SimplifyCFG/ |
| H A D | 2009-01-18-PHIPropCrash.ll | 3 ; Dead use caused invariant violation.
|
| /llvm-project-15.0.7/llvm/test/TableGen/ |
| H A D | HwModeSelect.td | 7 // These two lists must have the same size. Make sure that a violation of
|
| /llvm-project-15.0.7/clang/docs/ |
| H A D | LTOVisibility.rst | 20 violation to define a class with hidden LTO visibility in multiple linkage 60 visibility in order to avoid an ODR violation. 115 an ODR violation.
|
| H A D | ControlFlowIntegrity.rst | 86 flow integrity violation. You can use the :ref:`-fno-sanitize-trap= 213 violation of the C and C++ standards, but it should not affect most programs.
|
| /llvm-project-15.0.7/llvm/test/CodeGen/X86/ |
| H A D | regcall-no-plt.ll | 11 ;; We encounter the violation symptom when using PIC with lazy binding
|
| /llvm-project-15.0.7/llvm/test/Linker/ |
| H A D | debug-info-bad-enum.ll | 14 ; CHECK-NOT: enum type is not a scope; check enum type ODR violation
|
| /llvm-project-15.0.7/lld/docs/ELF/ |
| H A D | warn_backrefs.rst | 68 unnecessarily large. Moreover, the layering violation makes lower-level 98 In C++, this is likely an ODR violation. We probably need a dedicated option
|
| /llvm-project-15.0.7/compiler-rt/lib/asan/ |
| H A D | asan_flags.inc | 151 "If >=2, detect violation of One-Definition-Rule (ODR); " 152 "If ==1, detect ODR-violation only if the two variables "
|
| /llvm-project-15.0.7/mlir/test/Dialect/Affine/ |
| H A D | inlining.mlir | 113 // Test that calls that would result in violation of affine value
|
| /llvm-project-15.0.7/clang/test/Analysis/ |
| H A D | nullability.mm | 212 // Since we've already had an invariant violation along this path, 224 // Since we've already had an invariant violation along this path, 243 // Since we've already had an invariant violation along this path,
|
| /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/ |
| H A D | array-odr-violation.ll | 1 ; This tests that emitting CodeView arrays doesn't assert when an ODR violation
|
| /llvm-project-15.0.7/third-party/benchmark/test/ |
| H A D | CMakeLists.txt | 169 # LTO is enabled and -Werror is specified GCC diagnoses this ODR violation
|
| /llvm-project-15.0.7/libcxx/lib/abi/ |
| H A D | CHANGELOG.TXT | 284 ODR violation. 482 I thought that if a debug violation aborted, we could only test one violation per file. This made
|
| /llvm-project-15.0.7/clang/lib/StaticAnalyzer/ |
| H A D | README.txt | 34 a node that satisfies some "bug condition" (basically a violation of a
|
| /llvm-project-15.0.7/clang/include/clang/AST/ |
| H A D | CXXRecordDeclDefinitionBits.def | 28 /// NO_MERGE: It is an ODR violation if the fields do not match.
|