HomeSort by relevance Sort by last modified time
    Searched full:compilation (Results 251 - 275 of 2636) sorted by null

<<11121314151617181920>>

  /external/qemu/distrib/kernel-toolchain/
android-kernel-toolchain-strip 9 # Also support ccache compilation if USE_CCACHE is defined as "1"
toolbox.sh 9 # Also support ccache compilation if USE_CCACHE is defined as "1"
  /external/qemu-pc-bios/
README 18 Fixed compilation error + x86-64 correctness fix
  /external/srtp/
TODO 10 - re-write configure.in to make cross-compilation easier
  /external/valgrind/main/helgrind/tests/
filter_stderr 18 # Likewise for frame numbers, which depend on compilation.
  /hardware/samsung_slsi/exynos5/mobicore/common/MobiCore/inc/
mcVersionHelper.h 84 * On success, compilation goes through.
85 * On error, compilation breaks, telling the component that did not match in the
142 * On success, compilation goes through.
143 * On error, compilation breaks, telling the component that did not match in the
  /ndk/sources/host-tools/ndk-stack/elff/
dwarf_defs.h 340 * are counted on per-compilation unit basis. I.e. abbreviation number for the
341 * first DIE abbreviation descriptor of each compilation unit is always 1.
415 * NOTE: DIE abbreviation descriptor indexes are tied to the compilation
416 * unit. In other words, each compilation unit restarts counting DIE
484 /* Compilation unit header in the .debug_info section.
493 /* Size of the compilation unit data in .debug_info section. */
496 /* Compilation unit's DWARF version stamp. */
500 * beginning of abbreviation sequence for this compilation unit.
504 /* Pointer size for this compilation unit (should be 4, or 8). */
507 /* Compilation unit header in the .debug_info section for 32-bit DWARF. *
    [all...]
  /ndk/sources/host-tools/sed-4.2.1/m4/
strerror.m4 17 # Like gl_FUNC_STRERROR, except prepare for separate compilation (no AC_LIBOBJ).
  /ndk/tests/device/issue42891-boost-1_52/jni/boost/boost/config/compiler/
clang.hpp 29 // Clang supports "long long" in all compilation modes.
  /prebuilts/python/darwin-x86/2.7.5/include/python2.7/
pymacconfig.h 70 * mode that depends on the compilation environment
  /prebuilts/python/linux-x86/2.7.5/include/python2.7/
pymacconfig.h 70 * mode that depends on the compilation environment
  /system/core/include/cutils/
atomic-inline.h 33 * 0 or 1, indicating compilation for UP or SMP, respectively.
  /external/bison/build-aux/snippet/
warn-on-use.h 28 FUNCTION with a different signature in C is a compilation error, so
37 provided only via a macro, the result is a compilation error rather
54 (less common usage, like &environ, will cause a compilation error
  /external/chromium_org/third_party/angle/src/compiler/translator/
ShHandle.h 66 // Get results of the last compilation.
86 // Clears the results from the previous compilation.
155 // Results of compilation.
  /external/clang/examples/clang-interpreter/
main.cpp 12 #include "clang/Driver/Compilation.h"
87 std::unique_ptr<Compilation> C(TheDriver.BuildCompilation(Args));
94 // failed. Extract that job from the compilation.
  /external/icu/icu4c/source/samples/legacy/
README 6 What is it all about: Let's say you have a 10 Tb database indexed using ICU 1.8.1. sortkeys. New ICU comes out, with neat new features you would like to use, but also with new sortkeys and you don't care to reindex your 10 Tb database. What to do then??? You can use ICU 1.8.1. in one of your compilation units and current version in all the others. So, you can use old collation until you decide to reindex.
8 You cannot mix two versions of ICU in the same compilation unit. You cannot automatically use more than one legacy version of ICU.
10 In order to make the compilation unit use old version of ICU, you have to do a couple of things:
  /external/libpng/scripts/
makefile.cegcc 42 $(NAME): remove-old copy-src compilation copy manifest archive
65 compilation:
66 @echo " * Compilation of $(PACKAGE)"
  /external/llvm/include/llvm/ExecutionEngine/
JITEventListener.h 1 //===- JITEventListener.h - Exposes events from JIT compilation -*- C++ -*-===//
11 // callbacks when significant events happen during the JIT compilation process.
50 /// about significant events during compilation. For example, to notify
  /external/llvm/include/llvm/LTO/
LTOCodeGenerator.h 12 // LTO compilation consists of three phases: Pre-IPO, IPO and Post-IPO.
19 // compilation.
110 // is brought to memory. Return NULL if the compilation was not successful.
  /external/llvm/utils/release/
findRegressions-simple.py 123 print 'REGRESSION: Compilation Failed'
131 print 'REGRESSION: Compilation Time'
139 print 'NEW PASSES: Compilation'
  /external/protobuf/gtest/test/
gtest_nc.cc 32 // This file is the input to a negative-compilation test for Google
37 // We still need to write the negative-compilation test itself, which
40 // TODO(wan@google.com): finish the negative-compilation test.
  /prebuilts/misc/darwin-x86/analyzer/bin/
cxx-analyzer 14 # CCC_CXX: The origianl LOCAL_CXX which does the real compilation and code-gen
18 # modified to prefix/append them in options passed to clang++ for successful compilation
38 # passed for C++ compilation by build system
  /external/stlport/
configure 55 --with-cxx=<name> use <name> as C++ compiler (use --target= for cross-compilation)
56 --with-cc=<name> use <name> as C compiler (use --target= for cross-compilation)
97 \$CXX C++ compiler name (use --target= for cross-compilation)
98 \$CC C compiler name (use --target= for cross-compilation)
292 echo "For cross-compilation with gcc use --target option only"
  /external/chromium_org/tools/
nocompile_driver.py 10 invoke gcc on a source file and assert that compilation fails.
146 stdout from the compilation, and the compilation failed, then the test is
148 compiler output and just check for failed compilation. If |expectations|
150 should expect a SUCCESSFUL compilation.
329 # This signals a compiler sanity check test. Fail iff compilation failed.
340 'Unexpected successful compilation.',
  /external/clang/docs/
CrossCompilation.rst 2 Cross-compilation using Clang
21 related to cross-compilation, and what main compiler options Clang provides
22 for performing cross-compilation.
24 Cross compilation issues
68 General Cross-Compilation Options in Clang
76 match (since Clang assumes the host triple), and the compilation will
171 your code, it will get every dependency wrong, and your compilation

Completed in 605 milliseconds

<<11121314151617181920>>