Home
last modified time | relevance | path

Searched refs:destructors (Results 1 – 25 of 59) sorted by relevance

123

/external/compiler-rt/test/BlocksRuntime/
Dcopyconstructor.C14 int destructors = 0; variable
52 ++destructors; in ~TestObject()
79 if (constructors != destructors) { in main()
80 printf("%d constructors but only %d destructors\n", constructors, destructors); in main()
Dreference.C18 int destructors = 0; variable
57 ++destructors; in ~TestObject()
/external/boringssl/src/crypto/
Dthread_pthread.c88 thread_local_destructor_t destructors[NUM_OPENSSL_THREAD_LOCALS]; in thread_local_destructor() local
92 memcpy(destructors, g_destructors, sizeof(destructors)); in thread_local_destructor()
98 if (destructors[i] != NULL) { in thread_local_destructor()
99 destructors[i](pointers[i]); in thread_local_destructor()
Dthread_win.c167 thread_local_destructor_t destructors[NUM_OPENSSL_THREAD_LOCALS]; in thread_local_destructor() local
170 memcpy(destructors, g_destructors, sizeof(destructors)); in thread_local_destructor()
175 if (destructors[i] != NULL) { in thread_local_destructor()
176 destructors[i](pointers[i]); in thread_local_destructor()
/external/clang/docs/analyzer/
DIPA.txt43 -analyzer-config c++-inlining=[none | methods | constructors | destructors]
46 inlined as well; it doesn't make sense to inline destructors without inlining
49 The default c++-inlining mode is 'destructors', meaning that all member
54 destructors will not be inlined. Additionally, no C++ member functions will be
90 This option controls whether constructors and destructors of "container" types
95 Currently, these constructors and destructors are NOT considered for inlining
134 call. (In the case of calls without origin expressions, such as destructors,
186 implicit destructors, or if the destructors for the given object are not
192 or operator 'delete', nor does it inline the constructors and destructors
353 placement of their destructors in the CFG. We currently won't inline their
[all …]
/external/bison/tests/
Dglr-regression.at748 ## No users destructors if stack 0 deleted. See ##
752 AT_SETUP([No users destructors if stack 0 deleted])
764 static int destructors = 0;
773 destructors += 1;
779 ambig0 'a' { destructors += 2; USE ($2); }
780 | ambig1 start { destructors += 1; }
781 | ambig2 start { destructors += 1; }
803 if (tokens != destructors)
805 fprintf (stderr, "Tokens = %d, Destructors = %d\n", tokens, destructors);
880 ## Undesirable destructors if user action cuts parse. ##
[all …]
/external/llvm/test/Transforms/Inline/
Dinvoke-cleanup.ll21 ; this call site (PR17872), otherwise C++ destructors will not be
/external/llvm/bindings/ocaml/executionengine/
Dllvm_executionengine.mli66 (** [run_static_dtors ee] executes the static destructors of each module in
/external/clang/test/Analysis/
Dtemporaries.cpp114 namespace destructors { namespace
/external/llvm/docs/
DExceptionHandling.rst214 - C++ front-ends use this for calling objects' destructors.
223 unwinds the stack and calls object destructors first. For example, the GNU
224 C++ unwinder does not call object destructors when an unhandled exception
265 destructors are a typical example, but other languages and language extensions
358 such as calling object destructors. The runtime handles the actual unwinding
/external/llvm/lib/Target/AArch64/
DAArch64CallingConvention.td258 // Constructors and destructors return 'this' in the iOS 64-bit C++ ABI; since
264 // destructors with 'this' returns, so this RegMask will not be used in that
/external/clang/include/clang/Frontend/
DCodeGenOptions.def39 CODEGENOPT(CXAAtExit , 1, 1) ///< Use __cxa_atexit for calling destructors.
/external/clang/docs/
DBlock-ABI-Apple.rst851 copied objects with constructor/destructors. The (1<<26) bit is set and
881 and of course the constructors/destructors for ``const`` copied C++ objects.
885 copied objects with constructor/destructors, and again the (1<<26) bit is set
DThreadSafetyAnalysis.rst652 No checking inside constructors and destructors.
656 destructors. In other words, every constructor and destructor is treated as
661 The same is true of destructors.
/external/clang/lib/StaticAnalyzer/
DREADME.txt123 -cfg-add-implicit-dtors Add C++ implicit destructors to CFGs for all analyses
/external/llvm/docs/HistoricalNotes/
D2001-05-18-ExceptionHandling.txt196 llvm. Java would be very similar, except it only uses destructors to unlock
/external/llvm/lib/Target/ARM/
DARMCallingConv.td208 // Constructors and destructors return 'this' in the ARM C++ ABI; since 'this'
/external/llvm/lib/Support/Unix/
DProgram.inc305 // object destructors cloned from the parent process aren't
/external/bison/
DNEWS89 The parse function now catches exceptions, uses the %destructors to
231 for other actions such as printers, destructors, or initial actions. It
237 type-name in destructors, printers, and initial actions. For instance:
1301 if the symbols have destructors. For instance:
1343 The %parse-params are available in the destructors (and the
2039 LocalWords: YYRECOVERING nonfree destructors YYABORT YYACCEPT params enums de
DTODO44 class in the printers/destructors, which is not good for an operator<<
/external/selinux/libselinux/
DChangeLog166 * Hide unnecessarily-exported library destructors
252 * Library destructors for thread local storage keys from Eamon Walsh.
1001 * Merged destructors patch from Tomas Mraz.
/external/clang/include/clang/Driver/
DCC1Options.td46 HelpText<"Add C++ implicit destructors to CFGs for all analyses">;
233 HelpText<"Emit complete constructors and destructors as aliases when possible">;
/external/compiler-rt/lib/builtins/
DREADME.txt211 // because there are no catch clauses or destructors to be run. But there
/external/llvm/
DCMakeLists.txt337 option(LLVM_DISABLE_LLVM_DYLIB_ATEXIT "Disable llvm-shlib's atexit destructors." ON)
/external/clang/include/clang/Basic/
DDiagnosticGroups.td185 def ExitTimeDestructors : DiagGroup<"exit-time-destructors">;

123