HomeSort by relevance Sort by last modified time
    Searched full:requirements (Results 551 - 575 of 3071) sorted by null

<<21222324252627282930>>

  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8/x86_64-linux/include/c++/4.8/tr1/
unordered_set.h 161 * Meets the requirements of a <a href="tables.html#65">container</a>, and
210 * Meets the requirements of a <a href="tables.html#65">container</a>, and
  /prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/x86_64-w64-mingw32/include/c++/4.8.3/bits/
stl_tempbuf.h 124 // concept requirements
228 // Requirements: _Pointer::value_type(_Tp&&) is valid.
  /prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/x86_64-w64-mingw32/include/c++/4.8.3/tr1/
unordered_set.h 161 * Meets the requirements of a <a href="tables.html#65">container</a>, and
210 * Meets the requirements of a <a href="tables.html#65">container</a>, and
  /prebuilts/ndk/current/sources/cxx-stl/gnu-libstdc++/4.9/include/bits/
stl_tempbuf.h 124 // concept requirements
228 // Requirements: _Pointer::value_type(_Tp&&) is valid.
  /prebuilts/ndk/current/sources/cxx-stl/gnu-libstdc++/4.9/include/tr1/
unordered_set.h 161 * Meets the requirements of a <a href="tables.html#65">container</a>, and
210 * Meets the requirements of a <a href="tables.html#65">container</a>, and
  /external/icu/android_icu4j/src/main/java/android/icu/text/
StringPrep.java 51 * requirements for bidirectional strings. If the string does not
52 * satisfy the requirements for bidirectional strings, return an
460 requirements for bidirectional strings. If the string does not
461 satisfy the requirements for bidirectional strings, return an
465 the requirements below, an "RandALCat character" is a character that
475 three of the following requirements MUST be met:
  /external/icu/icu4j/main/classes/core/src/com/ibm/icu/text/
StringPrep.java 50 * requirements for bidirectional strings. If the string does not
51 * satisfy the requirements for bidirectional strings, return an
477 requirements for bidirectional strings. If the string does not
478 satisfy the requirements for bidirectional strings, return an
482 the requirements below, an "RandALCat character" is a character that
492 three of the following requirements MUST be met:
  /external/libogg/doc/
oggstream.html 210 storage or latency requirements.
250 <p>Buffering requirements in this design need not be explicitly
395 <h2>Mapping Requirements</h2>
400 codec's <em>mapping</em>. Ogg imposes a few mapping requirements
424 <h2>Multiplexing Requirements</h2>
426 <p>Multiplexing requirements within Ogg are straightforward. When
  /hardware/qcom/media/msm8974/mm-video-legacy/vidc/venc/test/
video_encoder_test.c 331 DEBUG_PRINT("\n Query Input bufffer requirements");
332 /*Get the Buffer requirements for input and output ports*/
342 DEBUG_PRINT("\n Requesting for input buffer requirements failed");
359 DEBUG_PRINT("\n Set Buffer Requirements Failed");
364 DEBUG_PRINT("\n Query output bufffer requirements");
371 DEBUG_PRINT("\n Requesting for output buffer requirements failed");
  /packages/apps/Settings/src/com/android/settings/
ChooseLockPassword.java 184 * Password requirements that we need to verify.
505 * Read the requirements from {@link DevicePolicyManager} and intent and aggregate them.
553 // Reserve all the requirements.
582 // The length requirements are fulfilled.
634 // Check the requirements one by one.
    [all...]
  /docs/source.android.com/src/compatibility/2.3/
android-2.3-cdd.xhtml 135 <p>This document enumerates the requirements that must be met in order for
145 MUST meet the requirements presented in this Compatibility Definition,
227 requirements in this section.</p>
242 for specific requirements for this scenario.</p>
250 implementations MUST meet all the requirements presented in this section.</p>
255 requirements related to the Android security model.</p>
286 identifier was used to generate the build. There are no requirements on the
330 human readable format. There are no requirements on the specific format of
347 is marketed and sold to end users. There are no requirements on the specific
382 build. There are no requirements on the specific format of this field, excep
    [all...]
  /docs/source.android.com/src/compatibility/5.1/
