Home
last modified time | relevance | path

Searched full:can (Results 1 – 25 of 9721) sorted by relevance

12345678910>>...389

/llvm-project/flang/test/Semantics/OpenMP/
H A Datomic01.f9018 !ERROR: At most one SEQ_CST clause can appear on the READ directive
22 !ERROR: At most one SEQ_CST clause can appear on the READ directive
26 !ERROR: At most one SEQ_CST clause can appear on the READ directive
31 !ERROR: At most one ACQUIRE clause can appear on the READ directive
35 !ERROR: At most one ACQUIRE clause can appear on the READ directive
39 !ERROR: At most one ACQUIRE clause can appear on the READ directive
44 !ERROR: At most one RELAXED clause can appear on the READ directive
48 !ERROR: At most one RELAXED clause can appear on the READ directive
52 !ERROR: At most one RELAXED clause can appear on the READ directive
58 !ERROR: At most one SEQ_CST clause can appea
[all...]
H A Dnested-simd.f9043 !ERROR: The only OpenMP constructs that can be encountered during execution of a 'SIMD' region are the `ATOMIC` construct, the `LOOP` construct, the `SIMD` construct, the `SCAN` construct and the `ORDERED` construct with the `SIMD` clause.
44 !ERROR: TEAMS region can only be strictly nested within the implicit parallel region or TARGET region
61 !ERROR: The only OpenMP constructs that can be encountered during execution of a 'SIMD' region are the `ATOMIC` construct, the `LOOP` construct, the `SIMD` construct, the `SCAN` construct and the `ORDERED` construct with the `SIMD` clause.
67 !ERROR: The only OpenMP constructs that can be encountered during execution of a 'SIMD' region are the `ATOMIC` construct, the `LOOP` construct, the `SIMD` construct, the `SCAN` construct and the `ORDERED` construct with the `SIMD` clause.
73 !ERROR: The only OpenMP constructs that can be encountered during execution of a 'SIMD' region are the `ATOMIC` construct, the `LOOP` construct, the `SIMD` construct, the `SCAN` construct and the `ORDERED` construct with the `SIMD` clause.
79 !ERROR: The only OpenMP constructs that can be encountered during execution of a 'SIMD' region are the `ATOMIC` construct, the `LOOP` construct, the `SIMD` construct, the `SCAN` construct and the `ORDERED` construct with the `SIMD` clause.
94 !ERROR: The only OpenMP constructs that can be encountered during execution of a 'SIMD' region are the `ATOMIC` construct, the `LOOP` construct, the `SIMD` construct, the `SCAN` construct and the `ORDERED` construct with the `SIMD` clause.
100 !ERROR: The only OpenMP constructs that can be encountered during execution of a 'SIMD' region are the `ATOMIC` construct, the `LOOP` construct, the `SIMD` construct, the `SCAN` construct and the `ORDERED` construct with the `SIMD` clause.
106 !ERROR: The only OpenMP constructs that can be encountered during execution of a 'SIMD' region are the `ATOMIC` construct, the `LOOP` construct, the `SIMD` construct, the `SCAN` construct and the `ORDERED` construct with the `SIMD` clause.
113 !ERROR: The only OpenMP constructs that can b
[all...]
/llvm-project/clang/test/SemaCXX/
H A Dwarn-unsafe-buffer-usage-in-container-span-construct.cpp45 std::span<int> S{p, 10}; // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
46 std::span<int> S1(p, 10); // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
47 std::span<int> S2 = std::span{p, 10}; // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
48 std::span<int> S3 = std::span(p, 10); // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
49 std::span<int> S4 = std::span<int>{p, 10}; // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
50 std::span<int> S5 = std::span<int>(p, 10); // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
51 std::span<int> S6 = {p, 10}; // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
52 auto S7 = std::span<int>{p, 10}; // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
53 auto S8 = std::span<int>(p, 10); // expected-warning{{the two-parameter std::span construction is unsafe as it can introduce mismatch between buffer size and the bound information}} in warnVarInit()
54 const auto &S9 = std::span<int>{p, 10}; // expected-warning{{the two-parameter std::span construction is unsafe as it can introduc in warnVarInit()
[all...]
/llvm-project/clang-tools-extra/docs/clang-tidy/checks/bugprone/
H A Dempty-catch.rst11 // Some code that can throw an exception
15 Having empty catch statements in a codebase can be a serious problem that
23 properly, and the program continues to run as if nothing happened. This can
26 * *Hidden Bugs*: If an exception is caught and ignored, it can lead to hidden
31 * *Security Issues*: Ignoring exceptions can lead to security issues, such as
32 buffer overflows or null pointer dereferences. Hackers can exploit these
35 * *Poor Code Quality*: Empty catch statements can indicate poor code quality
36 and a lack of attention to detail. This can make the codebase difficult to
40 * *Unreliable Code*: Code that ignores exceptions is often unreliable and can
41 lead to unpredictable behavior. This can cause frustration for users and
[all …]
/llvm-project/libcxx/test/std/strings/basic.string/string.modifiers/string_insert/
H A Dsize_T_size_size.pass.cpp74 test(S(""), 0, SV(""), 1, 0, S("can't happen")); in test0()
97 test(S(""), 0, SV("12345"), 6, 0, S("can't happen")); in test0()
121 test(S(""), 0, SV("1234567890"), 11, 0, S("can't happen")); in test0()
151 test(S(""), 0, SV("12345678901234567890"), 21, 0, S("can't happen")); in test1()
152 test(S(""), 1, SV(""), 0, 0, S("can't happen")); in test1()
153 test(S(""), 1, SV(""), 0, 1, S("can't happen")); in test1()
154 test(S(""), 1, SV(""), 1, 0, S("can't happen")); in test1()
155 test(S(""), 1, SV("12345"), 0, 0, S("can't happen")); in test1()
156 test(S(""), 1, SV("12345"), 0, 1, S("can't happen")); in test1()
157 test(S(""), 1, SV("12345"), 0, 2, S("can't happen")); in test1()
[all …]
H A Dsize_string_size_size.pass.cpp74 test(S(""), 0, S(""), 1, 0, S("can't happen")); in test0()
97 test(S(""), 0, S("12345"), 6, 0, S("can't happen")); in test0()
121 test(S(""), 0, S("1234567890"), 11, 0, S("can't happen")); in test0()
151 test(S(""), 0, S("12345678901234567890"), 21, 0, S("can't happen")); in test1()
152 test(S(""), 1, S(""), 0, 0, S("can't happen")); in test1()
153 test(S(""), 1, S(""), 0, 1, S("can't happen")); in test1()
154 test(S(""), 1, S(""), 1, 0, S("can't happen")); in test1()
155 test(S(""), 1, S("12345"), 0, 0, S("can't happen")); in test1()
156 test(S(""), 1, S("12345"), 0, 1, S("can't happen")); in test1()
157 test(S(""), 1, S("12345"), 0, 2, S("can't happen")); in test1()
[all …]
H A Dsize_pointer_size.pass.cpp65 test(S(""), 1, "", 0, S("can't happen")); in test()
66 test(S(""), 1, "12345", 0, S("can't happen")); in test()
67 test(S(""), 1, "12345", 1, S("can't happen")); in test()
68 test(S(""), 1, "12345", 2, S("can't happen")); in test()
69 test(S(""), 1, "12345", 4, S("can't happen")); in test()
70 test(S(""), 1, "12345", 5, S("can't happen")); in test()
71 test(S(""), 1, "1234567890", 0, S("can't happen")); in test()
72 test(S(""), 1, "1234567890", 1, S("can't happen")); in test()
73 test(S(""), 1, "1234567890", 5, S("can't happen")); in test()
74 test(S(""), 1, "1234567890", 9, S("can't happen")); in test()
[all …]
/llvm-project/clang-tools-extra/test/clang-tidy/checkers/readability/
H A Dsimplify-boolean-expr-demorgan.cpp3 // Check when we can convert !(A Op B) -> !A InvOp !B.
23 …// CHECK-MESSAGES-RELAXED: :[[@LINE-2]]:7: warning: boolean expression can be simplified by DeMorg… in foo()
24 …// CHECK-MESSAGES-RELAXED: :[[@LINE-2]]:7: warning: boolean expression can be simplified by DeMorg… in foo()
31 …// CHECK-MESSAGES: :[[@LINE-3]]:7: warning: boolean expression can be simplified by DeMorgan's the… in foo()
32 …// CHECK-MESSAGES: :[[@LINE-3]]:7: warning: boolean expression can be simplified by DeMorgan's the… in foo()
33 …// CHECK-MESSAGES: :[[@LINE-3]]:7: warning: boolean expression can be simplified by DeMorgan's the… in foo()
41 …// CHECK-MESSAGES: :[[@LINE-3]]:7: warning: boolean expression can be simplified by DeMorgan's the… in foo()
42 …// CHECK-MESSAGES: :[[@LINE-3]]:7: warning: boolean expression can be simplified by DeMorgan's the… in foo()
43 …// CHECK-MESSAGES: :[[@LINE-3]]:7: warning: boolean expression can be simplified by DeMorgan's the… in foo()
51 …// CHECK-MESSAGES: :[[@LINE-3]]:7: warning: boolean expression can be simplified by DeMorgan's the… in foo()
[all …]
H A Dqualified-auto.cpp16 …// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'auto TdNakedPtr' can be declared as 'auto *TdNakedPtr' in foo()
21 …// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'auto TdNakedCPtr' can be declared as 'const auto *TdN… in foo()
24 …// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'auto &TdNakedCRef' can be declared as 'const auto &Td… in foo()
44 // CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'auto UNakedPtr' can be declared as 'auto *UNakedPtr' in foo()
49 …// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'auto UNakedCPtr' can be declared as 'const auto *UNak… in foo()
52 …// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'auto &UNakedCRef' can be declared as 'const auto &UNa… in foo()
75 // CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'auto NakedPtr' can be declared as 'auto *NakedPtr' in foo()
78 …// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'auto NakedCPtr' can be declared as 'const auto *Naked… in foo()
82 …// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'const auto ConstPtr' can be declared as 'auto *const … in foo()
85 …// CHECK-MESSAGES: :[[@LINE-1]]:3: warning: 'const auto ConstCPtr' can be declared as 'const auto … in foo()
[all …]
H A Dnon-const-parameter.cpp5 // It can be defined both that the data is const and that the pointer is const,
6 // the checker only checks if the data can be const-specified.
15 // CHECK-MESSAGES: :[[@LINE+1]]:29: warning: pointer parameter 'last' can be pointer to const [read…
20 } // <- last can be const in warn1()
29 // CHECK-MESSAGES: :[[@LINE+1]]:19: warning: pointer parameter 'p' can be
36 // CHECK-MESSAGES: :[[@LINE+1]]:19: warning: pointer parameter 'p' can be
83 // CHECK-MESSAGES: :[[@LINE+1]]:17: warning: pointer parameter 'p' can be
89 // CHECK-MESSAGES: :[[@LINE+1]]:17: warning: pointer parameter 'p' can be
116 // CHECK-MESSAGES: :[[@LINE+1]]:18: warning: pointer parameter 'p' can be
122 // CHECK-MESSAGES: :[[@LINE+1]]:25: warning: pointer parameter 'p' can be
[all …]
/llvm-project/mlir/docs/
H A DActionTracing.md12 that can be intercepted by the framework for debugging or tracing purposes,
23 single stream of text that can be gigantic and requires tedious crawling through
25 and analyzing it can be very time consuming and often not very practical beyond
49 There are no constraints on the granularity of an “action”, it can be as simple
54 /// A custom Action can be defined minimally by deriving from
63 /// This tag should uniquely identify this action, it can be matched for filtering
71 Any transformation can then be dispatched with this `Action` through the
84 An action can also carry arbitrary payload, for example we can extend the
88 /// A custom Action can b
[all...]
/llvm-project/llvm/docs/GlobalISel/
H A DPipeline.rst33 the gMIR to suit what the backend can support. There is a very small set of
35 can shape the MIR as they wish.
80 alternatives but Combiners can also focus on code size or other metrics.
82 Additional passes such as these can be inserted to support higher optimization
87 Of course, combiners can be inserted in other places too. Also passes can be
100 function with the ``legalized`` property can have the ``MachineVerifier``
111 The main issue is that GlobalISel is a separate library, so we can't
126 can be serialized using ``-stop-before`` or ``-stop-after`` and loaded using
129 We can also go further still, as many of GlobalISel's passes are readily unit
136 FileCheck directives can be embedded using strings so you still have access to
[all …]
/llvm-project/lldb/docs/use/
H A Dondemand.rst4 On demand symbols can be enabled in LLDB for projects that generate debug info
6 enable debug information for all binaries and can end up producing many
7 gigabytes of debug information. This amount of debug information can greatly
8 increase debug session load times and can slow developer productivity when the
9 debug information isn't indexed. It can also cause expression evaluation to
35 Users can also put this command into their ~/.lldbinit file so it is always
48 target, some simple things can cause module to get its debug information
74 Setting breakpoints by function name can work, but we try to avoid using
81 mean that setting breakpoints on inline function names can fail for modules
88 symbol tables. This can cause breakpoint setting by function name to fail when
[all …]
H A Dtutorial.rst42 Options can be placed anywhere on the command line, but if the arguments begin
77 To set the same file and line breakpoint in LLDB you can enter either of:
84 To set a breakpoint on a function named ``foo`` in LLDB you can enter either of:
91 You can use the ``--name`` option multiple times to make a breakpoint on a set of
99 Setting breakpoints by name is even more specialized in LLDB as you can specify
101 breakpoint on all C++ methods named ``foo`` you can enter either of:
109 To set a breakpoint Objective-C selectors named ``alignLeftEdges:`` you can enter either of:
116 You can limit any breakpoints to a specific executable image by using the
124 The ``--shlib`` option can also be repeated to specify several shared libraries.
139 command can hav
[all...]
/llvm-project/flang/docs/
H A DFortranForCProgrammers.md18 a C or C++ programmer can get started more quickly with the language,
37 can be read only as discouraging their use in new code -- they'll
48 rules can be changed in the source.
108 User-defined ("derived") data types can be synthesized from the intrinsic
110 Derived types can be parameterized with integer values that either have
114 Derived types can inherit ("extend") from at most one other derived type.
115 They can have user-defined destructors (`FINAL` procedures).
116 They can specify default initial values for their components.
117 With some work, one can also specify a general constructor function,
121 Last, there are "typeless" binary constants that can be used in a few
[all …]
/llvm-project/clang-tools-extra/test/clang-tidy/checkers/misc/
H A Dconst-correctness-values.cpp13 char np_global = 0; // globals can't be known to be const
39 // CHECK-MESSAGES: [[@LINE-1]]:3: warning: variable 'p_local0' of type 'int' can be declared 'const' in some_function()
61 // CHECK-MESSAGES: [[@LINE-1]]:3: warning: variable 'p_local0' of type 'int' can be declared 'const' in nested_scopes()
70 // CHECK-MESSAGES: [[@LINE-1]]:3: warning: variable 'p_local0' of type 'int' can be declared 'const' in nested_scopes()
76 // CHECK-MESSAGES: [[@LINE-1]]:5: warning: variable 'p_local1' of type 'int' can be declared 'const' in ignore_reference_to_pointers()
90 // CHECK-MESSAGES: [[@LINE-1]]:3: warning: variable 'p_local0' of type 'int' can be declared 'const' in some_lambda_environment_capture_all_by_reference()
100 // CHECK-MESSAGES: [[@LINE-1]]:3: warning: variable 'p_local1' of type 'int' can be declared 'const' in some_lambda_environment_capture_all_by_value()
107 // CHECK-MESSAGES: [[@LINE-1]]:3: warning: variable 'p_local0' of type 'int' can be declared 'const' in some_lambda_environment_capture_all_by_value()
140 // CHECK-MESSAGES: [[@LINE-1]]:3: warning: variable 'p_local1' of type 'int' can be declared 'const'
145 // CHECK-MESSAGES: [[@LINE-1]]:3: warning: variable 'p_local2' of type 'int' can b in some_reference_taking()
[all...]
/llvm-project/clang/test/Sema/
H A Dtest-wunaligned-access.c23 …ned than 'struct T1' and is usually due to 'struct U1' being packed, which can lead to unaligned a…
29 …ned than 'struct T1' and is usually due to 'struct U2' being packed, which can lead to unaligned a…
61 …ned than 'struct T1' and is usually due to 'struct U7' being packed, which can lead to unaligned a…
82 …ed than 'struct T1' and is usually due to 'struct U10' being packed, which can lead to unaligned a…
97 …ed than 'struct T1' and is usually due to 'struct U12' being packed, which can lead to unaligned a…
103 …ed than 'struct T1' and is usually due to 'struct U13' being packed, which can lead to unaligned a…
109 …ed than 'struct T1' and is usually due to 'struct U14' being packed, which can lead to unaligned a…
115 …ed than 'struct T1' and is usually due to 'struct U15' being packed, which can lead to unaligned a…
136 …ed than 'struct T1' and is usually due to 'struct U18' being packed, which can lead to unaligned a…
141 …ed than 'struct T1' and is usually due to 'struct U19' being packed, which can lead to unaligned a…
[all …]
/llvm-project/clang/test/CXX/temp/temp.spec/temp.expl.spec/
H A Dp2-20.cpp45 static int A::y = 0; // expected-error {{'static' can only be specified inside the class definition}}
49 static void A::g() { } // expected-error {{'static' can only be specified inside the class definition}} in g()
93 static int B::y = 0; // expected-error {{'static' can only be specified inside the class definition}}
99 static int B::y<T*> = 0; // expected-error {{'static' can only be specified inside the class definition}}
105 static int B::y<T***>; // expected-error {{'static' can only be specified inside the class definition}}
112 // expected-error@-1 {{'static' can only be specified inside the class definition}}
118 static void B::g() { } // expected-error {{'static' can only be specified inside the class definition}} in g()
125 // expected-error@-1 {{'static' can only be specified inside the class definition}}
142 static int C<T>::y = 0; // expected-error {{'static' can only be specified inside the class definition}}
148 static void C<T>::g() { } // expected-warning {{'static' can onl
[all...]
/llvm-project/clang/test/Analysis/
H A Dptr-sort.cpp
/llvm-project/openmp/runtime/doc/doxygen/
H A Dconfig9 # For lists items can also be appended using:
31 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
37 # Using the PROJECT_BRIEF tag one can provide an optional one line description
43 # With the PROJECT_LOGO tag one can specify an logo or icon that is
60 # Enabling this option can be useful when feeding doxygen a huge amount of
125 # can be used to strip a user-defined part of the path. Stripping is
127 # the path. The tag can be used to show relative paths in the file list.
135 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
145 # (but less readable) file names. This can be useful if your file system
166 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
[all …]
/llvm-project/clang/test/OpenMP/
H A Drequires_messages.cpp9 …ed_shared_memory // expected-error {{only one unified_shared_memory clause can appear on a require…
11 #pragma omp requires unified_address // expected-error {{only one unified_address clause can appear…
13 …dress, unified_address // expected-error {{only one unified_address clause can appear on a require…
18 …se_offload, reverse_offload // rev-error {{only one reverse_offload clause can appear on a require…
23 … dynamic_allocators // expected-error {{only one dynamic_allocators clause can appear on a require…
27 …rder(acq_rel) // expected-error {{only one atomic_default_mem_order clause can appear on a require…
29 …rder(relaxed) // expected-error {{only one atomic_default_mem_order clause can appear on a require…
35 …match this '('}} expected-error {{only one atomic_default_mem_order clause can appear on a require…
41 …m_order' claus}} expected-error {{only one atomic_default_mem_order clause can appear on a require…
49 …p requires' are ignored}} expected-error {{only one unified_address clause can appear on a require…
[all …]
/llvm-project/llvm/docs/
H A DXRay.rst15 instrumentation points and a runtime library that can dynamically enable and
18 More high level information about XRay can be found in the `XRay whitepaper`_.
45 You can use XRay in a couple of ways:
66 get XRay instrumentation points. You can tweak that number through the
73 The loop detection can be disabled with ``-fxray-ignore-loops`` to use only the
74 instruction threshold. You can also specifically instrument functions in your
76 You can do it using the GCC-style attributes or C++11-style attributes.
88 When linking a binary, you can either manually link in the `XRay Runtime
90 ``-fxray-instrument`` flag. Alternatively, you can statically link-in the XRay
98 If you're using LLVM IR directly, you can ad
[all...]
/llvm-project/lldb/source/Commands/
H A DCommandOptionArgumentTable.cpp19 return "Register names can be specified using the architecture specific " in RegisterNameHelpTextCallback()
21 "They can also be specified using generic names. Not all generic " in RegisterNameHelpTextCallback()
46 "can specify all the locations of a breakpoint by just indicating the " in BreakpointIDHelpTextCallback()
58 "This can be done through several mechanisms. The easiest way is to " in BreakpointIDRangeHelpTextCallback()
61 "breakpoint locations under a major breakpoint, you can use the major " in BreakpointIDRangeHelpTextCallback()
64 "breakpoint 5. You can also indicate a range of breakpoints by using " in BreakpointIDRangeHelpTextCallback()
66 "range can " in BreakpointIDRangeHelpTextCallback()
75 return "A name that can be added to a breakpoint when it is created, or " in BreakpointNameHelpTextCallback()
78 "Breakpoint names can be used to specify breakpoints in all the " in BreakpointNameHelpTextCallback()
80 "and breakpoint ID ranges can be used. As such they provide a " in BreakpointNameHelpTextCallback()
[all …]
/llvm-project/mlir/docs/Bindings/
H A DPython.md43 # The pip version can be obtained with `python -m pip --version`, and for
86 composable modules that downstream integrators can include and re-export into
104 translation unit. Breaking into multiple translation units can significantly aid
137 that one-time initialization code can be invoked apart from module constructors.
195 increases the chances that interesting DSLs and higher level APIs can be
204 As mentioned above, `PyOperation` is special because it can exist in either a
205 top-level or dependent state. The life-cycle is unidirectional: operations can
216 for regions and blocks and needs to be a top-level type that we can count on not
233 With the way it is now, we can avoid having a global live list for regions and
236 objects. We can cros
[all...]
/llvm-project/llvm/docs/Frontend/
H A DPerformanceTips.rst20 surprisingly small changes in the source IR can have a large effect on the
26 can often be useful to write a quick C program with the semantics you're trying
28 Studying Clang's CodeGen directory can also be a good source of ideas. Note
39 will be enabled. This can have a major effect on the generated code quality.
53 An alloca instruction can be used to represent a function scoped stack slot,
54 but can also represent dynamic frame expansion. When representing function
63 SSA is the canonical form expected by much of the optimizer; if allocas can
101 On some architectures (X86_64 is one), sign extension can involve an extra
102 instruction whereas zero extension can be folded into a load. LLVM will try to
103 replace a sext with a zext when it can b
[all...]

12345678910>>...389