| /external/ltp/testcases/kernel/syscalls/openat2/ |
| D | openat201.c | 13 static struct open_how *how; variable
24 struct open_how **how; member
27 {&dir_fd, TEST_FILE, O_RDWR, S_IRWXU, 0, &how, sizeof(*how)},
28 {&dir_fd, TEST_FILE, O_RDONLY, S_IRUSR, 0, &how, sizeof(*how)},
29 {&dir_fd, TEST_FILE, O_WRONLY, S_IWUSR, 0, &how, sizeof(*how)},
30 {&dir_fd, TEST_FILE, O_RDWR, S_IRWXU, RESOLVE_NO_XDEV, &how, sizeof(*how)},
31 {&dir_fd, TEST_FILE, O_RDWR, S_IRWXU, RESOLVE_NO_MAGICLINKS, &how, sizeof(*how)},
32 {&dir_fd, TEST_FILE, O_RDWR, S_IRWXU, RESOLVE_NO_SYMLINKS, &how, sizeof(*how)},
33 {&dir_fd, TEST_FILE, O_RDWR, S_IRWXU, RESOLVE_BENEATH, &how, sizeof(*how)},
34 {&dir_fd, TEST_FILE, O_RDWR, S_IRWXU, RESOLVE_IN_ROOT, &how, sizeof(*how)},
[all …]
|
| D | openat203.c | 12 static struct open_how *how; variable
22 struct open_how **how; member
26 {"invalid-dfd", -1, TEST_FILE, O_RDWR | O_CREAT, S_IRWXU, 0, &how, sizeof(*how), EBADF},
27 {"invalid-pathname", AT_FDCWD, NULL, O_RDONLY | O_CREAT, S_IRUSR, 0, &how, sizeof(*how), EFAULT},
28 {"invalid-flags", AT_FDCWD, TEST_FILE, O_RDONLY, S_IWUSR, 0, &how, sizeof(*how), EINVAL},
29 {"invalid-mode", AT_FDCWD, TEST_FILE, O_RDWR | O_CREAT, -1, 0, &how, sizeof(*how), EINVAL},
30 …{"invalid-resolve", AT_FDCWD, TEST_FILE, O_RDWR | O_CREAT, S_IRWXU, -1, &how, sizeof(*how), EINVAL…
31 {"invalid-size-zero", AT_FDCWD, TEST_FILE, O_RDWR | O_CREAT, S_IRWXU, 0, &how, 0, EINVAL},
32 …{"invalid-size-small", AT_FDCWD, TEST_FILE, O_RDWR | O_CREAT, S_IRWXU, 0, &how, sizeof(*how) - 1, …
33 …{"invalid-size-big", AT_FDCWD, TEST_FILE, O_RDWR | O_CREAT, S_IRWXU, 0, &how, sizeof(*how) + 1, EF…
[all …]
|
| D | openat202.c | 12 static struct open_how *how; variable
44 how->flags = O_RDONLY | O_CREAT; in run()
45 how->mode = S_IRUSR; in run()
46 how->resolve = tc->resolve; in run()
48 TEST(openat2(AT_FDCWD, tc->pathname, how, sizeof(*how))); in run()
84 {&how, .size = sizeof(*how)},
|
| /external/linux-kselftest/tools/testing/selftests/openat2/ |
| D | openat2_test.c | 158 struct open_how how; member
169 .how.flags = O_TMPFILE | O_PATH | O_RDWR, .err = -EINVAL }, in test_openat2_flags()
171 .how.flags = O_TMPFILE | O_CREAT | O_RDWR, .err = -EINVAL }, in test_openat2_flags()
175 .how.flags = O_PATH | O_CLOEXEC }, in test_openat2_flags()
177 .how.flags = O_PATH | O_DIRECTORY }, in test_openat2_flags()
179 .how.flags = O_PATH | O_NOFOLLOW }, in test_openat2_flags()
182 .how.flags = O_PATH | O_RDWR, .err = -EINVAL }, in test_openat2_flags()
184 .how.flags = O_PATH | O_CREAT, .err = -EINVAL }, in test_openat2_flags()
186 .how.flags = O_PATH | O_EXCL, .err = -EINVAL }, in test_openat2_flags()
188 .how.flags = O_PATH | O_NOCTTY, .err = -EINVAL }, in test_openat2_flags()
[all …]
|
| D | resolve_test.c | 113 struct open_how how; member
139 .path = "/", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
142 .path = "cheeky/absself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
145 .path = "abscheeky/absself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
148 .path = "..", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
151 .path = "../root/", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
154 .path = "cheeky/self", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
157 .path = "abscheeky/self", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
160 .path = "cheeky/garbageself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
163 .path = "abscheeky/garbageself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests()
[all …]
|
| D | helpers.c | 17 bool needs_openat2(const struct open_how *how) in needs_openat2() argument
19 return how->resolve != 0; in needs_openat2()
22 int raw_openat2(int dfd, const char *path, void *how, size_t size) in raw_openat2() argument
24 int ret = syscall(__NR_openat2, dfd, path, how, size); in raw_openat2()
28 int sys_openat2(int dfd, const char *path, struct open_how *how) in sys_openat2() argument
30 return raw_openat2(dfd, path, how, sizeof(*how)); in sys_openat2()
33 int sys_openat(int dfd, const char *path, struct open_how *how) in sys_openat() argument
35 int ret = openat(dfd, path, how->flags, how->mode); in sys_openat()
98 struct open_how how = {}; in init() local
104 fd = sys_openat2(AT_FDCWD, ".", &how); in init()
|
| /external/sdv/vsomeip/third_party/boost/numeric/odeint/doc/ |
| D | examples_table.qbk | 19 [This examples shows how member functions can be used as system functions in odeint.]]
22 …[This examples shows how member functions can be used as system functions in odeint with `std::bin…
34 [The Fermi-Pasta-Ulam (FPU) example shows how odeint can be used to integrate lattice systems.]]
37 [Shows skeletal code on how to implement own factory functions.]]
43 [This examples shows how __boost_units can be used with odeint.]]
46 …[The Heun example shows how an custom Runge-Kutta stepper can be created with odeint generic Runge…
55 [Simple example showing how to get odeint to work with a self-defined vector type.]]
58 …[The phase oscillator ensemble example shows how globally coupled oscillators can be analyzed and …
79 [The Stuart-Landau example shows how odeint can be used with complex state types.]]
82 …[The 2D phase oscillator example shows how a two-dimensional lattice works with odeint and how mat…
[all …]
|
| /external/python/python-api-core/google/api_core/future/ |
| D | polling.py | 72 documentation for that method for details on how polling works.
81 This parameter controls how often :meth:`done` is polled. If the
107 retry (google.api_core.retry.Retry): (Optional) How to retry the
150 how this method operates, just call it with ``result(timeout=X)``. The
176 ``retry`` (google.api_core.retry.Retry): (Optional) How to retry the
179 This parameter defines ONLY how the polling RPC call is retried
181 does NOT define how the polling is done (i.e. how frequently and for
182 how long to call the polling RPC); use the ``polling`` parameter for that.
188 ``polling`` (google.api_core.retry.Retry): (Optional) How often and
189 for how long to call the polling RPC periodically (i.e. what to do if
[all …]
|
| /external/federated-compute/fcp/client/ |
| D | histogram_counters.proto | 34 * How long it takes to run a plan on device, excluding downloading the plan
46 /** How long running a "restore state op" takes. */
50 * How long it takes to run training for a whole client execution (which may
56 /** How long running an "init op" takes. */
59 /** How long running a "before op" takes. */
62 /** How long running an "after op" takes. */
66 * How long it takes to run training for a whole epoch. This includes
73 * How long it takes to gather enough examples for a mini batch.
79 * How long it takes to run training on a mini batch.
85 * How long it takes the TensorFlow session to terminate after it's been
[all …]
|
| /external/coreboot/Documentation/contributing/ |
| D | documentation_ideas.md | 27 section should include guidelines on how to build coreboot, how to flash coreboot
32 include how to get started developing coreboot, explaining the basic concepts of
33 coreboot and also give guideance on how to proceed after the first steps.
49 * Understanding on how a different groups of users might use the documentation area
50 * Basic understanding of how coreboot works (Can be worked out _on-the-fly_)
59 as enduser, are guides and how-to's. There are already some guides which need
67 For developers, how to debug coreboot and various debugging techniques need
71 * Knowledge of virtual machines, how to install different OSs and set up the
79 ## How to Support a New Board
85 exists. There should be a 'how-to' guide for this. Also what are common problems
[all …]
|
| /external/perfetto/protos/perfetto/metrics/android/ |
| D | android_garbage_collection_stats.proto | 35 // how much allocation activity is going on during the trace.
41 // Overall heap utilization. This gives a sense of how aggressive GC is
49 // A measure of how efficient GC is with respect to cpu, independent of how
57 // the trace. This gives a sense of how much potential interference there
60 // A measure of how efficient GC is with regards to gc during application
61 // startup, independent of how aggressively GC is tuned. Larger values
78 // how much allocation activity is going on during the trace.
84 // Overall heap utilization. This gives a sense of how aggressive GC is
92 // A measure of how efficient GC is with respect to cpu, independent of how
103 // the trace. This gives a sense of how much potential interference there
[all …]
|
| /external/capstone/tests/ |
| D | README | 1 This directory contains some test code to show how to use Capstone API.
9 This code shows how to access to architecture-neutral information in disassembled
14 This code shows how to use SKIPDATA option to skip broken instructions (most likely
19 This code shows how to use the API cs_disasm_iter() to decode one instruction at
23 This code shows how to use MNEMONIC option to customize instruction mnemonic
24 at run-time, and then how to reset the engine to use the default mnemonic.
27 These code show how to access architecture-specific information for each
31 This code shows how to use Capstone from a Windows driver.
|
| /external/hamcrest/hamcrest-library/src/test/java/org/hamcrest/text/ |
| D | IsEqualIgnoringWhiteSpaceTest.java | 12 … private final Matcher<String> matcher = equalToIgnoringWhiteSpace("Hello World how\n are we? ");
20 assertThat("Hello World how are we?", matcher); in testPassesIfWordsAreSameButWhitespaceDiffers()
21 assertThat(" Hello World how are \n\n\twe?", matcher); in testPassesIfWordsAreSameButWhitespaceDiffers()
25 assertThat("Hello PLANET how are we?", not(matcher)); in testFailsIfTextOtherThanWhitespaceDiffers()
26 assertThat("Hello World how are we", not(matcher)); in testFailsIfTextOtherThanWhitespaceDiffers()
30 assertThat("HelloWorld how are we?", not(matcher)); in testFailsIfWhitespaceIsAddedOrRemovedInMidWord()
31 assertThat("Hello Wo rld how are we?", not(matcher)); in testFailsIfWhitespaceIsAddedOrRemovedInMidWord()
48 assertDescription("equalToIgnoringWhiteSpace(\"Hello World how\\n are we? \")", in testHasAReadableDescription()
|
| /external/sdv/vsomeip/third_party/boost/asio/doc/ |
| D | examples.qbk | 32 This example shows how to customise the allocation of memory associated with
40 This example demonstrates how to create reference counted buffers that can be
55 The following POSIX-specific chat client demonstrates how to use the
77 These POSIX-specific examples show how to use Boost.Asio in conjunction with the
83 The second example demonstrates how it is possible to fork a process from
91 Example programs implementing simple HTTP 1.0 clients. These examples show how
102 implementation of HTTP 1.0. It demonstrates how to perform a clean shutdown by
189 This example shows how to use raw sockets with ICMP to ping a remote host.
198 This example shows how to customise handler invocation. Completion handlers are
206 Two examples showing how to use [link boost_asio.reference.ip__tcp.iostream
[all …]
|
| /external/flatbuffers/docs-old/source/ |
| D | FlatBuffers.md | 38 write and what data you don't, and how you design data structures.
94 explaining how it speeds up loading their posts.
100 This section is a quick rundown of how to use this system. Subsequent
127 - How to [build the compiler](@ref flatbuffers_guide_building) and samples on
129 - How to [use the compiler](@ref flatbuffers_guide_using_schema_compiler).
130 - How to [write a schema](@ref flatbuffers_guide_writing_schema).
131 - How to [use the generated C++ code](@ref flatbuffers_guide_use_cpp) in your
133 - How to [use the generated Java code](@ref flatbuffers_guide_use_java)
135 - How to [use the generated C# code](@ref flatbuffers_guide_use_c-sharp)
137 - How to [use the generated Kotlin code](@ref flatbuffers_guide_use_kotlin)
[all …]
|
| /external/clang/www/analyzer/ |
| D | faq.html | 5 <title>FAQ and How to Deal with Common False Positives</title>
20 <h1>FAQ and How to Deal with Common False Positives</h1>
23 <li><a href="#custom_assert">How do I tell the analyzer that I do not want the bug being
27 pointer is never null. How can I tell the analyzer that a pointer can never be
29 …<li><a href="#dead_store">How do I tell the static analyzer that I don't care about a specific dea…
30 …<li><a href="#unused_ivar">How do I tell the static analyzer that I don't care about a specific un…
31 …<li><a href="#unlocalized_string">How do I tell the static analyzer that I don't care about a spec…
32 …<li><a href="#use_assert">The analyzer assumes that a loop body is never entered. How can I tell …
33 <li><a href="#suppress_issue">How can I suppress a specific analyzer warning?</a></li>
34 <li><a href="#exclude_code">How can I selectively exclude code the analyzer examines?</a></li>
[all …]
|
| /external/libwebsockets/minimal-examples/raw/ |
| D | README.md | 3 minimal-raw-adopt-tcp|Shows how to have lws adopt an existing tcp socket something else had connect…
4 minimal-raw-adopt-udp|Shows how to create a udp socket and read and write on it
5 minimal-raw-fallback-http|Shows how to run a normal http(s) server that falls back to a specified r…
6 minimal-raw-file|Shows how to adopt a file descriptor (device node, fifo, file, etc) into the lws e…
8 minimal-raw-proxy-fallback|Shows how to run a normal http(s) server that falls back to a proxied co…
9 minimal-raw-proxy|Shows how to set up a vhost so it listens for connections and proxies them to a s…
10 minimal-raw-vhost|Shows how to set up a vhost that listens and accepts RAW socket connections
|
| /external/sdv/vsomeip/third_party/boost/utility/doc/ |
| D | Jamfile.v2 | 52 # How far down we chunk nested sections, basically all of them:
56 # How far down sections get TOC's
60 # How far down we go with TOC's
71 # How far down we chunk nested sections, basically all of them:
75 # How far down sections get TOC's
79 # How far down we go with TOC's
90 # How far down we chunk nested sections, basically all of them:
94 # How far down sections get TOC's
98 # How far down we go with TOC's
109 # How far down we chunk nested sections, basically all of them:
[all …]
|
| /external/cronet/stable/third_party/icu/source/samples/ |
| D | readme.txt | 10 break - demonstrates how to use BreakIterators in C and C++.
14 case - demonstrates how to do Unicode case conversion in C and C++.
16 coll - shows how collation compares strings
22 datecal - demonstrates how a calendar object provides information
26 dtitvfmtsample - shows how date interval format uses predefined skeletons
42 strsrch - demonstrates how to search for patterns in Unicode text using the usearch interface.
46 uciter8 - demonstrates how to leniently read 8-bit Unicode text.
72 * How do I build the samples?
|
| /external/cronet/tot/third_party/icu/source/samples/ |
| D | readme.txt | 10 break - demonstrates how to use BreakIterators in C and C++.
14 case - demonstrates how to do Unicode case conversion in C and C++.
16 coll - shows how collation compares strings
22 datecal - demonstrates how a calendar object provides information
26 dtitvfmtsample - shows how date interval format uses predefined skeletons
42 strsrch - demonstrates how to search for patterns in Unicode text using the usearch interface.
46 uciter8 - demonstrates how to leniently read 8-bit Unicode text.
72 * How do I build the samples?
|
| /external/gemmlowp/doc/ |
| D | quantization.md | 13 perform, specifically, it affects how one goes from internal 32bit accumulator
23 In the present document, our purpose is to show how, reasoning from first
25 naturally at some specific quantization paradigm, and how that can be
28 We also aim to show how that differs from the older, legacy quantization
133 how to eliminate all usage of floating-point arithmetic. That will come
138 Now that we know — equation (3) — how real numbers are to correspond
182 matrix multiplication should do, i.e. how to compute `result_quantized_value`.
202 Equation (5) is the conclusion of this general discussion of how to specify what
227 It is out of scope of the present doc to discuss how to avoid the overhead of
263 So how do we implement the multiplication of a int32 value by a positive real
[all …]
|
| /external/googleapis/google/cloud/audit/ |
| D | bigquery_audit_metadata.proto | 37 // Describes how the job was inserted.
52 // Describes how the job was inserted.
70 // Describes how the job was deleted.
84 // Describes how the job was deleted.
90 // Describes how the dataset was created.
105 // Describes how the dataset was created.
117 // Describes how the dataset was changed.
135 // Describes how the dataset was changed.
147 // Describes how the dataset was deleted.
159 // Describes how the dataset was deleted.
[all …]
|
| /external/pigweed/docs/contributing/docs/ |
| D | index.rst | 15 How to do common tasks related to authoring ``pigweed.dev`` content
23 How to structure and write docs for Pigweed modules.
32 Style guide for writing conventions such as how to capitalize titles.
39 How to format reStructuredText, the main markup language for
49 How to format the C++ code comments that are transformed
57 Information about how the ``pigweed.dev`` website is generated.
66 How to use the semi-automation tool to create a new bi-weekly update
|
| /external/python/google-api-python-client/docs/dyn/ |
| D | healthcare_v1beta1.projects.locations.datasets.dicomStores.studies.html | 87 …r samples that show how to call DeleteStudy, see [Deleting a study, series, or instance](https://c…
90 …. For samples that show how to call RetrieveStudyMetadata, see [Retrieving metadata](https://cloud…
93 …ent. For samples that show how to call RetrieveStudy, see [Retrieving DICOM data](https://cloud.go…
96 …hat show how to call SearchForInstances, see [Searching for studies, series, instances, and frames…
99 …that show how to call SearchForSeries, see [Searching for studies, series, instances, and frames](…
102 …ment. For samples that show how to call StoreInstances, see [Storing DICOM data](https://cloud.goo…
111 …r samples that show how to call DeleteStudy, see [Deleting a study, series, or instance](https://c…
126 …ssage, and error details. You can find out more about this error model and how to work with it in …
147 …. For samples that show how to call RetrieveStudyMetadata, see [Retrieving metadata](https://cloud…
160 …ody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and res…
[all …]
|
| D | healthcare_v1.projects.locations.datasets.dicomStores.studies.html | 87 …r samples that show how to call DeleteStudy, see [Deleting a study, series, or instance](https://c…
90 …. For samples that show how to call RetrieveStudyMetadata, see [Retrieving metadata](https://cloud…
93 …ent. For samples that show how to call RetrieveStudy, see [Retrieving DICOM data](https://cloud.go…
96 …hat show how to call SearchForInstances, see [Searching for studies, series, instances, and frames…
99 …that show how to call SearchForSeries, see [Searching for studies, series, instances, and frames](…
102 …ment. For samples that show how to call StoreInstances, see [Storing DICOM data](https://cloud.goo…
111 …r samples that show how to call DeleteStudy, see [Deleting a study, series, or instance](https://c…
126 …ssage, and error details. You can find out more about this error model and how to work with it in …
147 …. For samples that show how to call RetrieveStudyMetadata, see [Retrieving metadata](https://cloud…
160 …ody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and res…
[all …]
|