Home
last modified time | relevance | path

Searched full:functionality (Results 1 – 25 of 8264) sorted by relevance

12345678910>>...331

/external/bazelbuild-rules_go/tests/core/
DREADME.rst12 * `Basic go_library functionality <go_library/README.rst>`_
13 * `output_groups functionality <output_groups/README.rst>`_
14 * `Basic -buildmode=plugin functionality <go_plugin/README.rst>`_
15 * `go_bazel_test macro functionality <go_bazel_test/README.rst>`_
19 * `Basic go_proto_library functionality <go_proto_library/README.rst>`_
21 * `Basic go_test functionality <go_test/README.rst>`_
23 * `Runfiles functionality <runfiles/README.rst>`_
27 * `stdlib functionality <stdlib/README.rst>`_
28 * `Basic go_binary functionality <go_binary/README.rst>`_
32 * `Basic go_path functionality <go_path/README.rst>`_
/external/pytorch/c10/core/
DDispatchKeySet.h49 // "functionality" bits and "backend bits", and every tensor holds its own
52 // specific piece of functionality. The functionality bits are *ordered*. When
53 // multiple functionality bits are set, we use the highest priority
54 // functionality. Similarly, multiple backend bits can theoretically be set if
95 // CUDABit) (b) functionalities: (per-backend) functionality-bit DispatchKeys
115 // Not every backend and not every functionality counts as a "building block
117 // Backend keys and functionality keys that count as "building blocks" will
118 // contribute to a full cross product of functionality that can be overriden.
121 // blocks (CPU, CUDA, XLA, ...) and at least 5 "functionality"
126 // dispatcher operator. Not every piece of functionality necessarily
[all …]
DDispatchKeySet.cpp213 // If the current functionality bit is a per-backend bit, we need special in operator ++()
218 // backend instance of this functionality key so we can skip it. in operator ++()
220 // increment the functionality mask so we skip the current functionality in operator ++()
228 // functionality bits are. in operator ++()
240 // in the keyset. In this case, we need to bump the functionality mask and in operator ++()
246 // over the same functionality bit next time, but a different backend bit. in operator ++()
250 // Functionality bits that aren't per backend are simpler to handle. We can in operator ++()
265 // loop through every functionality key (aside from Undefined). in initializeFunctionalityOffsetsAndMasks()
271 // If the previous functionality was not per-backend, then we can just in initializeFunctionalityOffsetsAndMasks()
284 // Sanity check that the computed offset index of the last functionality key in initializeFunctionalityOffsetsAndMasks()
[all …]
DDispatchKey.h21 // functionalities. When we encounter a functionality bit that is known to be
53 // WARNING! If we add a new per-backend functionality key that has higher
78 // pieces of functionality:
86 // per-backend functionality]
106 // to a type of functionality.
138 // This is not a "real" functionality, but it exists to give us a "nullopt"
154 // ~~~~~~~~~~~~~~~~~~~~~~~~~~ Functionality Keys ~~~~~~~~~~~~~~~~~~~~~~ //
156 // corresponds to an individual "functionality" that can be dispatched to.
166 // See [Note: Per-Backend Functionality Dispatch Keys] for details.
168 // See [Note: Per-Backend Functionality Dispatch Keys]
[all …]
/external/trusty/arm-trusted-firmware/lib/xlat_tables_v2/
Dro_xlat_tables.mk8 $(error "Debugfs requires functionality from the dynamic translation \
14 $(error "RESET_TO_SP_MIN requires functionality from the dynamic \
20 $(error "Tegra requires functionality from the dynamic translation \
24 $(error "RESET_TO_BL31 requires functionality from the dynamic \
29 $(error "Trusty requires functionality from the dynamic translation \
33 $(error "SPM_MM requires functionality to change memory region \
38 $(error "EL3 SPMC requires functionality from the dynamic translation \
/external/deqp/external/openglcts/modules/glesext/
DesextcTestCaseBase.hpp39 #define GEOMETRY_SHADER_EXTENSION_NOT_SUPPORTED "Geometry shader functionality not supported, skipp…
40 #define GEOMETRY_SHADER_POINT_SIZE_NOT_SUPPORTED "Geometry shader point size functionality not supp…
41 #define GPU_SHADER5_EXTENSION_NOT_SUPPORTED "GPU shader5 functionality not supported, skipping"
42 #define TESSELLATION_SHADER_EXTENSION_NOT_SUPPORTED "Tessellation shader functionality not supporte…
43 #define TEXTURE_BORDER_CLAMP_NOT_SUPPORTED "Texture border clamp functionality not supported, skipp…
45 "Floating point texture linear filtering functionality not supported, skipping"
46 #define TEXTURE_CUBE_MAP_ARRAY_EXTENSION_NOT_SUPPORTED "Texture cube map array functionality not su…
47 #define SHADER_IMAGE_ATOMIC_EXTENSION_NOT_SUPPORTED "Shader image atomic functionality not supporte…
48 #define TEXTURE_BUFFER_EXTENSION_NOT_SUPPORTED "Texture buffer functionality not supported, skippin…
49 #define DRAW_BUFFERS_INDEXED_NOT_SUPPORTED "Draw buffers indexed functionality not supported, skipp…
[all …]
/external/coreboot/src/soc/intel/common/block/include/intelblocks/
Dsmihandler.h51 * the SMI event on SLP_EN. The default functionality is provided in
59 * SMI_APM event. The default functionality is provided in
67 * SMI_PM1 event. The default functionality is provided in
75 * SMI_GPE0 event. The default functionality is provided in
83 * MC event. The default functionality is provided in
91 * minitor event. The default functionality is provided in
98 * SMI_TCO event. The default functionality is provided in
106 * SMI PERIODIC_STS event. The default functionality is provided in
114 * SMI GPIO_STS event. The default functionality is provided in
122 * SMI ESPI_STS event. The default functionality is provided in
/external/arm-trusted-firmware/lib/xlat_tables_v2/
Dro_xlat_tables.mk8 $(error "Debugfs requires functionality from the dynamic translation \
14 $(error "RESET_TO_SP_MIN requires functionality from the dynamic \
20 $(error "Tegra requires functionality from the dynamic translation \
24 $(error "RESET_TO_BL31 requires functionality from the dynamic \
29 $(error "Trusty requires functionality from the dynamic translation \
33 $(error "SPM_MM requires functionality to change memory region \
/external/chromiumos-config/payload_utils/merge_plugins/
Dmerge_hwid_test.py33 """Test the _set_support_status functionality."""
61 """Test basic audio codec functionality."""
87 """Test basic battery functionality."""
120 """Test basic bluetooth functionality."""
153 """Test basic cellular functionality."""
186 """Test basic cpu functionality."""
244 """Test basic display panel functionality."""
280 """Test basic display panel functionality."""
322 """Test basic ec_flash functionality."""
351 """Test basic ec functionality."""
[all …]
/external/sdv/vsomeip/third_party/boost/tti/doc/
Dtti_why.qbk10 In the Boost Type Traits library there is compile time functionality for
22 There has been some of this functionality in Boost, both in already existing
25 library is Boost MPL, where there is functionality, in the form of macros and
29 functionality of this library, related to type traits, was taken and expanded.
33 functionality to introspect a type's elements at compile time. But to the best
34 of my knowledge this sort of functionality has never been incorporated in
Dtti_nested_type.qbk10 Besides the functionality of the TTI library which queries whether some inner element
11 of a given name within a type exists, the library also includes functionality for
13 marker type is meant a type either internally created by the library, with no functionality,
16 First I will explain the syntax and use of this functionality and then the reason it exists in
19 The functionality is a metafunction created by the macro [macroref BOOST_TTI_MEMBER_TYPE].
26 to be generated and then the name of the 'named type'. After that the functionality
60 which has no functionality, is used. Unless there is a specific reason for the end-user
64 A simple example of this functionality would be:
77 we can now answer the question of why this functionality to create
122 have to work with, being a marker type, will generally not fulfill any other further functionality
[all …]
/external/pigweed/pw_digital_io/public/pw_digital_io/
Ddigital_io.h63 /// the derived classes that explicitly supports the functionality that your
67 /// derived classes that explicitly support the functionality that you want to
471 // Use this class in APIs when only interrupt functionality is required.
478 // Available functionality
489 // Unavailable functionality
509 // Use this class in APIs when only input functionality is required.
515 // Available functionality
524 // Unavailable functionality
547 // Use in APIs when input and interrupt functionality is required.
556 // Available functionality
[all …]
/external/icu/icu4c/source/test/intltest/
Dtchcfmt.h22 * tests Choice Format, functionality of examples, as well as API functionality
26 * tests basic functionality in a simple example
30 * tests functionality in a more complex example,
31 * and extensive API functionality.
Dtmsgfmt.h44 * test MesageFormat formatting functionality in a simple example
53 * tests MesageFormat functionality with a simple format
57 * tests MesageFormat functionality with a format including a ChoiceFormat
61 * tests MesageFormat functionality with a PluralFormat.
66 * tests MessageFormat functionality with a SelectFormat.
102 * These routines test various API functionality.
/external/cronet/stable/third_party/icu/source/test/intltest/
Dtchcfmt.h22 * tests Choice Format, functionality of examples, as well as API functionality
26 * tests basic functionality in a simple example
30 * tests functionality in a more complex example,
31 * and extensive API functionality.
Dtmsgfmt.h44 * test MesageFormat formatting functionality in a simple example
53 * tests MesageFormat functionality with a simple format
57 * tests MesageFormat functionality with a format including a ChoiceFormat
61 * tests MesageFormat functionality with a PluralFormat.
66 * tests MessageFormat functionality with a SelectFormat.
102 * These routines test various API functionality.
/external/cronet/tot/third_party/icu/source/test/intltest/
Dtchcfmt.h22 * tests Choice Format, functionality of examples, as well as API functionality
26 * tests basic functionality in a simple example
30 * tests functionality in a more complex example,
31 * and extensive API functionality.
Dtmsgfmt.h44 * test MesageFormat formatting functionality in a simple example
53 * tests MesageFormat functionality with a simple format
57 * tests MesageFormat functionality with a format including a ChoiceFormat
61 * tests MesageFormat functionality with a PluralFormat.
66 * tests MessageFormat functionality with a SelectFormat.
102 * These routines test various API functionality.
/external/pigweed/pw_digital_io/public/pw_digital_io/internal/
Dconversions.h23 // A type trait that describes the functionality required by a particular type
24 // of line, and also the functionality that we assume is always provided by an
29 // functionality as `true` and optional functionality as `false`.
39 // Concrete struct describing the available functionality of a line at runtime.
46 // Returns the functionality always provided by the given type.
57 // functionality.
/external/rust/android-crates-io/crates/glam/
DCONTRIBUTING.md23 If `glam` is missing functionality on existing types, [suggest a new feature]
26 the feature. I'd like to keep `glam` reasonably light functionality wise
27 initially but commonly used functionality that is missing is very welcome. If
28 you do submit a pull request please ensure any new functionality also has a
33 If you feel some functionality could be optimized please [open an issue] on
/external/pigweed/pw_digital_io/
Ddocs.rst72 Functionality overview
74 The following table summarizes the interfaces and their required functionality:
109 not cover every possible type of functionality supported by the hardware. There
186 and represents all the functionality that is available on the line.
200 not guarantee any particular functionality is available.
208 functionality.
214 functionality. For example, ``DigitalInOptionalInterrupt`` could describe a line
217 When using any classes with optional functionality, including
218 ``DigitalIoOptional``, you must check that a functionality is available using
251 depending on the supported set of functionality. For example, ``DigitalIn``
[all …]
/external/ltp/testcases/kernel/syscalls/mknod/
Dmknod08.c45 * Verify the Functionality of system call
47 * Issue Functionality-Pass message.
49 * Issue Functionality-Fail message.
58 * -f : Turn off functionality Testing.
131 /* Set the functionality flag */ in main()
139 /* unset flag as functionality fails */ in main()
147 /* unset flag as functionality fails */ in main()
155 /* unset flag as functionality fails */ in main()
159 tst_resm(TPASS, "Functionality of mknod(%s, " in main()
Dmknod05.c46 * Verify the Functionality of system call
48 * Issue Functionality-Pass message.
50 * Issue Functionality-Fail message.
58 * -f : Turn off functionality Testing.
134 /* Set the functionality flag */ in main()
141 /* unset functionality flag */ in main()
149 /* unset flag as functionality fails */ in main()
157 /* unset flag as functionality fails */ in main()
161 tst_resm(TPASS, "Functionality of mknod(%s, " in main()
/external/pytorch/c10/cuda/
DREADME.md1 c10/cuda is a core library with CUDA functionality. It is distinguished
3 contain any kernels, and consists solely of core functionality that is generally
6 **Important notes for developers.** If you want to add files or functionality
32 Thus, if you add new functionality to c10, you must also update `C10_MAPPINGS`
/external/libcap/cap/
Doslockluster.go9 // Launch functionality really needs to rely on the fact that an
16 // in this Launch() functionality:
21 // A value of false for this constant causes the Launch functionality
23 // have two choices with respect to the Launch functionality:

12345678910>>...331