| /llvm-project-15.0.7/llvm/utils/unittest/googletest/src/ |
| H A D | gtest-printers.cc | 386 unsigned char lead = s[i++]; in IsValidUTF8() local
388 if (lead <= 0x7f) { in IsValidUTF8()
391 if (lead < 0xc2) { in IsValidUTF8()
393 } else if (lead <= 0xdf && (i + 1) <= length && IsUTF8TrailByte(s[i])) { in IsValidUTF8()
395 } else if (0xe0 <= lead && lead <= 0xef && (i + 2) <= length && in IsValidUTF8()
399 (lead != 0xe0 || s[i] >= 0xa0) && in IsValidUTF8()
400 (lead != 0xed || s[i] < 0xa0)) { in IsValidUTF8()
402 } else if (0xf0 <= lead && lead <= 0xf4 && (i + 3) <= length && in IsValidUTF8()
407 (lead != 0xf0 || s[i] >= 0x90) && in IsValidUTF8()
408 (lead != 0xf4 || s[i] < 0x90)) { in IsValidUTF8()
|
| /llvm-project-15.0.7/clang/test/SemaObjC/ |
| H A D | warn-retain-cycle.m | 12 …]; // expected-warning {{capturing 'x' strongly in this block is likely to lead to a retain cycle}}
14 …}; // expected-warning {{capturing 'x' strongly in this block is likely to lead to a retain cycle}}
17 …]; // expected-warning {{capturing 'x' strongly in this block is likely to lead to a retain cycle}}
31 … // expected-warning {{capturing 'x' strongly in this block is likely to lead to a retain cycle}}…
74 …// expected-warning {{capturing 'self' strongly in this block is likely to lead to a retain cycle}}
94 …// expected-warning {{capturing 'self' strongly in this block is likely to lead to a retain cycle}}
126 …// expected-warning {{capturing 'self' strongly in this block is likely to lead to a retain cycle}}
149 …b1(); // expected-warning{{capturing 'b1' strongly in this block is likely to lead to a retain cyc…
154 …b2(); // expected-warning{{capturing 'b2' strongly in this block is likely to lead to a retain cyc…
170 …[obj actNow]; // expected-warning{{capturing 'obj' strongly in this block is likely to lead to a r…
[all …]
|
| /llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/ |
| H A D | inline-asm-reserved-regs.ll | 4 …st may not be preserved across the asm statement, and clobbering them may lead to undefined behavi…
12 …st may not be preserved across the asm statement, and clobbering them may lead to undefined behavi…
20 …st may not be preserved across the asm statement, and clobbering them may lead to undefined behavi…
28 …st may not be preserved across the asm statement, and clobbering them may lead to undefined behavi…
36 …st may not be preserved across the asm statement, and clobbering them may lead to undefined behavi…
|
| H A D | fold-multiple.mir | 13 # after constant-folding the definition of %3 lead to the definition of %2
|
| /llvm-project-15.0.7/llvm/test/CodeGen/PowerPC/ |
| H A D | inline-asm-clobber-warning.ll | 13 …st may not be preserved across the asm statement, and clobbering them may lead to undefined behavi…
22 …st may not be preserved across the asm statement, and clobbering them may lead to undefined behavi…
|
| /llvm-project-15.0.7/lld/test/ELF/linkerscript/ |
| H A D | memory-nonalloc.test | 7 ## matching the section/region properties. Previously, that could lead to an
13 ## Previously, that also could lead to the same error.
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/objc/ |
| H A D | avoid-nserror-init.rst | 10 of ``[NSError alloc] init]``. Otherwise it will lead to a warning message
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines/ |
| H A D | interfaces-global-init.rst | 7 and therefore can lead to order-of-initialization problems.
|
| H A D | pro-bounds-pointer-arithmetic.rst | 6 This check flags all usage of pointer arithmetic, because it could lead to an
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/hicpp/ |
| H A D | signed-bitwise.rst | 6 Finds uses of bitwise operations on signed integer types, which may lead to
|
| /llvm-project-15.0.7/llvm/test/CodeGen/X86/ |
| H A D | codegen-prepare-collapse.ll | 15 ; lead to crashes.
|
| H A D | empty-function.ll | 8 ; Don't emit empty functions on Windows; it can lead to duplicate entries
|
| H A D | switch-order-weight.ll | 3 ; Check that the cases which lead to unreachable are checked after "10"
|
| H A D | lsr-overflow.ll | 4 ; The comparison uses the pre-inc value, which could lead LSR to
|
| /llvm-project-15.0.7/llvm/test/DebugInfo/Generic/ |
| H A D | lto-comp-dir.ll | 27 ; comp_dir is ambiguous and relying on it would lead to different path
28 ; interpretations depending on which CU lead to the table - so ensure that
|
| /llvm-project-15.0.7/clang/test/CodeGen/ |
| H A D | enable-split-lto-unit.ll | 3 ; Disable the verifier so the compiler doesn't abort and thus lead to empty
|
| /llvm-project-15.0.7/llvm/test/Transforms/InstSimplify/ConstProp/ |
| H A D | 2002-03-11-ConstPropCrash.ll | 3 ; can be bad, f.e. because constproping a terminator can lead to the
|
| /llvm-project-15.0.7/llvm/test/CodeGen/Hexagon/ |
| H A D | tail-dup-subreg-abort.ll | 6 ; This could lead to HexagonInstrInfo::copyPhysReg aborting on an unhandled
|
| /llvm-project-15.0.7/llvm/test/Other/ |
| H A D | loop-deletion-printer.ll | 2 ; does not lead to problems for -print-after-all and is just skipped.
|
| /llvm-project-15.0.7/clang/test/Headers/ |
| H A D | opencl-builtins.cl | 16 // example, addition of builtin declarations that lead to ambiguity during
|
| /llvm-project-15.0.7/llvm/test/Transforms/PGOProfile/ |
| H A D | memop_size_opt_zero.ll | 2 ; up a value profile with a 0 count, which would lead to divide by 0.
|
| /llvm-project-15.0.7/llvm/test/Instrumentation/AddressSanitizer/ |
| H A D | basic-msvc64.ll | 25 ; __asan_init before the shadow initialisation, which may lead to incorrect
|
| /llvm-project-15.0.7/llvm/test/Transforms/InstCombine/ |
| H A D | demand_shrink_nsw.ll | 4 ; The constant at %v35 should be shrunk, but this must lead to the nsw flag of
|
| /llvm-project-15.0.7/llvm/utils/lit/ |
| H A D | CMakeLists.txt | 13 # configure time (i.e. `file(COPY ...)`) because this could lead to stale
|
| /llvm-project-15.0.7/llvm/test/Transforms/JumpThreading/ |
| H A D | is_constant.ll | 6 ; intrinsic with non-local uses. It could lead to later passes no DCE'ing
|