android-5.1-cdd.html 324 <p>This document enumerates the requirements that must be met in order for devices
336 the requirements presented in this Compatibility Definition, including any
364 compatibility requirements were optimized for handheld devices. Starting from
405 types still MUST meet all requirements in this document to be Android 5.1
552 MUST still be present and behave in a reasonable way. See <a href="#7_hardware_compatibility">section 7</a> for specific requirements for this scenario.</p>
565 documented by the Permission reference page [<a href="http://developer.android.com/reference/android/Manifest.permission.html">Resources, 6]</a>. Note that <a href="#9_security_model_compatibility">section 9</a> lists additional requirements related to the Android security model.</p>
602 identifier was used to generate the build. There are no requirements on the
675 human-readable format. There are no requirements on the specific format of this
689 There are no requirements on the specific format of this field, except that it
696 marketed and sold to end users. There are no requirements on the specifi
    [all...]
  /docs/source.android.com/src/compatibility/4.2/
android-4.2-cdd.xhtml 166 <p>This document enumerates the requirements that must be met in order for
176 MUST meet the requirements presented in this Compatibility Definition,
296 <a href="#section-7">Section 7</a> for specific requirements for this scenario.
308 requirements related to the Android security model.</p>
345 identifier was used to generate the build. There are no requirements on the
407 human readable format. There are no requirements on the specific format o
    [all...]
  /external/libcxx/www/
cxx1y_status.html 54 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3346.pdf">3346</a></td><td>LWG</td><td>Terminology for Container Element Requirements - Rev 1</td><td>Kona</td><td>Complete</td><td>3.4</td></tr>
112 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#1214">1214</a></td><td>Insufficient/inconsistent key immutability requirements for associative containers</td><td>Kona</td><td>Complete</td></tr>
135 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#2081">2081</a></td><td>Allocator requirements should include CopyConstructible</td><td>Portland</td><td>Complete</td></tr>
140 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#2105">2105</a></td><td>Inconsistent requirements on const_iterator's value_type</td><td>Portland</td><td>Complete</td></tr>
142 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#2123">2123</a></td><td>merge() allocator requirements for lists versus forward lists</td><td>Portland</td><td>Complete</td></tr>
162 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#2169">2169</a></td><td>Missing reset() requirements in unique_ptr specialization</td><td>Bristol</td><td>Complete</td></tr>
166 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#2109">2109</a></td><td>Incorrect requirements for hash specializations</td><td>Bristol</td><td>Complete</td></tr>
174 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#2177">2177</a></td><td>Requirements on Copy/MoveInsertable</td><td>Bristol</td><td>Complete</td></tr>
185 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#2211">2211</a></td><td>Replace ambiguous use of "Allocator" in container requirements</td><td>Bristol</td><td>Complete</td></tr>
190 <tr><td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-defects.html#2235">2235</a></td><td>Undefined behavior without proper requirements on basic_string constructors</td><td>Bristol</td><td>Complete</td></tr
    [all...]
  /docs/source.android.com/src/compatibility/4.3/
android-4.3-cdd.xhtml 168 <p>This document enumerates the requirements that must be met in order for
178 MUST meet the requirements presented in this Compatibility Definition,
301 <a href="#section-7">Section 7</a> for specific requirements for this scenario.
313 requirements related to the Android security model.</p>
350 identifier was used to generate the build. There are no requirements on the
    [all...]
  /ndk/tests/device/test-libc++-static-full/jni/
Android.mk     [all...]
  /ndk/tests/device/test-libc++-shared-full/jni/
Android.mk     [all...]
  /docs/source.android.com/src/compatibility/6.0/
