| /third_party/mesa3d/src/microsoft/compiler/ |
| D | dxil_signature.c | 370 struct semantic_info *semantic) { in fill_SV_param_nodes() argument
377 for (unsigned i = 0; i < semantic->rows; ++i) in fill_SV_param_nodes()
378 flattened_semantics[i] = dxil_get_metadata_int32(mod, semantic->index + i); in fill_SV_param_nodes()
381 SV_params_nodes[1] = dxil_get_metadata_string(mod, semantic->name); // Element name in fill_SV_param_nodes()
382 SV_params_nodes[2] = dxil_get_metadata_int8(mod, semantic->sig_comp_type); // Element type in fill_SV_param_nodes()
383 …SV_params_nodes[3] = dxil_get_metadata_int8(mod, (int8_t)semantic->kind); // Effective system value in fill_SV_param_nodes()
385 semantic->rows); // Semantic index vector in fill_SV_param_nodes()
386 SV_params_nodes[5] = dxil_get_metadata_int8(mod, semantic->interpolation); // Interpolation mode in fill_SV_param_nodes()
387 SV_params_nodes[6] = dxil_get_metadata_int32(mod, semantic->rows); // Number of rows in fill_SV_param_nodes()
388 SV_params_nodes[7] = dxil_get_metadata_int8(mod, semantic->cols); // Number of columns in fill_SV_param_nodes()
[all …]
|
| /third_party/typescript_eslint/packages/typescript-estree/tests/lib/__snapshots__/ |
| D | semantic-diagnostics-enabled.test.ts.snap | 3 …ed fixtures/comments/block-trailing-comment.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
5 … fixtures/comments/comment-within-condition.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
7 …res/comments/export-default-anonymous-class.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
9 …es" enabled fixtures/comments/jsdoc-comment.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
11 …ixtures/comments/jsx-attr-and-text-with-url.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
13 …enabled fixtures/comments/jsx-block-comment.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
15 …led fixtures/comments/jsx-comment-after-jsx.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
17 …comments/jsx-comment-after-self-closing-jsx.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
19 …es/comments/jsx-generic-with-comment-in-tag.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
21 …ixtures/comments/jsx-tag-comment-after-prop.src 1`] = `"TEST OUTPUT: No semantic or syntactic issu…
[all …]
|
| /third_party/mesa3d/src/gallium/drivers/svga/ |
| D | svga_tgsi_decl_sm30.c | 40 struct tgsi_declaration_semantic semantic, in translate_vs_ps_semantic() argument
44 switch (semantic.Name) { in translate_vs_ps_semantic()
46 *idx = semantic.Index; in translate_vs_ps_semantic()
50 *idx = semantic.Index; in translate_vs_ps_semantic()
54 *idx = semantic.Index + 2; /* sharing with COLOR */ in translate_vs_ps_semantic()
59 assert(semantic.Index == 0); in translate_vs_ps_semantic()
63 *idx = semantic.Index; in translate_vs_ps_semantic()
68 semantic.Index); in translate_vs_ps_semantic()
72 *idx = semantic.Index; in translate_vs_ps_semantic()
179 struct tgsi_declaration_semantic semantic, in ps30_input() argument
[all …]
|
| /third_party/boost/libs/metaparse/example/meta_hs/ |
| D | grammar.hpp | 55 semantic::if_
62 boost::metaparse::transform<token::name, semantic::ref>,
63 boost::metaparse::transform<token::int_, semantic::value>,
72 semantic::application
83 semantic::binary_op
94 semantic::binary_op
102 semantic::binary_op
115 semantic::lambda
118 semantic::pair
|
| /third_party/mesa3d/src/gallium/frontends/clover/core/ |
| D | binary.hpp | 98 enum semantic { enum
111 enum semantic semantic = general) : in argument()
114 ext_type(ext_type), semantic(semantic) { } in argument()
119 ext_type(zero_ext), semantic(general) { } in argument()
123 ext_type(zero_ext), semantic(general) { } in argument()
132 semantic semantic; member
|
| /third_party/skia/third_party/externals/swiftshader/src/Renderer/ |
| D | SetupProcessor.cpp | 130 …const Shader::Semantic& semantic = context->pixelShader->getInput(interpolant, component - project… in update() local
132 if(semantic.active()) in update()
137 if(semantic == context->vertexShader->getOutput(i, component - project)) in update()
146 switch(semantic.usage) in update()
149 case Shader::USAGE_COLOR: flat = semantic.flat || flatShading; break; in update()
164 const Shader::Semantic& semantic = context->pixelShader->getInput(interpolant, component); in update() local
166 switch(semantic.usage) in update()
171 state.gradient[interpolant][component].attribute = T0 + semantic.index; in update()
172 state.gradient[interpolant][component].flat = semantic.flat || (point && !sprite); in update()
175 state.gradient[interpolant][component].attribute = C0 + semantic.index; in update()
[all …]
|
| /third_party/boost/libs/spirit/doc/karma/ |
| D | action.qbk | 15 output by the generator attached to the semantic action. Semantic
33 [[`fa`] [A (semantic action) function with signature `void(Attrib&, Context&, bool&)`.
49 [[`g[fa]`] [Call semantic action, `fa` /before/ invoking `g`. The function
54 The possible signatures for functions to be used as semantic actions are:
67 the attribute type of the generator attached to the semantic action.
71 `context` is used by semantic actions written using __phoenix__ to access various
73 placeholder expressions usable in semantic actions see __karma_nonterminal_concept__.
75 The third parameter, `pass`, can be used by the semantic action to force the
90 generator the semantic action is attached to and the complexity of the function
91 or function object used as the semantic action.
[all …]
|
| D | actions.qbk | 18 Very much like for __qi__ we have semantic actions in __karma__ as well.
31 semantic action. In __karma__ the opposite happens. Semantic actions are called
45 [important Generally, and more formally, the semantic action `F` attached to
60 To sum up, the possible signatures for semantic actions are:
68 In the following example we present various ways to attach semantic actions:
117 There are more ways to bind semantic action functions, but the examples above
118 are the most common. Attaching semantic actions is the first hurdle one has
128 for binding semantic actions. It is like __boost_lambda__ on steroids, with
129 special custom features that make it easy to integrate semantic actions with
134 [important There are different ways to write semantic actions for __karma__:
[all …]
|
| D | complex.qbk | 18 Also this time, we're using __phoenix__ to do the semantic actions.
39 primitive generator `eps()`, which is usable as a semantic predicate. It has
54 Now on to the full example, this time with the proper semantic actions (the
65 The `double_` generators have this semantic action attached:
70 semantic action. Remember, semantic actions in __karma__ are called
72 to provide the generator with the data to be used. The semantic action
75 the attribute of the semantic action's attached generator. If you need
76 more information about semantic actions, you may want to read about them
79 These semantic actions are easy to understand but have the unexpected side
83 rid of the semantic actions altogether. When writing your grammars in Spirit
[all …]
|
| /third_party/boost/libs/spirit/doc/qi/ |
| D | action.qbk | 15 to be output by the parser attached to the semantic action. Semantic
33 [[`fa`] [A (semantic action) function with signature `void(Attrib&, Context, bool&)`.
49 [[`p[fa]`] [If `p` is successful, call semantic action, `fa`. The function
55 The possible signatures for functions to be used as semantic actions are:
68 the attribute type of the parser attached to the semantic action.
72 `context` used by semantic actions written using __phoenix__ to access various
74 placeholder expressions usable in semantic actions see __qi_nonterminal__.
76 The third parameter, `pass`, can be used by the semantic action to force the
91 parser the semantic action is attached to and the complexity of the function
92 or function object used as the semantic action.
[all …]
|
| D | actions.qbk | 15 need ['semantic actions].
40 Presented are various ways to attach semantic actions:
88 There are more ways to bind semantic action functions, but the examples above
89 are the most common. Attaching semantic actions is the first hurdle one has
99 for binding semantic actions. It is like __boost_lambda__ on steroids, with
100 special custom features that make it easy to integrate semantic actions with
103 will use __phoenix__ for semantic actions.
105 [important There are different ways to write semantic actions for __qi__:
112 use different libraries while writing a semantic action.
120 For semantic actions written using __phoenix__ use the placeholders
|
| /third_party/mesa3d/src/gallium/drivers/radeonsi/ |
| D | si_shader_llvm_tess.c | 390 ubyte semantic; in si_nir_load_tcs_varyings() local
393 semantic = info->input[driver_location].semantic; in si_nir_load_tcs_varyings()
395 semantic = info->output_semantic[driver_location]; in si_nir_load_tcs_varyings()
402 si_shader_io_get_unique_index(semantic, false) * 4; in si_nir_load_tcs_varyings()
414 assert((semantic >= VARYING_SLOT_PATCH0 || in si_nir_load_tcs_varyings()
415 semantic == VARYING_SLOT_TESS_LEVEL_INNER || in si_nir_load_tcs_varyings()
416 semantic == VARYING_SLOT_TESS_LEVEL_OUTER) == is_patch); in si_nir_load_tcs_varyings()
432 semantic); in si_nir_load_tcs_varyings()
451 ubyte semantic = info->input[driver_location].semantic; in si_nir_load_input_tes() local
453 assert((semantic >= VARYING_SLOT_PATCH0 || in si_nir_load_input_tes()
[all …]
|
| D | si_shader_llvm_vs.c | 460 unsigned semantic = outputs[i].semantic; in si_prepare_param_exports() local
466 switch (semantic) { in si_prepare_param_exports()
479 if ((semantic >= VARYING_SLOT_TEX0 && semantic <= VARYING_SLOT_TEX7) || in si_prepare_param_exports()
480 semantic >= VARYING_SLOT_VAR0) in si_prepare_param_exports()
486 if ((semantic <= VARYING_SLOT_VAR31 || semantic >= VARYING_SLOT_VAR0_16BIT) && in si_prepare_param_exports()
488 (1ull << si_shader_io_get_unique_index(semantic, true))) in si_prepare_param_exports()
516 if (outputs[i].semantic != VARYING_SLOT_COL0 && in si_vertex_color_clamping()
517 outputs[i].semantic != VARYING_SLOT_COL1 && in si_vertex_color_clamping()
518 outputs[i].semantic != VARYING_SLOT_BFC0 && in si_vertex_color_clamping()
519 outputs[i].semantic != VARYING_SLOT_BFC1) in si_vertex_color_clamping()
[all …]
|
| /third_party/boost/libs/spirit/doc/lex/ |
| D | lexer_semantic_actions.qbk | 15 of semantic actions for parsers (__qi__) and generators (__karma__). Lexer
16 semantic actions may be attached to any token definition. These are C++
34 (its first template parameter). The semantic action
41 (its first template parameter). The semantic action
45 If the semantic action sets it to `pass_fail` this
47 the first place. If the semantic action sets this
53 matched token. The semantic action is allowed to
60 lexer state control from inside a semantic
64 When using a C++ function as the semantic action the following prototypes are
72 [important In order to use lexer semantic actions you need to use type
[all …]
|
| /third_party/boost/libs/program_options/src/ |
| D | variables_map.cpp | 81 d.semantic()->parse(v.value(), options.options[i].value, utf8); in store()
83 v.m_value_semantic = d.semantic(); in store()
90 if (!d.semantic()->is_composing()) in store()
124 if (d.semantic()->apply_default(def)) { in store()
126 m[key].m_value_semantic = d.semantic(); in store()
131 if (d.semantic()->is_required()) { in store()
|
| /third_party/typescript/tests/baselines/reference/ |
| D | getEmitOutputWithSemanticErrorsForMultipleFiles2.baseline | 4 // File to emit, does not contain semantic errors, but --out is passed
5 // expected to not generate declarations because of the semantic errors in the other file
7 // File not emitted, and contains semantic errors
|
| D | getEmitOutputWithSemanticErrorsForMultipleFiles.baseline | 4 // File to emit, does not contain semantic errors
5 // expected to be emitted correctelly regardless of the semantic errors in the other file
|
| /third_party/mesa3d/src/mesa/state_tracker/ |
| D | st_cb_bitmap_shader.c | 58 unsigned i, semantic; in transform_instr() local
74 semantic = ctx->use_texcoord ? TGSI_SEMANTIC_TEXCOORD : in transform_instr()
77 if (ctx->info.input_semantic_name[i] == semantic && in transform_instr()
87 semantic, 0, TGSI_INTERPOLATE_PERSPECTIVE); in transform_instr()
|
| /third_party/boost/libs/xpressive/doc/ |
| D | symbols.qbk | 14 the data to be returned to your semantic action. Xpressive attributes, named
16 that it can be used in a semantic action. A default value can be specified
24 `a1`. Then, in the semantic action, it assigns the value stored in attribute
75 lookup. In the semantic action, the attribute is assigned to an integer
96 default value for an attribute can be specified in a semantic action with the
100 `( (a1=sym1) >> (a1=sym2)[ref(x)=a1] )[ref(y)=a1]`. The inner semantic action
101 sees the inner `a1`, and the outer semantic action sees the outer one. They can
|
| /third_party/mesa3d/src/gallium/auxiliary/tgsi/ |
| D | tgsi_emulate.c | 121 unsigned semantic; in transform_instr() local
127 semantic = in transform_instr()
130 if (semantic == TGSI_SEMANTIC_COLOR || in transform_instr()
131 semantic == TGSI_SEMANTIC_BCOLOR) in transform_instr()
|
| /third_party/typescript/src/testRunner/unittests/tsserver/ |
| D | projectReferenceErrors.ts | 147 semantic: [
164 semantic: [
216 semantic: [
233 semantic: [
|
| /third_party/mesa3d/src/gallium/drivers/r600/sfn/ |
| D | sfn_shader_geometry.cpp | 122 auto semantic = r600_get_varying_semantic(location); in process_store_output() local
123 io.name = semantic.first; in process_store_output()
124 io.sid = semantic.second; in process_store_output()
172 auto semantic = r600_get_varying_semantic(location); in process_load_input() local
173 io.name = semantic.first; in process_load_input()
174 io.sid = semantic.second; in process_load_input()
|
| /third_party/flutter/flutter/packages/flutter/test/widgets/ |
| D | semantics_9_test.dart | 14 testWidgets('hides semantic nodes of siblings', (WidgetTester tester) async {
52 …testWidgets('does not hides semantic nodes of siblings outside the current semantic boundary', (Wi…
106 …testWidgets('node is semantic boundary and blocking previously painted nodes', (WidgetTester teste…
|
| /third_party/flutter/flutter/packages/flutter/lib/src/semantics/ |
| D | semantics_event.dart | 55 /// An event for a semantic announcement.
92 /// An event for a semantic announcement of a tooltip.
111 /// An event which triggers long press semantic feedback.
117 /// Constructs an event that triggers a long-press semantic feedback by the platform.
124 /// An event which triggers tap semantic feedback.
130 /// Constructs an event that triggers a long-press semantic feedback by the platform.
|
| /third_party/boost/libs/test/doc/test_organization/ |
| D | semantic.qbk | 9 [section:semantic Adding semantic to a test]
11 It is sometimes useful to add a /semantic description/ to a test unit, which may be consulted by th…
|