Home
last modified time | relevance | path

Searched refs:allocations (Results 1 – 25 of 53) sorted by relevance

123

/openbsd/gnu/llvm/compiler-rt/lib/hwasan/
H A Dhwasan_flags.inc53 "The number of heap (de)allocations remembered per thread. "
67 // enough, use malloc_bisect_dump to see interesting allocations.
73 "Print all allocations within [malloc_bisect_left, "
/openbsd/gnu/llvm/llvm/docs/
H A DGwpAsan.rst19 key adaptation. Notably, we only choose a very small percentage of allocations
20 to sample, and apply guard pages to these sampled allocations only. The sampling
25 depending on the average size of your allocations.
56 inserting stubs into a supporting allocator to redirect allocations to GWP-ASan
115 slots are randomly reused to guard future allocations.
175 | PerfectlyRightAlign | false | When allocations are right-aligned, should we perfectly al…
182 | MaxSimultaneousAllocations | 16 | Number of simultaneously-guarded allocations available in …
H A DScudoHardenedAllocator.rst44 allocations are surrounded by Guard Pages. It is also configurable via compile
75 resides for Primary backed allocations, or 0 for Secondary backed allocations;
116 reclaiming. While Secondary mapped allocations can be unmapped on deallocation,
129 If using Fuchsia or an Android version greater than 11, your memory allocations
H A DInAlloca.rst96 The rule against allocas between argument allocations and the call site
108 allocations.
H A DAliasAnalysis.rst523 * Distinct globals, stack allocations, and heap allocations can never alias.
524 * Globals, stack allocations, and heap allocations never alias the null pointer.
530 * Function calls can not modify or references stack allocations if they never
H A DJITLink.rst559 allocation. This allows the context to track/hold memory allocations and
655 memory allocations may be one and the same, depending on how the user wants
656 to build their JIT). It also requires that these allocations conform to the
/openbsd/gnu/usr.bin/gcc/gcc/f/
H A Dmalloc.c162 p->name, p->allocated, p->freed, p->old_sizes, p->new_sizes, p->allocations, in malloc_pool_display()
256 p->allocated = p->freed = p->old_sizes = p->new_sizes = p->allocations in malloc_pool_new()
426 pool->allocations++; in malloc_new_inpool_()
H A Dmalloc.h88 unsigned long allocations; member
/openbsd/gnu/llvm/compiler-rt/lib/sanitizer_common/
H A Dsanitizer_malloc_mac.inc101 // FIXME: ASan should support purgeable allocations.
108 // FIXME: ASan should support purgeable allocations. Ignoring them is fine
114 // FIXME: ASan should support purgeable allocations. Ignoring them is fine
H A Dsanitizer_flags.inc144 " This limit does not affect memory allocations other than"
/openbsd/gnu/llvm/compiler-rt/lib/lsan/
H A Dlsan_flags.inc37 "Root set: mark as reachable all allocations made from dynamic "
H A Dlsan_common.cpp932 uptr bytes = 0, allocations = 0; in PrintSummary() local
937 allocations += leaks_[i].hit_count; in PrintSummary()
941 allocations); in PrintSummary()
/openbsd/gnu/llvm/compiler-rt/lib/scudo/standalone/
H A Dwrappers_c.inc259 // Sets whether scudo records stack traces and other metadata for allocations
281 // allocations, before the guard page. This can be enabled to work around buggy
/openbsd/gnu/llvm/compiler-rt/lib/gwp_asan/
H A Doptions.inc27 "Number of simultaneously-guarded allocations available in the "
/openbsd/regress/sys/kern/extent/
H A Dtests40 # last two allocations should succeed without boundary "fixups"
/openbsd/gnu/llvm/clang/docs/
H A DShadowCallStack.rst108 other allocations. Therefore, the address should be chosen to make this
115 memory allocations in certain processes, as this also limits the number of
H A DExternalClangExamples.rst91 memory allocations to misusage of API, including fix-its for automatic
H A DAddressSanitizer.rst302 depends on the allocations sizes. The smaller the allocations you make the
/openbsd/gnu/llvm/llvm/lib/Target/SystemZ/
H A DREADME.txt140 Dynamic stack allocations round the size to 8 bytes and then allocate
/openbsd/gnu/llvm/llvm/docs/CommandGuide/
H A Dllc.rst155 in the function prologue. Functions with dynamic stack allocations are not
/openbsd/gnu/usr.bin/perl/lib/unicore/
H A DBlocks.txt24 # This constraint on block ranges guarantees that allocations
/openbsd/gnu/usr.bin/perl/pod/
H A Dperl5004delta.pod706 a slightly different algorithm for small allocations (up to 64 bytes
708 allocations which are powers of two (and appear quite often).
717 Similarly to C<PACK_MALLOC>, this macro improves allocations of data
718 with size close to a power of two; but this works for big allocations
719 (starting with 16K by default). Such allocations are typical for big
H A Dperlhacktips.pod1846 allocations, also known as "global destruction of objects".
1877 allocations in addition to memory allocations. Each SV allocation has a
1898 memory and SV allocations go through logging functions, which is
1919 Since the logging doesn't use PerlIO, all SV allocations are logged and
1920 no extra SV allocations are introduced by enabling the logging. If
H A Dperldebguts.pod985 The switch was used to track Perl's memory allocations and possible
1032 Perl's malloc() uses bucketed allocations. Every request is rounded
1065 8188-byte allocations.
/openbsd/gnu/llvm/llvm/docs/tutorial/
H A DBuildingAJIT1.rst164 added (a JIT memory manager manages memory allocations, memory permissions, and

123