Home
last modified time | relevance | path

Searched full:are (Results 1 – 25 of 11160) sorted by relevance

12345678910>>...447

/llvm-project/llvm/test/MC/AMDGPU/
H A Dgfx10_asm_vopc.s12 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
16 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
20 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
24 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
28 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
32 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
36 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
40 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
44 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are not valid for this GPU or mode
48 // W32-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: operands are no
[all...]
H A Dgfx12_asm_vopc.s9 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
13 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
17 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
21 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
25 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
29 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
33 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
37 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
41 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
45 // W64-ERR: :[[@LINE-2]]:1: error: operands are no
[all...]
H A Dgfx11_asm_vopc.s9 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
13 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
17 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
21 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
25 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
29 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
33 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
37 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
41 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
45 // W64-ERR: :[[@LINE-2]]:1: error: operands are no
[all...]
H A Dgfx11_asm_vop2_t16_err.s
H A Dgfx12_asm_vopc_dpp16.s9 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
13 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
17 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
21 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
25 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
29 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
33 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
37 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
41 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
45 // W64-ERR: :[[@LINE-2]]:1: error: operands are no
[all...]
H A Dgfx12_asm_vop2_t16_err.s
H A Dgfx11_asm_vopc_dpp16.s9 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
13 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
17 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
21 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
25 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
29 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
33 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
37 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
41 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
45 // W64-ERR: :[[@LINE-2]]:1: error: operands are no
[all...]
H A Dgfx12_asm_vopc_dpp8.s9 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
13 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
17 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
21 // W32-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
25 // W32-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
29 // W32-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
33 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
37 // W32-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
41 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
45 // W32-ERR: :[[@LINE-2]]:1: error: operands are no
[all...]
H A Dgfx11_asm_vopc_dpp8.s9 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
13 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
17 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
21 // W32-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
25 // W32-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
29 // W32-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
33 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
37 // W32-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
41 // W64-ERR: :[[@LINE-2]]:1: error: operands are not valid for this GPU or mode
45 // W32-ERR: :[[@LINE-2]]:1: error: operands are no
[all...]
H A Dmai-err.s64 // GFX908: :[[@LINE-2]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
67 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
71 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
75 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
79 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
83 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
87 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
91 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
95 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
99 // GFX908: :[[@LINE-1]]:{{[0-9]+}}: error: inline constants are not allowed for this operand
[all …]
H A Dgfx12_asm_vopc_t16_err.s
H A Dvop3-literal.s8 // GFX9-ERR: error: literal operands are not supported
12 // GFX9-ERR: error: literal operands are not supported
16 // GFX9-ERR: error: literal operands are not supported
20 // GFX9-ERR: error: literal operands are not supported
24 // GFX9-ERR: error: literal operands are not supported
28 // GFX9-ERR: error: literal operands are not supported
32 // GFX9-ERR: error: literal operands are not supported
36 // GFX9-ERR: error: literal operands are not supported
40 // GFX9-ERR: :[[@LINE-2]]:{{[0-9]+}}: error: literal operands are not supported
44 // GFX9-ERR: error: literal operands are no
[all...]
/llvm-project/llvm/test/Verifier/
H A Dsme-attributes.ll4 ; CHECK: Attributes 'aarch64_pstate_sm_enabled and aarch64_pstate_sm_compatible' are incompatible!
7 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutually exclusive
10 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutually exclusive
13 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutually exclusive
16 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutually exclusive
19 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutually exclusive
22 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutually exclusive
25 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutually exclusive
28 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutually exclusive
31 ; CHECK: Attributes 'aarch64_new_za', 'aarch64_in_za', 'aarch64_out_za', 'aarch64_inout_za', 'aarch64_preserves_za' and 'aarch64_za_state_agnostic' are mutuall
[all...]
/llvm-project/mlir/include/mlir/Dialect/SPIRV/IR/
H A DSPIRVIntegerDotProductOps.td87 When Vector 1 and Vector 2 are scalar integer types, Packed Vector
88 Format must be specified to select how the integers are to be
91 All components of the input vectors are sign-extended to the bit width
92 of the result's type. The sign-extended input vectors are then
94 from the component-wise multiplication are added together. The resulting
117 Components of Vector 1 are treated as signed, components of Vector 2 are
129 and Vector 2 are vectors, the components of Vector 2 must have a
132 When Vector 1 and Vector 2 are scalar integer types, Packed Vector
133 Format must be specified to select how the integers are to be
136 All components of Vector 1 are sign-extended to the bit width of the
[all …]
/llvm-project/clang/docs/
H A DConstantInterpreter.rst12 clang, improving performance on constructs which are executed inefficiently
24 one to directly evaluate expressions as they are compiled, without
25 generating bytecode (``EvalEmitter``). All functions are compiled to
26 bytecode, while toplevel expressions used in constant contexts are directly
34 description of opcodes, can be found in ``Opcodes.td``. The opcodes are
50 implement integral types which are required by the target, but are not
87 records (structs and classes). Unions are represented as records, except
89 fields are kept until they are reactivate
[all...]
/llvm-project/clang/test/OpenMP/
H A Dcancellation_point_messages.cpp13 …ion point'}} expected-error {{orphaned 'omp cancellation point' directives are prohibited; perhaps… in main()
19 … of '#pragma omp cancellation point' are ignored}} expected-error {{orphaned 'omp cancellation poi… in main()
20 … of '#pragma omp cancellation point' are ignored}} expected-error {{orphaned 'omp cancellation poi… in main()
21 … of '#pragma omp cancellation point' are ignored}} expected-error {{orphaned 'omp cancellation poi… in main()
22 … of '#pragma omp cancellation point' are ignored}} expected-error {{orphaned 'omp cancellation poi… in main()
24 …bstatement}} expected-error {{orphaned 'omp cancellation point' directives are prohibited; perhaps… in main()
51 …bstatement}} expected-error {{orphaned 'omp cancellation point' directives are prohibited; perhaps… in main()
53 … sections // expected-error {{orphaned 'omp cancellation point' directives are prohibited; perhaps… in main()
56 …bstatement}} expected-error {{orphaned 'omp cancellation point' directives are prohibited; perhaps… in main()
60 …taskgroup // expected-error {{orphaned 'omp cancellation point' directives are prohibited; perhaps… in main()
[all …]
H A Dcancel_messages.cpp13 …e '#pragma omp cancel'}} expected-error {{orphaned 'omp cancel' directives are prohibited; perhaps… in main()
19 … tokens at the end of '#pragma omp cancel' are ignored}} expected-error {{orphaned 'omp cancel' di… in main()
20 … tokens at the end of '#pragma omp cancel' are ignored}} expected-error {{orphaned 'omp cancel' di… in main()
21 … tokens at the end of '#pragma omp cancel' are ignored}} expected-error {{orphaned 'omp cancel' di… in main()
22 … tokens at the end of '#pragma omp cancel' are ignored}} expected-error {{orphaned 'omp cancel' di… in main()
24 …immediate substatement}} expected-error {{orphaned 'omp cancel' directives are prohibited; perhaps… in main()
51 …immediate substatement}} expected-error {{orphaned 'omp cancel' directives are prohibited; perhaps… in main()
53 #pragma omp cancel sections // expected-error {{orphaned 'omp cancel' directives are prohibited; pe… in main()
56 …immediate substatement}} expected-error {{orphaned 'omp cancel' directives are prohibited; perhaps… in main()
60 #pragma omp cancel taskgroup // expected-error {{orphaned 'omp cancel' directives are prohibited; p… in main()
[all …]
/llvm-project/llvm/include/llvm/Transforms/Utils/
H A DFunctionComparator.h10 // are used by the MergeFunctions pass for comparing functions.
45 /// globals need to maintain their relative order. Globals are assigned a number
46 /// when they are first visited. This order is deterministic, and so the
47 /// assigned numbers are as well. When two functions are merged, neither number
48 /// is updated. If the symbols are weak, this would be incorrect. If they are
92 /// side of claiming that two functions are different).
125 /// Stage 0: If types are equal in terms of cmpTypes, then we can go straight
129 /// Stage 1: Types that satisfies isFirstClassType conditions are alway
[all...]
/llvm-project/flang/test/Semantics/
H A Dallocate06.f9056 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
58 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
59 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
61 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
63 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
64 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
66 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
68 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
70 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
71 …!ERROR: Type parameters in type-spec must be assumed if and only if they are assumed for allocatab…
[all …]
H A Dresolve53.f906 !ERROR: Generic 'g' may not have specific procedures 's2' and 's4' as their interfaces are not distinguishable
28 !ERROR: Generic 'g' may not have specific procedures 'm2s1' and 'm2s2' as their interfaces are not distinguishable
39 !ERROR: Generic 'g' may not have specific procedures 'm3f1' and 'm3f2' as their interfaces are not distinguishable
65 ! These are all different ranks so they are distinguishable
82 !ERROR: Generic 'g' may not have specific procedures 'm5s1' and 'm6s4' as their interfaces are not distinguishable
91 !ERROR: Generic 'g' may not have specific procedures 'm5s1' and 'm7s5' as their interfaces are not distinguishable
92 !ERROR: Generic 'g' may not have specific procedures 'm5s2' and 'm7s5' as their interfaces are not distinguishable
93 !ERROR: Generic 'g' may not have specific procedures 'm5s3' and 'm7s5' as their interfaces are not distinguishable
101 ! Two procedures that differ only by attributes are no
[all...]
/llvm-project/llvm/test/Transforms/ObjCARC/
H A Dprovenance.ll39 ; CHECK: y1 and y2 are related.
40 ; CHECK: y1 and y3 are related.
41 ; CHECK: y2 and y3 are related.
42 ; CHECK: x0 and y1 are not related.
43 ; CHECK: x0 and y2 are not related.
44 ; CHECK: x0 and y3 are not related.
45 ; CHECK: l_objc_msgSend_fixup_ and y1 are not related.
46 ; CHECK: l_objc_msgSend_fixup_ and y2 are not related.
47 ; CHECK: l_objc_msgSend_fixup_ and y3 are not related.
48 ; CHECK: x1 and y1 are not related.
[all …]
/llvm-project/mlir/docs/Rationale/
H A DMLIRForGraphAlgorithms.md6 concern for others who are more concerned about the "here and now" - why does it
20 MLIR's relationship to XLA, Eigen, etc, are out of scope for this particular
34 graph rewriting, and others - which are independent of the representational
40 TensorFlow has numerous subsystems (some of which are proprietary, e.g.
47 going on: they are both particular data structures and encodings (e.g. HLO
55 that describe the set of operations that are legal and supported for a given
56 application. This means that the actual translations between data structures are
57 kept as simple as possible - and are thus relatively easy to make "correct".
73 high, and often very specific to that subsystem. That said, there are several
74 subsystems that are about to get rewritten or substantially revised anyway, so
[all …]
/llvm-project/clang/test/SemaObjC/
H A Dproperty-10.m6 …int p0; // expected-error {{property attributes 'readonly' and 'readwrite' are mutually exclusive}}
13 @property(assign, copy) id p3_0; // expected-error {{property attributes 'assign' and 'copy' are mu…
14 …in) id p3_1; // expected-error {{property attributes 'assign' and 'retain' are mutually exclusive}…
15 …ng) id s3_1; // expected-error {{property attributes 'assign' and 'strong' are mutually exclusive}…
16 @property(copy, retain) id p3_2; // expected-error {{property attributes 'copy' and 'retain' are mu…
17 @property(copy, strong) id s3_2; // expected-error {{property attributes 'copy' and 'strong' are mu…
18 … attributes 'assign' and 'copy' are mutually exclusive}}, expected-error {{property attributes 'as…
19 … attributes 'assign' and 'copy' are mutually exclusive}}, expected-error {{property attributes 'as…
21 …_0; // expected-error {{property attributes 'unsafe_unretained' and 'copy' are mutually exclusive}…
22 …; // expected-error {{property attributes 'unsafe_unretained' and 'retain' are mutually exclusive}…
[all …]
/llvm-project/clang/docs/analyzer/developer-docs/
H A DIPA.rst4 There are several options that control which calls the analyzer will consider for
22 determined at runtime and we are not 100% sure that our type info is
28 has code that is only exercised when some of its methods are overridden.
35 analyzer's configuration table, so they are all specified as follows:
66 Currently, template functions are considered for inlining by default.
82 Currently, C++ standard library functions are considered for inlining by
85 The standard library functions and the STL in particular are used ubiquitously
99 Currently, these constructors and destructors are NOT considered for inlining
103 named 'iterator' or a member named 'begin'; these names are idiomatic in C++,
115 Many of these issues are avoided if containers always have unknown, symbolic
[all …]
/llvm-project/clang/lib/Headers/
H A Dammintrin.h34 /// The value from which bits are extracted.
36 /// Bits [5:0] specify the length; the other bits are ignored. If bits [5:0]
37 /// are zero, the length is interpreted as 64.
40 /// bits are ignored. If the sum of the index and length is greater than 64,
41 /// the result is undefined. If the length and index are both zero, bits
42 /// [63:0] of parameter \a x are extracted. If the length is zero but the
59 /// The value from which bits are extracted.
62 /// length at [5:0]; all other bits are ignored. If bits [5:0] are zero, the
64 /// greater than 64, the result is undefined. If the length and index are
65 /// both zero, bits [63:0] of parameter \a __x are extracted. If the length
[all …]

12345678910>>...447