| /llvm-project-15.0.7/clang/test/PCH/ |
| H A D | chain-friend-instantiation.cpp | 10 template <class X, class Y> TClass<X> problematic(X * ptr, const TClass<Y> &src);
16 template <class X, class Y> friend TClass<X> problematic(X * ptr, const TClass<Y> &src);
30 TClass<X> problematic(X *ptr, const TClass<T> &src);
|
| /llvm-project-15.0.7/llvm/test/CodeGen/AArch64/ |
| H A D | machine-outliner-bad-register.mir | 10 ; No problematic register appears at all. Safe for outlining.
13 ; A problematic register is live, but after the candidate. Safe for outlining.
16 ; A problematic register is live before the candidate, but killed before
20 ; Ensure that we never outline when any of the problematic registers we care
|
| H A D | trunc-v1i64.ll | 65 ; PR20777: v1i1 is also problematic, but we can't widen it, so we extract_elt
|
| /llvm-project-15.0.7/clang-tools-extra/test/clang-tidy/checkers/cppcoreguidelines/ |
| H A D | owning-memory.cpp | 306 HeapArray(int size, T val, int *problematic) : _data{problematic}, size(size) {} // Bad in HeapArray()
|
| /llvm-project-15.0.7/llvm/cmake/modules/ |
| H A D | CheckProblematicConfigurations.cmake | 2 option(LLVM_ALLOW_PROBLEMATIC_CONFIGURATIONS OFF "Set this option to ON to allow problematic toolch…
|
| /llvm-project-15.0.7/llvm/test/Feature/OperandBundles/ |
| H A D | pr26510.ll | 5 ; if any problematic aliasing rules have accidentally snuck into -O3.
|
| /llvm-project-15.0.7/llvm/test/MC/X86/ |
| H A D | align-branch-negative.s | 3 # This file includes cases which are problematic to apply automatic padding
|
| /llvm-project-15.0.7/clang-tools-extra/test/clang-tidy/checkers/hicpp/ |
| H A D | exception-baseclass.cpp | 21 void problematic() { in problematic() function
|
| /llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines/ |
| H A D | macro-usage.rst | 6 Finds macro usage that is considered problematic because better language
|
| H A D | narrowing-conversions.rst | 65 problematic assignments such as `int n = std::vector<char>().size();` or
|
| /llvm-project-15.0.7/llvm/test/FileCheck/match-time-error-propagation/ |
| H A D | matched-expected-pattern.txt | 1 ; Check handling of diagnostics for problematic matches (e.g., variable capture
|
| H A D | matched-excluded-pattern.txt | 1 ; Check handling of diagnostics for problematic matches (e.g., variable capture
|
| /llvm-project-15.0.7/llvm/test/CodeGen/ARM/ |
| H A D | virtregrewriter-subregliveness.mir | 30 ; the problematic code anymore.
|
| /llvm-project-15.0.7/llvm/docs/HistoricalNotes/ |
| H A D | 2001-02-06-TypeNotationDebate.txt | 42 around for 27 years and perhaps more; why do you consider it problematic
|
| /llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/ |
| H A D | scalar-branch-missing-and-exec.ll | 10 ; The problematic case is s_xor_b64, as, unlike the other ops, it can actually
|
| /llvm-project-15.0.7/llvm/test/Transforms/LoopVectorize/ |
| H A D | pr31190.ll | 7 ; In this case, the problematic PHI is:
|
| /llvm-project-15.0.7/libcxx/docs/DesignDocs/ |
| H A D | VisibilityMacros.rst | 148 Consequently, all such problematic method templates are explicitly marked
150 libraries. The problematic methods were found by running
|
| /llvm-project-15.0.7/llvm/test/Transforms/PhaseOrdering/ |
| H A D | simplifycfg-switch-lowering-vs-correlatedpropagation.ll | 8 ; we may make further optimizations problematic.
|
| /llvm-project-15.0.7/llvm/test/Transforms/NewGVN/ |
| H A D | fence-xfail.ll | 76 ; Another example of why forwarding across an acquire fence is problematic
|
| /llvm-project-15.0.7/llvm/test/Transforms/GVN/ |
| H A D | fence.ll | 75 ; Another example of why forwarding across an acquire fence is problematic
|
| /llvm-project-15.0.7/llvm/test/Transforms/LoopVectorize/X86/ |
| H A D | consecutive-ptr-cg-bug.ll | 23 ; solution is to detect the problematic IVs in LV (%7 and %8) and perform an
|
| /llvm-project-15.0.7/llvm/test/CodeGen/Thumb2/ |
| H A D | thumb2-pack.ll | 93 ; use it for problematic cases when whether sign bits would be shifted in
|
| /llvm-project-15.0.7/clang/docs/ |
| H A D | ThreadSanitizer.rst | 29 Support for 32-bit platforms is problematic and is not planned.
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | ReportingGuide.rst | 8 problematic behavior. If we don't know, we can't learn or take any appropriate
|
| /llvm-project-15.0.7/llvm/test/Transforms/IndVarSimplify/ |
| H A D | lftr-dead-ivs.ll | 227 ; For integer IVs, we handle this trigger case by stripping the problematic
|