Searched refs:problematic (Results 1 – 25 of 202) sorted by relevance
123456789
/external/llvm-project/clang/test/PCH/ |
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);
|
/external/clang/test/PCH/ |
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);
|
/external/llvm-project/llvm/test/CodeGen/AArch64/ |
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
|
/external/iptables/extensions/ |
D | Android.bp | 47 // Exclude some modules that are problematic to compile (types/headers) 64 // Exclude some modules that are problematic to compile (types/headers)
|
/external/ltp/testcases/realtime/func/measurement/ |
D | README | 3 problematic.
|
/external/llvm-project/clang-tools-extra/test/clang-tidy/checkers/ |
D | cppcoreguidelines-owning-memory.cpp | 313 HeapArray(int size, T val, int *problematic) : _data{problematic}, size(size) {} // Bad in HeapArray()
|
D | hicpp-exception-baseclass.cpp | 21 void problematic() { in problematic() function
|
/external/skqp/site/dev/chrome/ |
D | repo.md | 16 Chromium doesn't need any of them, and it can be confusing and problematic if
|
/external/skia/site/docs/dev/chrome/ |
D | repo.md | 21 Chromium doesn't need any of them, and it can be confusing and problematic if
|
/external/llvm/test/Feature/OperandBundles/ |
D | pr26510.ll | 5 ; if any problematic aliasing rules have accidentally snuck into -O3.
|
/external/llvm-project/llvm/test/Feature/OperandBundles/ |
D | pr26510.ll | 5 ; if any problematic aliasing rules have accidentally snuck into -O3.
|
/external/toolchain-utils/afdo_tools/bisection/ |
D | README.md | 6 good and bad profiles to isolate the problematic portion of the bad profile. 15 problematic in conjunction with one another.
|
/external/tensorflow/third_party/ |
D | eigen.BUILD | 42 # This define (mostly) guarantees we don't link any problematic
|
/external/python/oauth2client/docs/ |
D | index.rst | 33 - Using ``pycrypto`` with ``pypy`` will be in general problematic. If 47 problematic since ``pyOpenSSL`` depends on the ``cryptography`` library.
|
/external/llvm/test/Transforms/FunctionAttrs/ |
D | out-of-bounds-iterator-bug.ll | 7 ; we _need_ the readonly on @va_func to trigger the problematic code path). It
|
/external/llvm-project/llvm/test/Transforms/FunctionAttrs/ |
D | out-of-bounds-iterator-bug.ll | 8 ; we _need_ the readonly on @va_func to trigger the problematic code path). It
|
/external/llvm-project/clang-tools-extra/docs/clang-tidy/checks/ |
D | cppcoreguidelines-macro-usage.rst | 6 Finds macro usage that is considered problematic because better language
|
/external/llvm-project/llvm/test/MC/X86/ |
D | align-branch-negative.s | 3 # This file includes cases which are problematic to apply automatic padding
|
/external/python/cpython3/Doc/c-api/ |
D | codec.rst | 82 :exc:`UnicodeTranslateError` that holds information about the problematic 86 containing the replacement for the problematic sequence, and an integer
|
/external/python/cpython2/Doc/c-api/ |
D | codec.rst | 82 :exc:`UnicodeTranslateError` that holds information about the problematic 86 containing the replacement for the problematic sequence, and an integer
|
/external/freetype/builds/amiga/ |
D | README | 100 replace problematic include files with your own version (same may be 103 - An example of how to replace/workaround a problematic include file
|
/external/llvm-project/llvm/docs/HistoricalNotes/ |
D | 2001-02-06-TypeNotationDebate.txt | 42 around for 27 years and perhaps more; why do you consider it problematic
|
/external/freetype/docs/ |
D | PROBLEMS | 26 up a list of such problematic fonts.
|
/external/llvm/docs/HistoricalNotes/ |
D | 2001-02-06-TypeNotationDebate.txt | 42 around for 27 years and perhaps more; why do you consider it problematic
|
/external/python/cpython3/Tools/c-analyzer/ |
D | README | 15 categories, the last two are problematic and generally should not exist
|
123456789