| /third_party/skia/third_party/externals/swiftshader/third_party/subzero/src/ |
| H A D | IceInstX8632.h | 2944 /// ret would do just as well.
|
| H A D | IceInstX8664.h | 2843 /// ret would do just as well.
|
| /third_party/python/Lib/test/ |
| H A D | test_ipaddress.py | 27 # multiple problems get classified differently, that's OK - just
|
| H A D | test_pathlib.py | 2257 # just before we try to create it ourselves. We do it
|
| /third_party/python/ |
| H A D | Makefile.pre.in | 714 # problems by creating a dummy pybuilddir.txt just to allow interpreter
|
| /third_party/python/Lib/ |
| H A D | typing.py | 1042 Just as a TypeVar (type variable) is a placeholder for a single type,
|
| /third_party/selinux/libsepol/cil/src/ |
| H A D | cil_build_ast.c | 5354 /* we don't want the tree walker to walk the macro parameters (they were just handled above), so the subtree is deleted, and the next pointer of the in cil_gen_macro()
|
| /third_party/rust/crates/rust-openssl/openssl/src/ssl/ |
| H A D | mod.rs | 1643 /// Sets a callback which will be invoked just after the client's hello message is received.
|
| /third_party/spirv-tools/test/opt/loop_optimizations/ |
| H A D | loop_fission.cpp | 200 // register pressure functor which just returns false. in TEST_F()
|
| /third_party/spirv-tools/test/reduce/ |
| H A D | structured_loop_to_selection_test.cpp | 843 // there was a loop embedded in the continue target of the loop we have just in TEST()
|
| /third_party/vk-gl-cts/external/vulkancts/modules_no_buildgn/vulkan/spirv_assembly/ |
| H A D | vktSpvAsmTypeTests.cpp | 718 DE_ASSERT(0); // Not implemented. Don't add to here. Just use VulkanFeatures
|
| /third_party/vk-gl-cts/external/vulkancts/modules_no_buildgn/vulkan/texture/ |
| H A D | vktTextureMipmapTests.cpp | 2482 // This one just reuses the default device from the context.
|
| /third_party/wpa_supplicant/wpa_supplicant-2.9/src/crypto/ |
| H A D | tls_openssl.c | 298 /* Just ignore the errors, since stdout is disabled */ in _tls_show_errors()
|
| /third_party/wpa_supplicant/wpa_supplicant-2.9/src/rsn_supp/ |
| H A D | wpa.c | 299 * just added based on SAE authentication for the in wpa_supplicant_get_pmk()
|
| /third_party/vk-gl-cts/modules/gles2/functional/ |
| H A D | es2fClippingTests.cpp | 348 // \note[jarkko] Doesn't have to be accurate, just to detect some obviously bad cases
|
| /third_party/vk-gl-cts/modules/gles3/functional/ |
| H A D | es3fClippingTests.cpp | 351 // \note[jarkko] Doesn't have to be accurate, just to detect some obviously bad cases
|
| /third_party/wpa_supplicant/wpa_supplicant-2.9_standard/src/crypto/ |
| H A D | tls_openssl.c | 304 /* Just ignore the errors, since stdout is disabled */ in _tls_show_errors()
|
| /third_party/wpa_supplicant/wpa_supplicant-2.9/src/ap/ |
| H A D | ieee802_11.c | 4938 "Process pending EAPOL frame that was received from " MACSTR " just before association notification", in handle_assoc_cb()
|
| /third_party/skia/third_party/externals/angle2/src/libANGLE/renderer/d3d/d3d11/ |
| H A D | Renderer11.cpp | 590 // Don't error in this case- just don't use mDeviceContext1 or mDeviceContext3. in initialize()
|
| /third_party/node/doc/api/ |
| H A D | all.json | 103 "desc": "<p>Node.js uses statically linked libraries such as V8, libuv, and OpenSSL. All\naddons are required to link to V8 and may link to any of the other dependencies\nas well. Typically, this is as simple as including the appropriate\n<code>#include <...></code> statements (e.g. <code>#include <v8.h></code>) and <code>node-gyp</code> will locate\nthe appropriate headers automatically. However, there are a few caveats to be\naware of:</p>\n<ul>\n<li>\n<p>When <code>node-gyp</code> runs, it will detect the specific release version of Node.js\nand download either the full source tarball or just the headers. If the full\nsource is downloaded, addons will have complete access to the full set of\nNode.js dependencies. However, if only the Node.js headers are downloaded,\nthen only the symbols exported by Node.js will be available.</p>\n</li>\n<li>\n<p><code>node-gyp</code> can be run using the <code>--nodedir</code> flag pointing at a local Node.js\nsource image. Using this option, the addon will have access to the full set of\ndependencies.</p>\n</li>\n</ul>",
202 "desc": "<p>Node-API (formerly N-API) is an API for building native Addons. It is\nindependent from the underlying JavaScript runtime (for example, V8) and is\nmaintained as part of Node.js itself. This API will be Application Binary\nInterface (ABI) stable across versions of Node.js. It is intended to insulate\naddons from changes in the underlying JavaScript engine and allow modules\ncompiled for one major version to run on later major versions of Node.js without\nrecompilation. The <a href=\"https://nodejs.org/en/docs/guides/abi-stability/\">ABI Stability</a> guide provides a more in-depth explanation.</p>\n<p>Addons are built/packaged with the same approach/tools outlined in the section\ntitled <a href=\"addons.html\">C++ Addons</a>. The only difference is the set of APIs that are used by\nthe native code. Instead of using the V8 or <a href=\"https://github.com/nodejs/nan\">Native Abstractions for Node.js</a>\nAPIs, the functions available in Node-API are used.</p>\n<p>APIs exposed by Node-API are generally used to create and manipulate\nJavaScript values. Concepts and operations generally map to ideas specified\nin the ECMA-262 Language Specification. The APIs have the following\nproperties:</p>\n<ul>\n<li>All Node-API calls return a status code of type <code>napi_status</code>. This\nstatus indicates whether the API call succeeded or failed.</li>\n<li>The API's return value is passed via an out parameter.</li>\n<li>All JavaScript values are abstracted behind an opaque type named\n<code>napi_value</code>.</li>\n<li>In case of an error status code, additional information can be obtained\nusing <code>napi_get_last_error_info</code>. More information can be found in the error\nhandling section <a href=\"n-api.html#error-handling\">Error handling</a>.</li>\n</ul>\n<p>Node-API is a C API that ensures ABI stability across Node.js versions\nand different compiler levels. A C++ API can be easier to use.\nTo support using C++, the project maintains a\nC++ wrapper module called <a href=\"https://github.com/nodejs/node-addon-api\"><code>node-addon-api</code></a>.\nThis wrapper provides an inlinable C++ API. Binaries built\nwith <code>node-addon-api</code> will depend on the symbols for the Node-API C-based\nfunctions exported by Node.js. <code>node-addon-api</code> is a more\nefficient way to write code that calls Node-API. Take, for example, the\nfollowing <code>node-addon-api</code> code. The first section shows the\n<code>node-addon-api</code> code and the second section shows what actually gets\nused in the addon.</p>\n<pre><code class=\"language-cpp\">Object obj = Object::New(env);\nobj[\"foo\"] = String::New(env, \"bar\");\n</code></pre>\n<pre><code class=\"language-cpp\">napi_status status;\nnapi_value object, string;\nstatus = napi_create_object(env, &object);\nif (status != napi_ok) {\n napi_throw_error(env, ...);\n return;\n}\n\nstatus = napi_create_string_utf8(env, \"bar\", NAPI_AUTO_LENGTH, &string);\nif (status != napi_ok) {\n napi_throw_error(env, ...);\n return;\n}\n\nstatus = napi_set_named_property(env, object, \"foo\", string);\nif (status != napi_ok) {\n napi_throw_error(env, ...);\n return;\n}\n</code></pre>\n<p>The end result is that the addon only uses the exported C APIs. As a result,\nit still gets the benefits of the ABI stability provided by the C API.</p>\n<p>When using <code>node-addon-api</code> instead of the C APIs, start with the API <a href=\"https://github.com/nodejs/node-addon-api#api-documentation\">docs</a>\nfor <code>node-addon-api</code>.</p>\n<p>The <a href=\"https://nodejs.github.io/node-addon-examples/\">Node-API Resource</a> offers\nan excellent orientation and tips for developers just getting started with\nNode-API and <code>node-addon-api</code>. Additional media resources can be found on the\n<a href=\"https://github.com/nodejs/abi-stable-node/blob/HEAD/node-api-media.md\">Node-API Media</a> page.</p>",
276 "desc": "<p>In order to use the Node-API functions, include the file <a href=\"https://github.com/nodejs/node/blob/HEAD/src/node_api.h\"><code>node_api.h</code></a> which\nis located in the src directory in the node development tree:</p>\n<pre><code class=\"language-c\">#include <node_api.h>\n</code></pre>\n<p>This will opt into the default <code>NAPI_VERSION</code> for the given release of Node.js.\nIn order to ensure compatibility with specific versions of Node-API, the version\ncan be specified explicitly when including the header:</p>\n<pre><code class=\"language-c\">#define NAPI_VERSION 3\n#include <node_api.h>\n</code></pre>\n<p>This restricts the Node-API surface to just the functionality that was available\nin the specified (and earlier) versions.</p>\n<p>Some of the Node-API surface is experimental and requires explicit opt-in:</p>\n<pre><code class=\"language-c\">#define NAPI_EXPERIMENTAL\n#include <node_api.h>\n</code></pre>\n<p>In this case the entire API surface, including any experimental APIs, will be\navailable to the module code.</p>\n<p>Occasionally, experimental features are introduced that affect already-released\nand stable APIs. These features can be disabled by an opt-out:</p>\n<pre><code class=\"language-c\">#define NAPI_EXPERIMENTAL\n#define NODE_API_EXPERIMENTAL_<FEATURE_NAME>_OPT_OUT\n#include <node_api.h>\n</code></pre>\n<p>where <code><FEATURE_NAME></code> is the name of an experimental feature that affects both\nexperimental and stable APIs.</p>",
1441 "desc": "<pre><code class=\"language-c\">napi_status napi_create_external(napi_env env,\n void* data,\n napi_finalize finalize_cb,\n void* finalize_hint,\n napi_value* result)\n</code></pre>\n<ul>\n<li><code>[in] env</code>: The environment that the API is invoked under.</li>\n<li><code>[in] data</code>: Raw pointer to the external data.</li>\n<li><code>[in] finalize_cb</code>: Optional callback to call when the external value is being\ncollected. <a href=\"n-api.html#napi_finalize\"><code>napi_finalize</code></a> provides more details.</li>\n<li><code>[in] finalize_hint</code>: Optional hint to pass to the finalize callback during\ncollection.</li>\n<li><code>[out] result</code>: A <code>napi_value</code> representing an external value.</li>\n</ul>\n<p>Returns <code>napi_ok</code> if the API succeeded.</p>\n<p>This API allocates a JavaScript value with external data attached to it. This\nis used to pass external data through JavaScript code, so it can be retrieved\nlater by native code using <a href=\"n-api.html#napi_get_value_external\"><code>napi_get_value_external</code></a>.</p>\n<p>The API adds a <code>napi_finalize</code> callback which will be called when the JavaScript\nobject just created has been garbage collected.</p>\n<p>The created value is not an object, and therefore does not support additional\nproperties. It is considered a distinct value type: calling <code>napi_typeof()</code> with\nan external value yields <code>napi_external</code>.</p>",
1457 "desc": "<pre><code class=\"language-c\">napi_status\nnapi_create_external_arraybuffer(napi_env env,\n void* external_data,\n size_t byte_length,\n napi_finalize finalize_cb,\n void* finalize_hint,\n napi_value* result)\n</code></pre>\n<ul>\n<li><code>[in] env</code>: The environment that the API is invoked under.</li>\n<li><code>[in] external_data</code>: Pointer to the underlying byte buffer of the\n<code>ArrayBuffer</code>.</li>\n<li><code>[in] byte_length</code>: The length in bytes of the underlying buffer.</li>\n<li><code>[in] finalize_cb</code>: Optional callback to call when the <code>ArrayBuffer</code> is being\ncollected. <a href=\"n-api.html#napi_finalize\"><code>napi_finalize</code></a> provides more details.</li>\n<li><code>[in] finalize_hint</code>: Optional hint to pass to the finalize callback during\ncollection.</li>\n<li><code>[out] result</code>: A <code>napi_value</code> representing a JavaScript <code>ArrayBuffer</code>.</li>\n</ul>\n<p>Returns <code>napi_ok</code> if the API succeeded.</p>\n<p><strong>Some runtimes other than Node.js have dropped support for external buffers</strong>.\nOn runtimes other than Node.js this method may return\n<code>napi_no_external_buffers_allowed</code> to indicate that external\nbuffers are not supported. One such runtime is Electron as\ndescribed in this issue\n<a href=\"https://github.com/electron/electron/issues/35801\">electron/issues/35801</a>.</p>\n<p>In order to maintain broadest compatibility with all runtimes\nyou may define <code>NODE_API_NO_EXTERNAL_BUFFERS_ALLOWED</code> in your addon before\nincludes for the node-api headers. Doing so will hide the 2 functions\nthat create external buffers. This will ensure a compilation error\noccurs if you accidentally use one of these methods.</p>\n<p>This API returns a Node-API value corresponding to a JavaScript <code>ArrayBuffer</code>.\nThe underlying byte buffer of the <code>ArrayBuffer</code> is externally allocated and\nmanaged. The caller must ensure that the byte buffer remains valid until the\nfinalize callback is called.</p>\n<p>The API adds a <code>napi_finalize</code> callback which will be called when the JavaScript\nobject just created has been garbage collected.</p>\n<p>JavaScript <code>ArrayBuffer</code>s are described in\n<a href=\"https://tc39.github.io/ecma262/#sec-arraybuffer-objects\">Section 24.1</a> of the ECMAScript Language Specification.</p>",
1473 "desc": "<pre><code class=\"language-c\">napi_status napi_create_external_buffer(napi_env env,\n size_t length,\n void* data,\n napi_finalize finalize_cb,\n void* finalize_hint,\n napi_value* result)\n</code></pre>\n<ul>\n<li><code>[in] env</code>: The environment that the API is invoked under.</li>\n<li><code>[in] length</code>: Size in bytes of the input buffer (should be the same as the\nsize of the new buffer).</li>\n<li><code>[in] data</code>: Raw pointer to the underlying buffer to expose to JavaScript.</li>\n<li><code>[in] finalize_cb</code>: Optional callback to call when the <code>ArrayBuffer</code> is being\ncollected. <a href=\"n-api.html#napi_finalize\"><code>napi_finalize</code></a> provides more details.</li>\n<li><code>[in] finalize_hint</code>: Optional hint to pass to the finalize callback during\ncollection.</li>\n<li><code>[out] result</code>: A <code>napi_value</code> representing a <code>node::Buffer</code>.</li>\n</ul>\n<p>Returns <code>napi_ok</code> if the API succeeded.</p>\n<p><strong>Some runtimes other than Node.js have dropped support for external buffers</strong>.\nOn runtimes other than Node.js this method may return\n<code>napi_no_external_buffers_allowed</code> to indicate that external\nbuffers are not supported. One such runtime is Electron as\ndescribed in this issue\n<a href=\"https://github.com/electron/electron/issues/35801\">electron/issues/35801</a>.</p>\n<p>In order to maintain broadest compatibility with all runtimes\nyou may define <code>NODE_API_NO_EXTERNAL_BUFFERS_ALLOWED</code> in your addon before\nincludes for the node-api headers. Doing so will hide the 2 functions\nthat create external buffers. This will ensure a compilation error\noccurs if you accidentally use one of these methods.</p>\n<p>This API allocates a <code>node::Buffer</code> object and initializes it with data\nbacked by the passed in buffer. While this is still a fully-supported data\nstructure, in most cases using a <code>TypedArray</code> will suffice.</p>\n<p>The API adds a <code>napi_finalize</code> callback which will be called when the JavaScript\nobject just created has been garbage collected.</p>\n<p>For Node.js >=4 <code>Buffers</code> are <code>Uint8Array</code>s.</p>",
5789 "desc": "<p><em><a href=\"https://github.com/nodejs/corepack\">Corepack</a></em> is an experimental tool to help with\nmanaging versions of your package managers. It exposes binary proxies for\neach <a href=\"corepack.html#supported-package-managers\">supported package manager</a> that, when called, will identify whatever\npackage manager is configured for the current project, transparently install\nit if needed, and finally run it without requiring explicit user interactions.</p>\n<p>This feature simplifies two core workflows:</p>\n<ul>\n<li>\n<p>It eases new contributor onboarding, since they won't have to follow\nsystem-specific installation processes anymore just to have the package\nmanager you want them to.</p>\n</li>\n<li>\n<p>It allows you to ensure that everyone in your team will use exactly the\npackage manager version you intend them to, without them having to\nmanually synchronize it each time you need to make an update.</p>\n</li>\n</ul>",
9177 "desc": "<p>Type: Documentation-only</p>\n<p><a href=\"net.html#socketbuffersize\"><code>socket.bufferSize</code></a> is just an alias for <a href=\"stream.html#writablewritablelength\"><code>writable.writableLength</code></a>.</p>",
14155 "desc": "<p>To control how ICU is used in Node.js, four <code>configure</code> options are available\nduring compilation. Additional details on how to compile Node.js are documented\nin <a href=\"https://github.com/nodejs/node/blob/HEAD/BUILDING.md\">BUILDING.md</a>.</p>\n<ul>\n<li><code>--with-intl=none</code>/<code>--without-intl</code></li>\n<li><code>--with-intl=system-icu</code></li>\n<li><code>--with-intl=small-icu</code></li>\n<li><code>--with-intl=full-icu</code> (default)</li>\n</ul>\n<p>An overview of available Node.js and JavaScript features for each <code>configure</code>\noption:</p>\n<table>\n<thead>\n<tr>\n<th>Feature</th>\n<th><code>none</code></th>\n<th><code>system-icu</code></th>\n<th><code>small-icu</code></th>\n<th><code>full-icu</code></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><a href=\"https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/normalize\"><code>String.prototype.normalize()</code></a></td>\n<td>none (function is no-op)</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n<tr>\n<td><code>String.prototype.to*Case()</code></td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl\"><code>Intl</code></a></td>\n<td>none (object does not exist)</td>\n<td>partial/full (depends on OS)</td>\n<td>partial (English-only)</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/localeCompare\"><code>String.prototype.localeCompare()</code></a></td>\n<td>partial (not locale-aware)</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n<tr>\n<td><code>String.prototype.toLocale*Case()</code></td>\n<td>partial (not locale-aware)</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/toLocaleString\"><code>Number.prototype.toLocaleString()</code></a></td>\n<td>partial (not locale-aware)</td>\n<td>partial/full (depends on OS)</td>\n<td>partial (English-only)</td>\n<td>full</td>\n</tr>\n<tr>\n<td><code>Date.prototype.toLocale*String()</code></td>\n<td>partial (not locale-aware)</td>\n<td>partial/full (depends on OS)</td>\n<td>partial (English-only)</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"url.html#legacy-url-api\">Legacy URL Parser</a></td>\n<td>partial (no IDN support)</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"url.html#the-whatwg-url-api\">WHATWG URL Parser</a></td>\n<td>partial (no IDN support)</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"buffer.html#buffertranscodesource-fromenc-toenc\"><code>require('node:buffer').transcode()</code></a></td>\n<td>none (function does not exist)</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"repl.html#repl\">REPL</a></td>\n<td>partial (inaccurate line editing)</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"util.html#class-utiltextdecoder\"><code>require('node:util').TextDecoder</code></a></td>\n<td>partial (basic encodings support)</td>\n<td>partial/full (depends on OS)</td>\n<td>partial (Unicode-only)</td>\n<td>full</td>\n</tr>\n<tr>\n<td><a href=\"https://github.com/tc39/proposal-regexp-unicode-property-escapes\"><code>RegExp</code> Unicode Property Escapes</a></td>\n<td>none (invalid <code>RegExp</code> error)</td>\n<td>full</td>\n<td>full</td>\n<td>full</td>\n</tr>\n</tbody>\n</table>\n<p>The \"(not locale-aware)\" designation denotes that the function carries out its\noperation just like the non-<code>Locale</code> version of the function, if one\nexists. For example, under <code>none</code> mode, <code>Date.prototype.toLocaleString()</code>'s\noperation is identical to that of <code>Date.prototype.toString()</code>.</p>",
[all...] |
| /third_party/glslang/glslang/MachineIndependent/ |
| H A D | glslang_tab.cpp | 4800 case, just report a simple "syntax error".
4801 - Don't assume there isn't a lookahead just because this state is a
5014 have just been pushed. So pushing a state here evens the stacks. */
5047 conditional around just the two extra args, but that might
12528 /* If just tried and failed to reuse lookahead token after an
|
| /third_party/vk-gl-cts/external/openglcts/modules/gl/ |
| H A D | gl4cEnhancedLayoutsTests.cpp | 4223 * @return Pointer to just created member
4290 * @return Pointer to just created member
4312 * @return Pointer to just created member
18975 /* Just get the highest valid component for goten and in test()
19558 /* Just get the highest valid component for goten and in test()
|
| /third_party/mksh/ |
| H A D | check.t | 144 Just output the environment variables set (always fails)
6083 lines, not just the first.
7899 Check that ERR and EXIT traps are run just like GNU bash does.
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/chapters/ |
| H A D | resources.adoc | 4471 * Descriptors referring just to the depth aspect of a depth/stencil image
4476 * Descriptors referring just to the stencil aspect of a depth/stencil
9671 ownership transfer, in the same way as for a resource that was just created;
|
| /device/soc/hisilicon/hi3516dv300/ |
| H A D | NOTICE | 3 Please note we provide an open source software notice for the third party open source software along with this software and/or this software component (in the following just “this SOFTWARE”). The open source software licenses are granted by the respective right holders.
|