Home
last modified time | relevance | path

Searched refs:confusing (Results 1 – 25 of 50) sorted by relevance

12

/llvm-project/llvm/docs/HistoricalNotes/
H A D2001-02-06-TypeNotationDebateResp2.txt10 > That is just too confusing:
14 > It is too confusing to have a list of 3 things, some of which are dimensions
28 If a two element list is too confusing, I would recommend an alternate
H A D2001-02-06-TypeNotationDebateResp1.txt13 and him that the C declarator syntax is difficult and confusing.
64 That is just too confusing:
67 It is too confusing to have a list of 3 things, some of which are dimensions
/llvm-project/clang/test/CodeGenHLSL/builtins/
H A DRWBuffer-subscript.hlsl
/llvm-project/llvm/utils/lit/tests/Inputs/shtest-define/errors/assignment/
H A Dbraces-with-number.txt3 # substitution), it would be confusing if someone tried to use the same name in
H A Dbraces-with-dot.txt3 # it would be confusing if someone tried to use the same name in a lit
/llvm-project/llvm/utils/lit/tests/Inputs/shtest-define/errors/defined-check/
H A Dredefine-multiple-once-exact.txt2 # another partial match, and that can lead to confusing expansions.
/llvm-project/clang-tools-extra/docs/clang-tidy/checks/misc/
H A Dmisleading-identifier.rst7 which can be confusing as they may change the understanding of a whole statement
/llvm-project/clang/test/utils/update_cc_test_checks/
H A Dglobal-value-regex.test11 # Show lit failures while avoiding confusing FileCheck input dump nesting.
H A Dglobal-hex-value-regex.test12 # Show lit failures while avoiding confusing FileCheck input dump nesting.
H A Dcheck-globals.test32 # Show lit failures while avoiding confusing FileCheck input dump nesting.
/llvm-project/clang/test/SemaCXX/
H A Dmissing-namespace-qualifier-typo-corrections.cpp96 void confusing() { in confusing() function
/llvm-project/llvm/test/CodeGen/AMDGPU/
H A Dat-least-one-def-value-assert.mir15 # LiveInterval computation, which was more confusing. The invalid
/llvm-project/lldb/test/Shell/Settings/
H A DTestStopCommandSourceOnError.test3 # implementation detail. This leads to confusing and unexpected scenarios.
/llvm-project/llvm/test/tools/llvm-exegesis/X86/
H A Danalysis-naive-clusterization-same-opcode-different-sched-class.test6 # may have different characteristics, and it will be confusing/misleading
/llvm-project/llvm/docs/
H A DBugpointRedesign.md11 through years of use: confusing to use, slow, it doesn’t always produce high
98 alone ends up confusing rather providing guidance. And, not only are there
/llvm-project/bolt/test/X86/
H A Dfalse-jump-table.s44 # Control flow confusing for JT detection
/llvm-project/clang-tools-extra/docs/clang-tidy/checks/bugprone/
H A Dforwarding-reference-overload.rst10 called, which can be confusing.
/llvm-project/llvm/test/CodeGen/X86/
H A Dpostra-ignore-dbg-instrs.mir14 # DBG_VALUE instruction confusing the sinking algorithm.
/llvm-project/clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines/
H A Drvalue-reference-param-not-moved.rst11 never moved is confusing and potentially indicative of a buggy program.
/llvm-project/llvm/test/DebugInfo/Mips/
H A Dfn-call-line.ll18 ; which would cause confusing stepping behaviour for the end user.
/llvm-project/llvm/utils/lit/tests/Inputs/shtest-define/
H A Dlit.cfg30 # The following substitution definitions are confusing and should be avoided.
/llvm-project/llvm/test/Analysis/LoopAccessAnalysis/
H A Dforward-loop-independent.ll6 ; FIXME: This does not actually always work which is pretty confusing. Right
/llvm-project/clang/test/SemaOpenCLCXX/
H A Daddress-space-deduction.clcpp96 // confusing.
/llvm-project/llvm/lib/Target/Mips/
H A DMSA.txt70 These three operations can be very confusing so here is a mapping
/llvm-project/llvm/docs/GlobalISel/
H A DIRTranslator.rst117 to prevent this from confusing debuggers.

12