Searched full:applications (Results 1 – 25 of 3734) sorted by relevance
12345678910>>...150
| /third_party/typescript/tests/baselines/reference/tsserver/cachingFileSystemInformation/ |
| D | watchDirectories-for-config-file-with-case-insensitive-file-system.js | 3 //// [/Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts]
6 //// [/Users/someuser/work/applications/frontend/src/app/redux/configureStore.ts]
22 //// [/Users/someuser/work/applications/frontend/tsconfig.json]
32 Info 1 [00:00:34.000] Search path: /Users/someuser/work/applications/frontend/src/app/utils
33 …fo: /Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts :: Config file name: /Use…
34 Info 3 [00:00:36.000] Creating configuration project /Users/someuser/work/applications/frontend/…
35 …tchInfo: /Users/someuser/work/applications/frontend/tsconfig.json 2000 undefined Project: /Users/s…
36 Info 5 [00:00:38.000] Config: /Users/someuser/work/applications/frontend/tsconfig.json : {
38 "/Users/someuser/work/applications/frontend/src/app/redux/configureStore.ts",
39 "/Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts"
[all …]
|
| D | watchDirectories-for-config-file-with-case-sensitive-file-system.js | 3 //// [/Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts]
6 //// [/Users/someuser/work/applications/frontend/src/app/redux/configureStore.ts]
22 //// [/Users/someuser/work/applications/frontend/tsconfig.json]
32 Info 1 [00:00:34.000] Search path: /Users/someuser/work/applications/frontend/src/app/utils
33 …fo: /Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts :: Config file name: /Use…
34 Info 3 [00:00:36.000] Creating configuration project /Users/someuser/work/applications/frontend/…
35 …tchInfo: /Users/someuser/work/applications/frontend/tsconfig.json 2000 undefined Project: /Users/s…
36 Info 5 [00:00:38.000] Config: /Users/someuser/work/applications/frontend/tsconfig.json : {
38 "/Users/someuser/work/applications/frontend/src/app/redux/configureStore.ts",
39 "/Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts"
[all …]
|
| /third_party/rust/rust/src/doc/rustc/src/platform-support/ |
| D | unknown-uefi.md | 47 UEFI uses a single address-space to run all code in. Multiple applications can
87 UEFI applications can be copied into the ESP on any UEFI system and executed
89 executing UEFI applications as well. See its documentation for details.
92 wrapper around `qemu` that can spawn UEFI applications in qemu. You can install
93 it via `cargo install uefi-run` and execute qemu applications as
108 - Use the **GNU-EFI** suite. This approach is used by many UEFI applications
135 - **efi**: *Ergonomic Rust bindings for writing UEFI applications*. Provides
137 environment to write UEFI applications.
146 UEFI applications written in rust.
147 - **uefi-run**: *Run UEFI applications*. A small wrapper around _qemu_ to spawn
[all …]
|
| /third_party/curl/docs/libcurl/ |
| D | libcurl-security.md | 26 Many applications are used in closed networks where users and servers can
29 some risks in the ways in which applications commonly use libcurl and
31 classes of attacks that robust applications should consider. The Common
56 For applications that enable .netrc use, a user who manage to set the right
106 enabled by default. Applications may opt to restrict that set further.
132 Applications can mitigate against this by disabling
158 10.1.2.3. Applications can mitigate against this by setting a
166 and display the result. Applications can mitigate against this with the
172 behind a firewall. Applications can mitigate against this by using the
211 overwritten. Applications must not allow any unsanitized URL to be passed in
[all …]
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/proposals/ |
| D | VK_KHR_cooperative_matrix.asciidoc | 16 A growing number of GPU applications are making use of matrix multiplication
20 SPIR-V/API mechanism to expose these features to applications or libraries.
24 Applications or libraries can use subgroup primitives to write more efficient
27 requires applications to have a lot of device-specific knowledge.
35 a wide variety of devices and applications and is thus a good candidate for
|
| D | VK_EXT_shader_module_identifier.adoc | 11 In some applications, SPIR-V is generated on-the-fly, usually by translating from some other repres…
14 In such applications, the overhead required to obtain valid SPIR-V before any pipeline creation cal…
15 Especially in graphics API translation layering efforts, applications expect that compilation with …
19 - Applications compile PSOs late -> stutter! -> but we are expected to mitigate
20 …- Applications compile a lot of PSOs early -> good! but can lead to excessive load times even on s…
74 is also needed so applications know if we need to throw away any caches using the identifier.
78 To make the API friendly to applications, there is a small upper bound on how large an identifier m…
104 === RESOLVED: Should applications be allowed to specify their own shader module identifier?
108 It is plausible that applications might want to generate their own keys instead of using driver-gen…
116 Applications could also hash the resulting SPIR-V and ensure non-duplicated identifiers this way,
[all …]
|
| D | VK_EXT_graphics_pipeline_library.adoc | 12 applications that have large numbers of materials, large amounts of
47 simple to perform, and applications should have control over when and how
76 inputs, render passes) allows for applications to individually compile
90 This proposal focuses on option 3 – providing applications with the ability
103 applications to create partial pipelines (pipeline libraries) containing
148 applications can link pipelines on demand while recording commands.
153 supported, applications must provide matching interpolation decorations in
161 applications are:
379 `VK_PIPELINE_CREATE_LINK_TIME_OPTIMIZATION_BIT_EXT` allows applications
409 Applications can continue to use shader modules as they are not
[all …]
|
| D | VK_EXT_shader_object.adoc | 10 …sively address problems the pipeline abstraction has created for both applications and implementat…
16 …ader patching that was so problematic for IHVs, and so detrimental to performance for applications.
18 … the burden of the shader state combinatorics out of drivers and into applications, ideally avoidi…
20 Implicit in such a design was an assumption that applications would be able to know and provide nea…
26 …ality that the natural design patterns of the most demanding class of applications which use graph…
28 …applications set various pieces of "pipeline" state independently, then hash it all at draw time a…
30 …to wait it out until application codebases are rewritten or replaced. Applications need the featur…
34 …turn to the old problem of the graphics API artificially constraining applications from accessing …
36 …applications on these platforms to waste storage space shipping both uncompiled SPIR-V and precomp…
64 …T` objects created at the same time. To create `VkShaderEXT` objects, applications call `vkCreateS…
[all …]
|
| D | VK_EXT_frame_boundary.adoc | 26 applications, a frame is typically the work needed to render into the image that
33 ### Graphics applications bypassing the Khronos swapchain
35 Graphics applications are not tied to use the Khronos swapchain, and they may
39 ### Compute-only applications
41 Compute-only applications typically do not interact with a presentation engine at
84 We want applications to be able to group queue submissions by frames. To this
85 aim, we let applications tag queue submissions with a `uint64_t` frame
176 . a list of VkBuffer: which allows applications that do not produce their
177 final result as an image (eg. compute applications) to provide the final
190 In practice it is advised that applications use a single monotonically
[all …]
|
| /third_party/openssl/ |
| D | README-ENGINES.md | 58 applications when they use that ENGINE. Work is in progress (or at least
60 NCONF) code so that applications using OpenSSL's existing configuration
62 Presently however, applications must use the ENGINE API itself to provide
86 devices from common OpenSSL-based applications. Bugs and/or inexplicable
119 This way, applications do not need to know anything specific to any
135 applications. This could be because existing compiled-in implementations
141 The other use-case for "dynamic" is with applications that wish to
147 applications based on OpenSSL 0.9.7 or later. If you're using an
180 ENGINE's "id". For most applications, this isn't necessary - but some
216 Applications that support the ENGINE API and more specifically, the
[all …]
|
| /third_party/openssl/doc/man7/ |
| D | fips_module.pod | 20 Applications written to use the OpenSSL 3.0 FIPS module should not use any
45 =head2 Making all applications use the FIPS module by default
47 One simple approach is to cause all applications that are using OpenSSL to only
50 This approach can be done purely via configuration. As long as applications are
99 Any applications that use OpenSSL 3.0 and are started after these changes are
100 made will start using only the FIPS module unless those applications take
108 are required in applications in order to benefit from the FIPS module. There are
115 You may not want all applications to use the FIPS module.
117 It may be the case that some applications should and some should not use the
122 If applications take explicit steps to not load the default config file or
[all …]
|
| D | migration_guide.pod | 28 of applications will work unchanged with OpenSSL 3.0 if those applications
31 applications need to take advantage of some of the new features available in
72 L</Using the FIPS Module in applications>.
89 your applications, but you may start to see deprecation warnings during
104 Applications using the EVP APIs to access these algorithms should instead use
105 more modern algorithms. If that is not possible then these applications
119 This is particularly relevant for applications written to use the OpenSSL 3.0
173 Existing applications that use KDF algorithms using EVP_PKEY
176 All new applications should use the new L<EVP_KDF(3)> interface.
188 All new applications should use the new L<EVP_MAC(3)> interface.
[all …]
|
| /third_party/rust/crates/libc/ci/ |
| D | android-emulator-package.xml | 29 …usive, and non-sublicensable license to use the SDK solely to develop applications for compatible …
31 …applications for other platforms (including non-compatible implementations of Android) or to devel…
39 …e to you and that future versions of the SDK may be incompatible with applications developed on pr…
48 …o any software applications that you develop using the SDK, including any intellectual property ri…
50 4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) the…
52 4.3 You agree that if you use the SDK to develop applications for general public users, you will pr…
56 …resources that you create, transmit or display through Android and/or applications for Android, an…
62 …u may choose yourself and that you will be solely responsible for all applications that are develo…
71 7. Third Party Applications
73 …applications developed by a third party or that access data, content or resources provided by a th…
[all …]
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/appendices/ |
| D | boilerplate.txt | 18 Khronos provides a corresponding set of header files for applications using
37 Applications normally will include the header `{full_header}`.
136 Applications that do not make use of window system-specific extensions may
166 Applications should not use this value as their
168 Instead applications should explicitly select a specific fixed major/minor
222 Applications must: not define handles in a way that is not binary compatible
272 allowing applications to decide which ones should be defined and how the
278 Before including these platform-specific Vulkan headers, applications must:
282 As a convenience for applications that do not need the flexibility of
286 Applications control which platform-specific headers are included by
[all …]
|
| D | boilerplate.adoc | 18 Khronos provides a corresponding set of header files for applications using
38 Applications normally will include the header `{full_header}`.
137 Applications that do not make use of window system-specific extensions may
172 Applications should not use this value as their
174 Instead applications should explicitly select a specific fixed major/minor
229 Applications must: not define handles in a way that is not binary compatible
294 extensions, allowing applications to decide which ones they need to be
300 Before including these platform-specific Vulkan headers, applications must:
304 As a convenience for applications that do not need the flexibility of
308 Applications control which platform-specific headers are included by
[all …]
|
| D | VK_NV_low_latency2.adoc | 22 This extension gives applications timing suggestions on when to start the
25 Applications can accomplish this through the extension by calling
31 `apiext:VK_NV_low_latency` provides legacy support for applications that
37 1) How does Low Latency 2 work with applications that utilize device groups?
|
| /third_party/openssl/doc/man3/ |
| D | EVP_PKEY_set1_RSA.pod | 81 functions are deprecated. Applications should instead use
88 I<pkey> is freed. These macros are deprecated. Applications should instead read
96 These functions are deprecated. Applications should instead use the EVP_PKEY
98 then applications should use L<EVP_PKEY_get_params(3)> and other similar
107 are deprecated. Applications should instead use the EVP_PKEY directly where
109 applications should use L<EVP_PKEY_get_params(3)> and other similar functions.
130 function is deprecated. Applications should use providers instead of engines
136 error occurs. This function is deprecated. Applications should use providers
159 in order that applications can "free" the return value. However applications
176 Most applications wishing to know a key type will simply call
|
| /third_party/ltp/testcases/kernel/device-drivers/v4l/user_space/doc/spec/ |
| D | x1859.htm | 89 applications, for example video images, raw or sliced VBI data, RDS
93 reopening a device, applications should always negotiate a data format
97 applications can also just query the current selection.</P
146 multiple panel applications can access the same device concurrently to
166 >When applications omit the
211 applications must support the <CODE
252 by all drivers exchanging image data with applications.</P
263 conversion routine or library for integration into applications.</P
295 enumerate) seems useless, but there are applications serving as proxy
296 between drivers and the actual video applications for which this is
|
| D | r11680.htm | 167 captured or output, applications can request frame skipping or
190 >To get and set the streaming parameters applications call
385 >Set by drivers and applications, see <A
408 >Applications store here the desired frame
420 reset manually applications can just set this field to
444 unused, applications and drivers must set this field to zero.
445 Applications using this field should check the driver name and
460 >Applications set this field to the desired number
485 applications must set the array to zero.</TD
538 >Set by drivers and applications, see <A
[all …]
|
| /third_party/mesa3d/src/util/ |
| D | driconf_static.py | 73 self.applications = []
77 self.applications.append(Application(application))
144 const struct driconf_application *applications;
174 % for application in device.applications:
178 %if len(device.applications) > 0:
180 % for application in device.applications:
215 .num_applications = ${len(device.applications)},
216 % if len(device.applications) > 0:
217 .applications = ${device.cname}_applications,
|
| /third_party/EGL/extensions/NV/ |
| D | EGL_NV_stream_origin.txt | 50 applications will rarely have to worry about frame orientation.
52 However, in some cases consumer applications such as compositors
55 stream frames. This will allow applications to adjust the way they
58 Similarly, producer applications might need to adjust how rendering
131 implementation. Applications must coordinate what they are
156 implementation. Applications must coordinate what they are
180 implementation. Applications must coordinate what they are
252 EGL_DONT_CARE and applications must coordinate what they do.
264 applications do not need to worry about it.
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/chapters/VK_KHR_present_wait/ |
| D | present_wait.adoc | 8 Applications wanting to control the pacing of the application by monitoring
22 applications can discover when images were presented, but only
26 Providing a mechanism which allows applications to block, waiting for a
31 The `apiext:VK_KHR_present_wait` extension allows applications to tell the
|
| D | present_wait.txt | 8 Applications wanting to control the pacing of the application by monitoring
22 applications can discover when images were presented, but only
26 Providing a mechanism which allows applications to block, waiting for a
31 The `apiext:VK_KHR_present_wait` extension allows applications to tell the
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/EXT/ |
| D | GLX_EXT_buffer_age.txt | 47 applications about how the driver manages the set of front and
48 back buffers associated with a given surface to allow applications
59 This extension lets applications query the age of the back buffer
80 buffers may be recycled so it wasn't safe for applications to try
81 and reuse their contents. Now applications can keep track of all
100 elapsed since it was most recently defined. Applications can,
145 reset. In other words, applications can assume that no event
150 It is up to applications to track pixel ownership using data
227 boundary otherwise applications can't be absolutely sure of
|
| /third_party/openGLES/extensions/EXT/ |
| D | GLX_EXT_buffer_age.txt | 47 applications about how the driver manages the set of front and
48 back buffers associated with a given surface to allow applications
59 This extension lets applications query the age of the back buffer
80 buffers may be recycled so it wasn't safe for applications to try
81 and reuse their contents. Now applications can keep track of all
100 elapsed since it was most recently defined. Applications can,
145 reset. In other words, applications can assume that no event
150 It is up to applications to track pixel ownership using data
227 boundary otherwise applications can't be absolutely sure of
|
12345678910>>...150