HomeSort by relevance Sort by last modified time
    Searched refs:correct (Results 201 - 225 of 906) sorted by null

1 2 3 4 5 6 7 891011>>

  /prebuilts/go/linux-x86/src/time/
zoneinfo_test.go 68 // Test that we get the correct results for times before the first
  /prebuilts/go/linux-x86/test/
escape.go 9 // Test for correct heap-moving of escaped variables.
nilptr.go 17 // that Go is doing the correct explicit checks to catch
  /toolchain/binutils/binutils-2.27/gas/testsuite/gas/m68hc11/
9s12x-exg-sex-tfr.s 1 # Test for correct generation of 9s12x specific insns.
  /build/soong/cc/
lto.go 84 // Work around bug in Clang that doesn't pass correct emulated
163 // Use correct dependencies if LTO property is explicitly set
  /device/linaro/bootloader/edk2/EdkCompatibilityPkg/Compatibility/BootScriptSaveOnS3SaveStateThunk/X64/
AsmDispatchExecute.S 113 # reload DS/ES/SS to make sure they are correct referred to current GDT
AsmDispatchExecute.asm 111 ; reload DS/ES/SS to make sure they are correct referred to current GDT
  /device/linaro/bootloader/edk2/IntelFspWrapperPkg/Library/BaseFspApiLib/X64/
Thunk64To32.S 119 # reload DS/ES/SS to make sure they are correct referred to current GDT
Thunk64To32.asm 117 ; reload DS/ES/SS to make sure they are correct referred to current GDT
  /external/llvm/test/MC/ARM/
eh-directive-section-multiple-func.s 10 @ test case, we are checking whether the section is correct when .section
  /external/llvm/test/MC/Mips/
mips-register-names-o32.s 3 # Check that the register names are mapped to their correct numbers for o32
mips64-register-names-o32.s 4 # Check that the register names are mapped to their correct numbers for o32
set-at-directive.s 4 # for ".set at" and set the correct value.
  /prebuilts/go/darwin-x86/src/index/suffixarray/
suffixarray_test.go 139 // check that each result is in fact a correct match and there are no duplicates
177 // check that each result is in fact a correct match and the result is sorted
  /prebuilts/go/darwin-x86/src/net/
lookup_windows_test.go 155 // "Non-authoritative answer" and it doesn't return the correct errcode
206 // assumes the last CNAME is the correct one
  /prebuilts/go/linux-x86/src/index/suffixarray/
suffixarray_test.go 139 // check that each result is in fact a correct match and there are no duplicates
177 // check that each result is in fact a correct match and the result is sorted
  /prebuilts/go/linux-x86/src/net/
lookup_windows_test.go 155 // "Non-authoritative answer" and it doesn't return the correct errcode
206 // assumes the last CNAME is the correct one
  /compatibility/cdd/7_hardware-compatibility/
7_1_display-and-graphics.md 31 * [C-0-1] Device implementations MUST report the correct layout size for the
33 Specifically, device implementations MUST report the correct logical
141 * [C-1-1] MUST report correct values for all display metrics defined in the
165 * [C-0-2] MUST report the correct value for the device?s current
251 * [C-1-1] MUST report the correct integer value with the
  /build/soong/bpfix/bpfix/
bpfix_test.go 81 // check that the value for the legacy property was updated to the correct value
  /build/soong/ui/build/
dumpvars.go 134 // So that we can use the correct TARGET_PRODUCT if it's been
  /external/mesa3d/docs/specs/OLD/
MESA_packed_depth_stencil.spec 49 2. If not, is it correct to use _REV to indicate that stencil
  /external/python/cpython2/Lib/idlelib/idle_test/
htest.py 230 'msg': "Test for correct display of all paths in sys.path.\n"
284 "Check that exc_value, exc_tb, and exc_type are correct.\n"
  /external/python/cpython3/Lib/idlelib/idle_test/
htest.py 223 'msg': "Test for correct display of all paths in sys.path.\n"
296 "Check that exc_value, exc_tb, and exc_type are correct.\n"
  /external/skia/tests/
SkNxTest.cpp 191 // This way should always be exactly correct.
192 int correct = (av * bv).div255()[0]; local
193 REPORTER_ASSERT(r, correct == exact);
195 // We're a bit more flexible on this method: correct for 0 or 255, otherwise off by <=1.
  /external/skqp/tests/
SkNxTest.cpp 191 // This way should always be exactly correct.
192 int correct = (av * bv).div255()[0]; local
193 REPORTER_ASSERT(r, correct == exact);
195 // We're a bit more flexible on this method: correct for 0 or 255, otherwise off by <=1.

Completed in 1214 milliseconds

1 2 3 4 5 6 7 891011>>