HomeSort by relevance Sort by last modified time
    Searched refs:have (Results 176 - 200 of 1130) sorted by null

1 2 3 4 5 6 78 91011>>

  /toolchain/binutils/binutils-2.25/ld/testsuite/ld-cris/
tls-global-74.d 13 # symbol. Check that we have proper NPTL/TLS markings and GOT.
tls-ie-8e1.d 10 # Check that we have proper NPTL/TLS markings and a constant GOT.
tls-le-12.d 9 # Check that we have proper NPTL/TLS markings and no GOT for an
tls-le-12s.d 9 # Check that we have proper NPTL/TLS markings and no GOT for an
tls-local-59.d 10 # symbol. Check that we have proper NPTL/TLS markings and GOT.
tls-local-60.d 9 # symbol. Check that we have proper NPTL/TLS markings and GOT.
tls-local-61.d 8 # symbol. Check that we have proper NPTL/TLS markings and GOT.
weakhiddso.d 7 # correctly when generating a DSO. For now, we have to live with the
  /toolchain/binutils/binutils-2.25/ld/testsuite/ld-elf/
flags1.d 11 # (There is no good reason why they have to be).
  /toolchain/binutils/binutils-2.25/ld/testsuite/ld-mmix/
orph-d.d 10 # attach to .debug_info, i.e. have address 0.
sec-6.d 9 # A non-loaded section with relocs would have the SEC_RELOC bit set in the
  /build/core/
goma.mk 48 $(warning You should have goma in $$GOMA_DIR or $(HOME)/goma) \
  /external/chromium-libpac/test/js-unittest/
bindings.js 21 // Those expected to fail (because we have passed a non-string parameter)
22 // will return |null|, whereas those that have called through to the C++
  /external/chromium-trace/catapult/third_party/closure_linter/closure_linter/
runner.py 42 'descriptions, or methods whose @return tags don\'t have a '
  /external/chromium-trace/catapult/third_party/polymer/components/web-animations-js/
History.md 43 If you have any feedback on this change, please start a discussion
79 features that are still undergoing discussion or have yet to be
87 Not all features of the previous polyfill have been ported to the
  /external/jcommander/
Android.mk 25 # Host JAR builds have every single file because all the standard APIs are available.
51 # TODO: also add the tests once we have testng working.
  /external/llvm/test/ExecutionEngine/RuntimeDyld/X86/
ELF_STT_FILE.s 7 # crash if we are relocating against a symbol that happens to have the
  /external/llvm/test/MC/ARM/
ltorg-darwin.s 4 @ between darwin and linux. Any tests added here should have a matching
135 @ should not have a constant pool at end of section with empty constant pools
141 @ should have a non-empty constant pool at end of this section
150 @ should not have a constant pool at end of section with empty constant pools
ltorg.s 4 @ between darwin and linux. Any tests added here should have a matching
124 @ should not have a constant pool at end of section with empty constant pools
130 @ should have a non-empty constant pool at end of this section
137 @ should not have a constant pool at end of section with empty constant pools
macho-relocs-with-addend.s 5 @ (scattered) still need to have the type set correctly.
  /external/valgrind/gdbserver_tests/
mcleak.stderr.exp 7 expecting to have NO details
10 expecting to have NO details
  /ndk/build/core/
check-cygwin-make.mk 16 # Check that we have a Cygwin-compatible make.
19 # have another GNU Make installed in their path, that fails
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/detail/
fenv.hpp 11 #error This platform does not have a floating point environment
17 /* If we're using clang + glibc, we have to get hacky.
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/iterator/detail/
config_def.hpp 20 # error you have nested config_def #inclusion.
  /packages/apps/Messaging/
ForceProguard.mk 17 # build. If the flag files have changed, proguard is rerun.
31 $(info *** Flag files used for proguard have changed; forcing proguard to rerun.)

Completed in 665 milliseconds

1 2 3 4 5 6 78 91011>>