| /third_party/python/Misc/ |
| D | README.valgrind | 7 --without-pymalloc.
20 memory leaks, you will need to configure python --without-pymalloc.
25 to the system malloc. Note: configuring python --without-pymalloc
29 about 5 times longer to run --without-pymalloc.
45 PyMalloc when configuring python by adding the --without-pymalloc option.
52 --without-pymalloc usually increases the usefulness of other tools.
67 time, regardless of how many memory areas are under pymalloc's
70 The memory pymalloc manages itself is in one or more "arenas",
72 The base address of each arena is saved by pymalloc
77 Given an arbitrary address, pymalloc computes the pool base
[all …]
|
| D | HISTORY | 6224 - Issue #17228: Fix building without pymalloc.
13119 - Issue #2422: When compiled with the ``--with-valgrind`` option, the pymalloc
13122 advantage of pymalloc at other times.
16938 in order to allow pymalloc to free more arenas. Python may give back
22623 - The optional object allocator ("pymalloc") has been enabled by
25189 allocator can be enabled by providing the "--with-pymalloc" option to
|
| /third_party/python/Doc/c-api/ |
| D | memory.rst | 92 statistics of the :ref:`pymalloc memory allocator <pymalloc>` every time a
93 new pymalloc object arena is created, and on shutdown.
202 :ref:`pymalloc memory allocator <pymalloc>`.
211 The default allocator is now pymalloc instead of system :c:func:`malloc`.
314 :ref:`pymalloc memory allocator <pymalloc>`.
380 Release build ``"pymalloc"`` ``malloc`` ``pymalloc`` `…
381 … ``"pymalloc_debug"`` ``malloc`` + debug ``pymalloc`` + debug ``pymalloc`` + d…
382 Release build, without pymalloc ``"malloc"`` ``malloc`` ``malloc`` `…
383 Debug build, without pymalloc ``"malloc_debug"`` ``malloc`` + debug ``malloc`` + debug `…
391 * ``pymalloc``: :ref:`pymalloc memory allocator <pymalloc>`.
[all …]
|
| D | init_config.rst | 241 * ``PYMEM_ALLOCATOR_PYMALLOC`` (``5``): :ref:`Python pymalloc memory
242 allocator <pymalloc>`.
243 * ``PYMEM_ALLOCATOR_PYMALLOC_DEBUG`` (``6``): :ref:`Python pymalloc
244 memory allocator <pymalloc>` with :ref:`debug hooks
248 not supported if Python is :option:`configured using --without-pymalloc
249 <--without-pymalloc>`.
820 If non-zero, dump statistics on :ref:`Python pymalloc memory allocator
821 <pymalloc>` at exit.
826 the --without-pymalloc option <--without-pymalloc>`.
|
| /third_party/python/Modules/_decimal/tests/ |
| D | runall-memorydebugger.sh | 110 … ./configure CFLAGS="$ADD_CFLAGS" LDFLAGS="$ADD_LDFLAGS" --without-pymalloc $args > /dev/null 2>&1
167 … ./configure CFLAGS="$ADD_CFLAGS" LDFLAGS="$ADD_LDFLAGS" --without-pymalloc $args > /dev/null 2>&1
|
| /third_party/python/Objects/ |
| D | obmalloc.c | 333 PyMemAllocatorEx pymalloc = PYMALLOC_ALLOC; in _PyMem_SetupAllocators() local
334 PyMem_SetAllocator(PYMEM_DOMAIN_MEM, &pymalloc); in _PyMem_SetupAllocators()
335 PyMem_SetAllocator(PYMEM_DOMAIN_OBJ, &pymalloc); in _PyMem_SetupAllocators()
378 PyMemAllocatorEx pymalloc = PYMALLOC_ALLOC; in _PyMem_GetCurrentAllocatorName() local
389 pymemallocator_eq(&_PyMem, &pymalloc) && in _PyMem_GetCurrentAllocatorName()
390 pymemallocator_eq(&_PyObject, &pymalloc)) in _PyMem_GetCurrentAllocatorName()
413 pymemallocator_eq(&_PyMem_Debug.mem.alloc, &pymalloc) && in _PyMem_GetCurrentAllocatorName()
414 pymemallocator_eq(&_PyMem_Debug.obj.alloc, &pymalloc)) in _PyMem_GetCurrentAllocatorName()
|
| /third_party/python/Lib/test/ |
| D | test_cmd_line.py | 753 pymalloc = support.with_pymalloc()
754 if pymalloc:
767 if pymalloc:
|
| /third_party/python/Doc/using/ |
| D | cmdline.rst | 798 * ``pymalloc``: use the :ref:`pymalloc allocator <pymalloc>` for
807 * ``pymalloc_debug``: same as ``pymalloc`` but also install debug hooks.
818 :ref:`pymalloc memory allocator <pymalloc>` every time a new pymalloc object
823 Python is configured without ``pymalloc`` support.
|
| D | configure.rst | 188 .. cmdoption:: --without-pymalloc
190 Disable the specialized Python memory allocator :ref:`pymalloc <pymalloc>`
|
| /third_party/python/Doc/whatsnew/ |
| D | 2.3.rst | 1802 .. _section-pymalloc:
1813 In 2.1 and 2.2, pymalloc was an experimental feature and wasn't enabled by
1815 :option:`!--with-pymalloc` option to the :program:`configure` script. In 2.3,
1816 pymalloc has had further enhancements and is now enabled by default; you'll have
1817 to supply :option:`!--without-pymalloc` to disable it.
1819 This change is transparent to code written in Python; however, pymalloc may
1821 code with pymalloc enabled, because some incorrect code may cause core dumps at
1845 * The "object memory" family is the interface to the pymalloc facility described
1852 Thanks to lots of work by Tim Peters, pymalloc in 2.3 also provides debugging
1868 For the full details of the pymalloc implementation, see the comments at
|
| D | 3.6.rst | 1825 (:c:data:`PYMEM_DOMAIN_MEM`) now use the :ref:`pymalloc memory allocator
1826 <pymalloc>` instead of :c:func:`malloc` function of the C library. The
1827 pymalloc allocator is optimized for objects smaller or equal to 512 bytes
2333 * The :c:func:`PyMem_Malloc` allocator family now uses the :ref:`pymalloc allocator
2334 <pymalloc>` rather than the system :c:func:`malloc`. Applications calling
|
| D | 3.2.rst | 366 debug, "m" for pymalloc, "u" for wide-unicode). For an arbitrary package "foo",
2585 * When compiled with the ``--with-valgrind`` option, the pymalloc
2588 advantage of pymalloc at other times (:issue:`2422`).
|
| D | 2.1.rst | 695 providing the :option:`!--with-pymalloc` option to the :program:`configure`
|
| D | 3.8.rst | 1535 pymalloc became useless (builds with and without pymalloc are ABI compatible)
|
| D | 3.4.rst | 1553 ``--with-pymalloc`` setting, this is allocations made through the
|
| D | 2.6.rst | 1738 by using pymalloc for the Unicode string's data.
|
| D | 2.7.rst | 2246 :option:`!--with-valgrind` option will now disable the pymalloc
|
| /third_party/python/Misc/NEWS.d/ |
| D | 3.8.0a4.rst | 1076 ``./configure --with-pymalloc`` no longer adds the ``m`` flag to SOABI
1077 (sys.implementation.cache_tag). Enabling or disabling pymalloc has no impact
1110 pymalloc memory allocator aligns memory on 8 bytes. On x86-64, clang expects
|
| D | 3.6.0a1.rst | 95 (:c:data:`PYMEM_DOMAIN_MEM`) now use the :ref:`pymalloc allocator
96 <pymalloc>` rather than system :c:func:`malloc`. Applications calling
278 allocators when Python is configured without pymalloc.
|
| D | 3.8.0b1.rst | 387 pymalloc returns memory blocks aligned by 16 bytes, instead of 8 bytes, on
|
| D | 3.9.0a1.rst | 732 Optimized pymalloc for non PGO build.
741 Compute allocated pymalloc blocks inside _Py_GetAllocatedBlocks(). This
|
| /third_party/python/ |
| D | configure.ac | 3573 AC_MSG_CHECKING(for --with-pymalloc)
3574 AC_ARG_WITH(pymalloc, optwith
3575 AS_HELP_STRING([--with-pymalloc], [enable specialized mallocs (default is yes)]))
3613 …[AC_DEFINE([WITH_VALGRIND], 1, [Define if you want pymalloc to be disabled when running under valg…
4818 # Thus for example, Python 3.2 built with wide unicode, pydebug, and pymalloc,
4823 # In Python 3.7 and older, --with-pymalloc added a 'm' flag.
|
| D | pyconfig.h.in | 1586 /* Define if you want pymalloc to be disabled when running under valgrind */
|
| D | configure | 1589 --with-pymalloc enable specialized mallocs (default is yes)
|
| /third_party/python/Doc/library/ |
| D | sys.rst | 20 Default flags became an empty string (``m`` flag for pymalloc has been
|