HomeSort by relevance Sort by last modified time
    Searched full:initializers (Results 1 - 25 of 3221) sorted by null

1 2 3 4 5 6 7 8 91011>>

  /external/llvm/test/CodeGen/NVPTX/
gvar-init.ll 3 ; Error out if initializer is given for address spaces that do not support initializers
  /external/clang/test/SemaCXX/
c99.cpp 7 Point p1 = { .x = 17, // expected-warning{{designated initializers are a C99 feature}}
8 y: 25 }; // expected-warning{{designated initializers are a C99 feature}} \
complex-init-list.cpp 7 // initializers, this extension kicks in to turn it into component-wise
  /external/compiler-rt/test/asan/TestCases/Windows/
crt_initializers.cc 17 // Iterate through CRT initializers.
23 printf("Number of nonzero CRT initializers: %u\n", count);
24 // CHECK: Number of nonzero CRT initializers
  /external/clang/test/CodeGen/
2004-01-01-UnknownInitSize.c 4 * This regression test ensures that the C front end can compile initializers
2002-03-12-ArrayInitialization.c 3 /* GCC would generate bad code if not enough initializers are
2005-01-02-ConstantInits.c 3 // This tests all kinds of hard cases with initializers and
  /external/clang/test/Sema/
big-endian-neon-initializers.c 6 int32x4_t x = {1, 2, 3, 4}; // expected-warning{{vector initializers are not compatible with NEON intrinsics}} expected-note{{consider using vld1q_s32() to initialize a vector from memory, or vcombine_s32(vcreate_s32(), vcreate_s32()) to initialize from integer constants}}
7 int16x4_t y = {1, 2, 3, 4}; // expected-warning{{vector initializers are not compatible with NEON intrinsics}} expected-note{{consider using vld1_s16() to initialize a vector from memory, or vcreate_s16() to initialize from an integer constant}}
8 int64x2_t z = {1, 2}; // expected-warning{{vector initializers are not compatible with NEON intrinsics}} expected-note{{consider using vld1q_s64() to initialize a vector from memory, or vcombine_s64(vcreate_s64(), vcreate_s64()) to initialize from integer constants}}
9 float32x2_t b = {1, 2}; // expected-warning{{vector initializers are not compatible with NEON intrinsics}} expected-note{{consider using vld1_f32() to initialize a vector from memory, or vcreate_f32() to initialize from an integer constant}}
  /external/llvm/test/CodeGen/PowerPC/
i128-and-beyond.ll 3 ; These static initializers are too big to hand off to assemblers
  /external/llvm/test/CodeGen/X86/
i128-and-beyond.ll 3 ; These static initializers are too big to hand off to assemblers
  /external/chromium_org/third_party/mesa/src/src/glsl/
TODO 3 - Improve handling of constants and their initializers. Constant initializers
  /external/mesa3d/src/glsl/
TODO 3 - Improve handling of constants and their initializers. Constant initializers
  /device/generic/goldfish/opengl/system/gralloc/
Android.mk 10 LOCAL_CFLAGS += -Wno-missing-field-initializers
  /external/harfbuzz_ng/src/
check-static-inits.sh 23 echo "Checking that no object file has static initializers"
26 echo "Ouch, $obj has static initializers"
  /external/llvm/include/llvm/IR/
GlobalVariable.h 16 // area. Global Constants are required to have initializers.
47 // initializers are run?
76 /// Definitions have initializers, declarations don't.
102 // marker may change at runtime before C++ initializers are evaluated.
110 // It's not safe to modify initializers of global variables with weak
115 // have different initializers, breaking the One Definition Rule.
117 // It is not safe to modify initializers of global variables with the
119 // before C++ initializers are evaluated.
169 /// replace constant initializers.
  /external/chromium_org/tools/mac/
dump-static-initializers.py 7 Dumps a list of files with static initializers. Use with release builds.
10 tools/mac/dump-static-initializers.py out/Release/Chromium\ Framework.framework.dSYM/Contents/Resources/DWARF/Chromium\ Framework
36 static initializers.
  /external/chromium_org/sdch/
logging_forward.h 13 // open-vcdiff's logging.h includes iostream, which adds static initializers
BUILD.gn 58 # open-vcdiff's logging.h introduces static initializers. This was
63 # introduce static initializers, and which prevents open-vcdiff's
  /external/chromium_org/third_party/WebKit/Source/wtf/
StaticConstructors.h 26 // initializers from being registered and called on program startup. On GCC, we
29 // to have the CRT ignore our static initializers. The constructors will never
41 // initializers ignored. This is currently the case. This means that if
43 // initializers after the include will not be executed.
  /external/clang/test/Parser/
cxx11-type-specifier.cpp 17 // initializers. Sad but true...
  /external/smack/src/org/xbill/DNS/
UNKRecord.java 9 * class can only be initialized using static Record initializers.
  /ndk/tests/device/test-stlport_shared-exception/jni/
pretty2.cpp 3 // in initializers at global scope
  /ndk/tests/device/test-stlport_static-exception/jni/
pretty2.cpp 3 // in initializers at global scope
  /external/chromium_org/third_party/re2/
README.chromium 20 - Remove static initializers (patches/remove-static-initializers.patch)
  /external/clang/unittests/AST/
EvaluateAsRValueTest.cpp 11 // \brief Unit tests for evaluation of constant initializers.
33 /// \brief Records information on variable initializers to a map.
87 // failures because it assumed that the type of initializers was always

Completed in 874 milliseconds

1 2 3 4 5 6 7 8 91011>>