Home
last modified time | relevance | path

Searched full:would (Results 1 – 25 of 13788) sorted by relevance

12345678910>>...552

/external/openthread/tests/scripts/thread-cert/
Dv1_2_test_multicast_registration.py69 …a) add MA1_LINKLOCAL which would NOT be registered in AddressRegistrationTLV of Child Update Reque…
70 … b) add MA2_ADMINSCOPE which would be registered in AddressRegistrationTLV of Child Update Request.
73 a) add MA1_LINKLOCAL which would be registered in AddressRegistrationTLV of Child Update Request
74 … b) add MA2_ADMINSCOPE which would be registered in AddressRegistrationTLV of Child Update Request.
77 …a) add MA1_LINKLOCAL which would NOT be registered in AddressRegistrationTLV of Child Update Reque…
78 …b) add MA2_ADMINSCOPE which would NOT be registered in AddressRegistrationTLV of Child Update Requ…
81 a) add MA1_LINKLOCAL which would be registered in AddressRegistrationTLV of Child Update Request
82 … b) add MA2_ADMINSCOPE which would be registered in AddressRegistrationTLV of Child Update Request.
87 …a) add MA1_LINKLOCAL which would NOT be registered in AddressRegistrationTLV of Child Update Reque…
88 …b) add MA2_ADMINSCOPE which would NOT be registered in AddressRegistrationTLV of Child Update Requ…
[all …]
/external/cronet/third_party/protobuf/csharp/src/Google.Protobuf/
DCodedOutputStream.ComputeSize.cs50 /// Computes the number of bytes that would be needed to encode a
59 /// Computes the number of bytes that would be needed to encode a
68 /// Computes the number of bytes that would be needed to encode a
77 /// Computes the number of bytes that would be needed to encode an
86 /// Computes the number of bytes that would be needed to encode an
103 /// Computes the number of bytes that would be needed to encode a
112 /// Computes the number of bytes that would be needed to encode a
121 /// Computes the number of bytes that would be needed to encode a
130 /// Computes the number of bytes that would be needed to encode a
140 /// Computes the number of bytes that would be needed to encode a
[all …]
/external/protobuf/csharp/src/Google.Protobuf/
DCodedOutputStream.ComputeSize.cs50 /// Computes the number of bytes that would be needed to encode a
59 /// Computes the number of bytes that would be needed to encode a
68 /// Computes the number of bytes that would be needed to encode a
77 /// Computes the number of bytes that would be needed to encode an
86 /// Computes the number of bytes that would be needed to encode an
103 /// Computes the number of bytes that would be needed to encode a
112 /// Computes the number of bytes that would be needed to encode a
121 /// Computes the number of bytes that would be needed to encode a
130 /// Computes the number of bytes that would be needed to encode a
140 /// Computes the number of bytes that would be needed to encode a
[all …]
/external/python/cffi/doc/misc/
Dgrant-cffi-1.0.rst53 invocations would be moved to a separate Python source file. Running
54 that Python file would produce a dynamically-linked library. There
55 would be no caching logic involved; you would need to run it
59 When distributed, the same file would be run (once) during
64 A major difference with the existing verify() approach would be that
65 the ``.so/.dll/.dylib`` file would not be immediately loaded into the
66 process; you would load it only from the installed program at
71 Additionally, this would solve another issue: every import of a large
76 proposed change, all the cdef() code would be pre-parsed and stored in
77 the dynamically-linked library, and no CRC would be needed. This
[all …]
Ddesign.rst11 for integer correspondance you would use ``signed char`` or ``unsigned
17 ``ffi.new("long", 42)`` to resolve the ambiguity. Floats would be
21 but passing an integer not. I would fix this once and for all by
23 The possibly acceptable exception would be None (for ``NULL``).
32 * It would be possible to add a debug mode: when we cast ``struct foo``
33 to ``struct foo *`` or store it in some other struct, then we would
37 ctypes, which in these cases would store a strong reference and
/external/llvm/docs/HistoricalNotes/
D2000-12-06-MeetingSummary.txt14 * A two dimensional namespace would be valuable when doing alias
19 * Including this information would require that all users of the LLVM
20 bytecode would have to parse and handle it. This would slow down the
26 reconstructed from SSA form in linear time, that it would be an
30 would not affect the runtime of the optimization in a significant
31 way. Additionally, this would be an unlikely optimization to do at
45 2. Including loop header and body information. This would facilitate
67 stream. The obvious benefit would be for compatibility, the drawback
68 is that it would tend to splinter that 'standard' LLVM definition.
76 A. Using 16 or 32 bit numbers, which would be 'big enough'
D2000-11-18-EarlyDesignIdeasResp.txt20 certifying a register based language as safe at run time would be a
21 pretty expensive operation to have to do. Additionally, we would like
38 the trusted compiler generated the code. This would be much quicker
94 constructs would be fairly low, but would give us lots of important
95 information... something else that would/could be important is to
96 have exceptions as first class types so that they would be handled in
107 would just have an array type (distinct from the pointer
108 types). This would allow us to have arbitrarily complex index
110 for example. Perhaps also, switch jump tables would be first class
111 types as well? This would allow better reasoning about the program.
[all …]
D2001-01-31-UniversalIRIdea.txt11 The idea would be that LLVM would provide a standard set of runtime features
14 perhaps a garbage collection library). Each language vm would select the
19 simplifying the language compiler. (This would also help interoperability
34 One interesting starting point would be to discuss how a JVM would be
/external/llvm/utils/lit/
DTODO38 suite. This would allow formats that anticipate large test suites to manage
50 represented each test suite by the path to its suite, then it would allow more
62 It would be really nice if we could allow test formats and test suites to add
66 formats to be registered in order to have options, but for test suites we would
81 which would be relatively easy to implement with optparser (I think).
120 (because they use features specific to bash). We would need to rewrite these
130 We could make this distinction part of the core infrastructure and that would
135 * This would provide a clear place to insert subtest support, because the
137 core. That would provide part of the infrastructure to parallelize them, for
138 example, and would probably interact well with other possible features like
[all …]
/external/protobuf/javamicro/src/main/java/com/google/protobuf/micro/
DCodedOutputStreamMicro.java400 * Compute the number of bytes that would be needed to encode a
409 * Compute the number of bytes that would be needed to encode a
417 * Compute the number of bytes that would be needed to encode a
425 * Compute the number of bytes that would be needed to encode an
433 * Compute the number of bytes that would be needed to encode an
441 * Compute the number of bytes that would be needed to encode a
450 * Compute the number of bytes that would be needed to encode a
459 * Compute the number of bytes that would be needed to encode a
468 * Compute the number of bytes that would be needed to encode a
477 * Compute the number of bytes that would be needed to encode a
[all …]
/external/python/google-api-python-client/docs/dyn/
Dserviceusage_v1beta1.services.consumerQuotaMetrics.html111 …name: string, The resource name of the quota limit. An example name would be: `projects/123/servic…
130 …ing", # The name of the parent metric of this limit. An example name would be: `compute.googl…
131 …t;A String", # The resource name of the quota limit. An example name would be: `projects/123/…
139 … # The name of the metric to which this override applies. An example name would be: `compute.googl…
140 …me is generated by the server when the override is created. Example names would be: `projects/123/…
142 …e limit unit of the limit to which this override applies. An example unit would be: `1/{project}/{…
149 … # The name of the metric to which this override applies. An example name would be: `compute.googl…
150 …me is generated by the server when the override is created. Example names would be: `projects/123/…
152 …e limit unit of the limit to which this override applies. An example unit would be: `1/{project}/{…
164 … # The name of the metric to which this override applies. An example name would be: `compute.googl…
[all …]
Dserviceconsumermanagement_v1beta1.services.consumerQuotaMetrics.html108 …uota metric, returned by a ListConsumerQuotaMetrics call. An example name would be: `services/comp…
126 …ing", # The name of the parent metric of this limit. An example name would be: `compute.googl…
127 …t;A String", # The resource name of the quota limit. An example name would be: `services/comp…
135 … # The name of the metric to which this override applies. An example name would be: `compute.googl…
136 …ring", # The resource name of the producer override. An example name would be: `services/comp…
138 …e limit unit of the limit to which this override applies. An example unit would be: `1/{project}/{…
145 … # The name of the metric to which this override applies. An example name would be: `compute.googl…
146 …ring", # The resource name of the producer override. An example name would be: `services/comp…
148 …e limit unit of the limit to which this override applies. An example unit would be: `1/{project}/{…
160 … # The name of the metric to which this override applies. An example name would be: `compute.googl…
[all …]
Dstorage_v1.bucketAccessControls.html142 # - The user liz@example.com would be user-liz@example.com.
143 # - The group example@googlegroups.com would be group-example@googlegroups.com.
144 …ll members of the Google Apps for Business domain example.com, the entity would be domain-example.…
180 # - The user liz@example.com would be user-liz@example.com.
181 # - The group example@googlegroups.com would be group-example@googlegroups.com.
182 …ll members of the Google Apps for Business domain example.com, the entity would be domain-example.…
214 # - The user liz@example.com would be user-liz@example.com.
215 # - The group example@googlegroups.com would be group-example@googlegroups.com.
216 …ll members of the Google Apps for Business domain example.com, the entity would be domain-example.…
257 # - The user liz@example.com would be user-liz@example.com.
[all …]
Dserviceusage_v1beta1.services.consumerQuotaMetrics.limits.consumerOverrides.html82 …n quota usage. Consumer overrides cannot be used to grant more quota than would be allowed by admi…
103 …n quota usage. Consumer overrides cannot be used to grant more quota than would be allowed by admi…
106 … ListConsumerQuotaMetrics or GetConsumerQuotaMetric call. An example name would be: `projects/123/…
115 … # The name of the metric to which this override applies. An example name would be: `compute.googl…
116 …me is generated by the server when the override is created. Example names would be: `projects/123/…
118 …e limit unit of the limit to which this override applies. An example unit would be: `1/{project}/{…
121 … force parameter to 'true' ignores all quota safety checks that would fail the request. …
125 …LIMIT_DECREASE_BELOW_USAGE - Validates that a quota mutation would not cause the consumer's e…
126 …LIMIT_DECREASE_PERCENTAGE_TOO_HIGH - Validates that a quota mutation would not cause the consumer&…
161 …name: string, The resource name of the override to delete. An example name would be: `projects/123…
[all …]
Dstorage_v1.defaultObjectAccessControls.html142 # - The user liz@example.com would be user-liz@example.com.
143 # - The group example@googlegroups.com would be group-example@googlegroups.com.
144 …ll members of the Google Apps for Business domain example.com, the entity would be domain-example.…
182 # - The user liz@example.com would be user-liz@example.com.
183 # - The group example@googlegroups.com would be group-example@googlegroups.com.
184 …ll members of the Google Apps for Business domain example.com, the entity would be domain-example.…
218 # - The user liz@example.com would be user-liz@example.com.
219 # - The group example@googlegroups.com would be group-example@googlegroups.com.
220 …ll members of the Google Apps for Business domain example.com, the entity would be domain-example.…
265 # - The user liz@example.com would be user-liz@example.com.
[all …]
/external/clang/test/CXX/special/class.copy/
Dp11.0x.move.cpp15 DeletedNTVariant::DeletedNTVariant(DeletedNTVariant&&) = default; // expected-error{{would delete}}
23 DeletedNTVariant2::DeletedNTVariant2(DeletedNTVariant2&&) = default; // expected-error{{would delet…
40 HasNoAccess::HasNoAccess(HasNoAccess&&) = default; // expected-error{{would delete}}
57 IsAmbiguous::IsAmbiguous(IsAmbiguous&&) = default; // expected-error{{would delete}}
66 Deleted::Deleted(Deleted&&) = default; // expected-error{{would delete}}
82 ConstMoveOnlyMember::ConstMoveOnlyMember(ConstMoveOnlyMember&&) = default; // expected-error{{would
87 VolatileMember::VolatileMember(VolatileMember&&) = default; // expected-error{{would delete}}
95 AmbiguousMoveBase::AmbiguousMoveBase(AmbiguousMoveBase&&) = default; // expected-error{{would delet…
100 DeletedMoveBase::DeletedMoveBase(DeletedMoveBase&&) = default; // expected-error{{would delete}}
105 …MoveBase::InaccessibleMoveBase(InaccessibleMoveBase&&) = default; // expected-error{{would delete}}
[all …]
/external/protobuf/javanano/src/main/java/com/google/protobuf/nano/
DCodedOutputByteBufferNano.java557 * Compute the number of bytes that would be needed to encode a
566 * Compute the number of bytes that would be needed to encode a
574 * Compute the number of bytes that would be needed to encode a
582 * Compute the number of bytes that would be needed to encode an
590 * Compute the number of bytes that would be needed to encode an
598 * Compute the number of bytes that would be needed to encode a
607 * Compute the number of bytes that would be needed to encode a
616 * Compute the number of bytes that would be needed to encode a
625 * Compute the number of bytes that would be needed to encode a
634 * Compute the number of bytes that would be needed to encode a
[all …]
/external/cronet/base/functional/
Dcallback_unittest.nc55 // callback's return type. Here we would pass `int*` to `float*`.
65 // callback's return type. Here we would pass `void` to `float`.
75 // callback's return type. Here we would pass `int` to `void`.
85 // callback's return type. Here we would pass `int*` to `float*`.
95 // callback's return type. Here we would pass `void` to `float`.
105 // callback's return type. Here we would pass `int` to `void`.
115 // callback's return type. Here we would pass `int*` to `float*`.
125 // callback's return type. Here we would pass `void` to `float`.
135 // callback's return type. Here we would pass `int` to `void`.
/external/icu/icu4j/perf-tests/data/collation/
Dvfear11a.txt143 your state is not listed and you would like to know
196 We would prefer to send you information by email.
457 mouthed doctor and slandered professor -- such would be your
500 "Because there are many ciphers which I would read as easily
514 which is the delight of your friends, would surely prevent
545 I was able to cover it up. If he had seen it, it would have
577 "Because he feared I would make some inquiry after him in
629 an unusual one, he would have sent it to me. Instead of that, he
631 in this envelope. He says so in his note. This would seem to
632 indicate that the book is one which he thought I would have no
[all …]
/external/clang/unittests/Basic/
DDiagnosticTest.cpp29 // Diag that would set UncompilableErrorOccurred and ErrorOccurred. in TEST()
32 // Diag that would set UnrecoverableErrorOccurred and ErrorOccurred. in TEST()
35 // Diag that would set FatalErrorOccurred in TEST()
56 // Diag that would set UncompilableErrorOccurred and ErrorOccurred. in TEST()
59 // Diag that would set UnrecoverableErrorOccurred and ErrorOccurred. in TEST()
62 // Diag that would set FatalErrorOccurred in TEST()
/external/llvm/docs/
DBigEndianNEON.rst69 …within the vector. This means that the register content is the same as it would have been on a lit…
93 …d the same in memory. Without this property there would be many special cases that the optimizer w…
95 Use of ``LDR`` would break this lane ordering property. This doesn't preclude the use of ``LDR``, b…
109 …encoded within them. This is important across an ABI boundary, because it would become necessary t…
126 …d treating the vector as an opaque value (just loading it and storing it) would be impossible with…
133 …LD1`` in some places to avoid alignment faults (the result of the ``LD1`` would then need to be re…
152would have to change target-agnostic compiler passes and would result in a strange IR in which lan…
179 This would produce a code sequence such as that in the figure on the right. The mismatched ``LD1`` …
190 For the previous example, this would be::
204 … in NEON/VFP registers. For example, an ``i64`` would live in an ``x`` register, but ``<1 x i64>``…
/external/mockito/src/main/java/org/mockito/
DArgumentMatchers.java182 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
269 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
292 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
315 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
338 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
361 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
384 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
407 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
430 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
453 …* would be {@link #isNull()}. We felt this change would make tests harness much safer that it was …
[all …]
/external/mbedtls/docs/architecture/psa-migration/
Dstrategy.md62 solutions to these problems would be higher or lower than the cost of
64 solutions would probably also solve other problems at the same time.)
84 part of) it ourselves under the hood as needed, but that would likely require
99 accepting an explicit `f_rng` parameter (see #5238), that would be
323 An alternative would be to have two different code paths depending on whether
385 are expressed (sometimes in bulk), to get things wrong in a way that would
414 Note: a necessary first step for that would be to make sure PSA is no longer
432 introducing new context types) would provide to users.
438 cost. For example, `mbedtls_md_context_t` would be defined as a (tagged) union
440 would initialize the correct part, and the rest of the functions be simple
[all …]
/external/iproute2/man/man7/
Dtc-hfsc.7190 and choosing the most fitting one, thus eligible time would be computed as
191 D^(\-1)(w) and deadline time would be computed as D^(\-1)(w+l). If the 2nd
195 packets earlier that would normally be allowed. That's where separate E() comes
240 whole class hierarchy would be equal.
248 criterion, A1 would become idle for a long time. We can workaround this
277 unable to guarantee the absolute values themselves \- as it would have to go
306 subtree gets 3Mbit, but its children would want (at the point when A1 became
314 violated fairness in the A subtree and set A2's service curve to 0, A1 would
342 all virtual times would be equal).
344 Without that, 'vt' would lag behind other virtual times, and could cause
[all …]
/external/clang/www/analyzer/
Dopen_projects.html18 <p>This page lists several projects that would boost analyzer's usability and
40 floats: RangeConstraintManager. This would involve adding a new SVal kind
85 ranges. A bitwise constraint manager would model constraints such as "bit 32
86 is known to be 1". This would help code that made use of bitmasks</code>.
99 determined to be equal via comparison. This would allow us to reduce the
100 number of false positives and would be a building step to more advanced
118 <p>It would be great to have more code reuse between "Minimal" and
120 IR for representing path diagnostics, which would be later be used to
143 <p>We would like to put all analyzer attributes behind a fence so that we
165 <p>This would require extending the MallocPessimistic checker to reason
[all …]

12345678910>>...552