android-6.0-cdd.html 358 <p>This document enumerates the requirements that must be met in order for devices
370 the requirements presented in this Compatibility Definition, including any
398 compatibility requirements were optimized for handheld devices. Starting from
446 types still MUST meet all requirements in this document to be Android 6.0
593 MUST still be present and behave in a reasonable way. See <a href="#7_hardware_compatibility">section 7</a> for specific requirements for this scenario.</p>
606 documented by the Permission reference page [<a href="http://developer.android.com/reference/android/Manifest.permission.html">Resources, 7</a>]. Note that <a href="#9_security_model_compatibility">section 9</a> lists additional requirements related to the Android security model.</p>
643 identifier was used to generate the build. There are no requirements on the
716 human-readable format. There are no requirements on the specific format of this
730 There are no requirements on the specific format of this field, except that it
737 marketed and sold to end users. There are no requirements on the specifi
    [all...]
  /frameworks/base/docs/html/guide/topics/graphics/
opengl.jd 14 <li><a href="#manifest">Declaring OpenGL Requirements</a></li>
195 <h2 id="manifest">Declaring OpenGL Requirements</h2>
197 these requirements in your <a
202 <li><strong>OpenGL ES version requirements</strong> - If your application requires a specific
242 <li><strong>Texture compression requirements</strong> - If your application uses texture
248 <p>Declaring texture compression requirements in your manifest hides your application from users
363 matrix. Depending on your application requirements, you may want to define separate projection
489 use of OpenGL shaders. You should carefully consider the graphics requirements and choose the API
503 reducing memory requirements and making more efficient use of memory bandwidth. The Android
    [all...]
  /cts/tests/camera/src/android/hardware/camera2/cts/
StaticMetadataTest.java 282 // Capability requirements other than key presences
345 // Legacy mode always doesn't support these requirements
428 // Check additional requirements and exit early if possible
453 // Check additional requirements
468 "Camera %s doesn't list capability %s but meets all requirements",
  /docs/source.android.com/src/devices/camera/
versioning.jd 131 <h2 id=cts_requirements>CTS requirements</h2>
145 requirements. Bugs that are exposed (and which cause a Camera API2 CTS failure)
156 requirements.</p>
196 <h3 id=hardening_general>Additional requirements</h3>
198 security include the following additional device requirements.</p>
  /external/autotest/server/
site_linux_system.py 542 """Ensure MAC address of |net_dev| meets uniqueness requirements.
666 def require_capabilities(self, requirements, fatal_failure=False):
669 Check that capabilities in |requirements| exist on this system.
674 @param requirements list of CAPABILITY_* defined above.
681 missing = [cap for cap in requirements if not cap in self.capabilities]
  /external/clang/include/clang/Basic/
Module.h 148 /// If any of these requirements are not available, the \c IsAvailable bit
150 SmallVector<Requirement, 2> Requirements;
152 /// \brief Whether this module is missing a feature from \c Requirements.
160 /// If the module is missing headers or does not meet all requirements then
327 /// will be set to one of the requirements that is not met for use of
  /external/libxml2/doc/
xmlmem.html 15 <li><a href="#General4">General memory requirements</a></li>
89 spot memory usage errors in a very precise way.</p><h3><a name="General4" id="General4">General memory requirements</a></h3><p>How much libxml2 memory require ? It's hard to tell in average it depends
96 <li>If you are generating the DOM tree then memory requirements will grow
104 <li>If you need to work with fixed memory requirements or don't need the
110 fixed memory requirements, and try to get the fastest parsing possible
  /external/webrtc/webrtc/modules/audio_processing/aec/
system_delay_unittest.cc 174 // The tests should meet basic requirements and not be adjusted to what is
177 // General requirements:
225 // delay meets the requirements.
237 // Verify system delay with respect to requirements, i.e., the
295 // Verify system delay with respect to requirements, i.e., the

Completed in 731 milliseconds

<<21222324252627282930>>