Home
last modified time | relevance | path

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

123

/llvm-project-15.0.7/compiler-rt/test/BlocksRuntime/
H A Dcopyconstructor.C13 int destructors = 0; variable
51 ++destructors; in ~TestObject()
78 if (constructors != destructors) { in main()
79 printf("%d constructors but only %d destructors\n", constructors, destructors); in main()
H A Dreference.C17 int destructors = 0; variable
56 ++destructors; in ~TestObject()
/llvm-project-15.0.7/libcxx/test/std/utilities/memory/allocator.traits/allocator.traits.members/
H A Ddestroy.pass.cpp86 int destructors = 0; in test() local
90 std::allocator_traits<Alloc>::construct(alloc, pool, &destructors); in test()
91 assert(destructors == 0); in test()
94 assert(destructors == 1); in test()
/llvm-project-15.0.7/clang/docs/analyzer/developer-docs/
H A DIPA.rst47 inlined as well; it doesn't make sense to inline destructors without inlining
50 The default c++-inlining mode is 'destructors', meaning that all member
55 destructors will not be inlined. Additionally, no C++ member functions will be
94 This option controls whether constructors and destructors of "container" types
99 Currently, these constructors and destructors are NOT considered for inlining
141 call. (In the case of calls without origin expressions, such as destructors,
193 implicit destructors, or if the destructors for the given object are not
199 or operator 'delete', nor does it inline the constructors and destructors
363 placement of their destructors in the CFG. We currently won't inline their
365 destructors at all, not even to invalidate the region.
[all …]
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines/
H A Dvirtual-class-destructor.rst17 Fixes are available for user-declared and implicit destructors that are either
19 private destructors. There, the decision whether to make them private and
H A Dspecial-member-functions.rst18 This rule is part of the "Constructors, assignments, and destructors" profile of the C++ Core
/llvm-project-15.0.7/clang/test/CodeGenObjC/
H A Dgnustep2-nontrivial-destructor-argument.mm3 // Regression test. Ensure that C++ arguments with non-trivial destructors
/llvm-project-15.0.7/llvm/test/ExecutionEngine/OrcLazy/
H A Dglobal-ctors-and-dtors.ll1 ; Test that global constructors and destructors are run:
6 ; Test that this is true for global constructors and destructors in other
/llvm-project-15.0.7/clang/include/clang/Basic/
H A DTargetCXXABI.def41 /// - constructors and destructors return 'this';
96 /// - constructors and destructors return 'this', as in ARM;
109 /// - constructors and destructors return 'this', as in ARM.
H A DCodeGenOptions.def45 CODEGENOPT(CXAAtExit , 1, 1) ///< Use __cxa_atexit for calling destructors.
46 …egisterGlobalDtorsWithAtExit, 1, 1) ///< Use atexit or __cxa_atexit to register global destructors.
249 ///< destructors are emitted.
/llvm-project-15.0.7/openmp/runtime/test/tasking/hidden_helper_task/
H A Dcommon.h28 kmp_routine_entry_t destructors; member
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/bugprone/
H A Dunused-raii.rst25 - Ignore types with trivial destructors. They are very unlikely to be RAII
/llvm-project-15.0.7/clang/include/clang/StaticAnalyzer/Core/
H A DAnalyzerOptions.def86 "Whether or not implicit destructors for C++ objects "
91 "Whether or not the destructors for C++ temporary "
143 "Whether C++ temporary destructors should be inlined "
144 "during analysis. If temporary destructors are disabled "
146 "temporary destructors would not be inlined anyway.",
492 "Value: \"constructors\", \"destructors\", \"methods\".",
493 "destructors")
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/misc/
H A Dno-recursion.rst20 * The check does not handle C++ destructors
/llvm-project-15.0.7/llvm/test/Transforms/Inline/
H A Dinvoke-cleanup.ll23 ; this call site (PR17872), otherwise C++ destructors will not be
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/modernize/
H A Duse-noexcept.rst60 destructors and delete operators that are ``noexcept(true)`` by
H A Duse-override.rst28 If set to `true`, this check will not diagnose destructors. Default is `false`.
/llvm-project-15.0.7/clang/test/CodeGenOpenCLCXX/
H A Daddrspace-with-class.clcpp5 // for constructors, member functions and destructors.
/llvm-project-15.0.7/llvm/bindings/ocaml/executionengine/
H A Dllvm_executionengine.mli65 (** [run_static_dtors ee] executes the static destructors of each module in
/llvm-project-15.0.7/lld/docs/
H A Dmissingkeyfunction.rst46 key function, but it's quite common because virtual destructors are likely to be
/llvm-project-15.0.7/compiler-rt/lib/builtins/
H A DREADME.txt219 // because there are no catch clauses or destructors to be run. But there
274 // SJLJ for exceptions, each function with a catch clause or destructors needs
/llvm-project-15.0.7/clang/lib/StaticAnalyzer/
H A DREADME.txt123 -cfg-add-implicit-dtors Add C++ implicit destructors to CFGs for all analyses
/llvm-project-15.0.7/clang/docs/
H A DBlock-ABI-Apple.rst860 copied objects with constructor/destructors. The (1<<26) bit is set and
890 and of course the constructors/destructors for ``const`` copied C++ objects.
894 copied objects with constructor/destructors, and again the (1<<26) bit is set
/llvm-project-15.0.7/llvm/docs/HistoricalNotes/
H A D2001-05-18-ExceptionHandling.txt196 llvm. Java would be very similar, except it only uses destructors to unlock
/llvm-project-15.0.7/llvm/lib/Target/AArch64/
H A DAArch64CallingConvention.td401 // Constructors and destructors return 'this' in the iOS 64-bit C++ ABI; since
407 // destructors with 'this' returns, so this RegMask will not be used in that

123