| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
(GH-123827) (#123875)
gh-123826: Fix unused function warnings in mimalloc on NetBSD (GH-123827)
(cherry picked from commit 4a6b1f179667e2a8c6131718eb78a15f726e047b)
Co-authored-by: Furkan Onder <furkanonder@protonmail.com>
|
| |
|
|
|
| |
(cherry picked from commit d005f2c1861dbf0ab3d9f80b54d05d0c0b522c3c)
Co-authored-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
|
| | |
|
| |
|
| |
Signed-off-by: cui fliter <imcusg@gmail.com>
|
| | |
|
| |
|
|
| |
(#112807)
|
| |
|
|
|
|
|
| |
gh-112027: Don't print mimalloc warning after mmap
This changes the warning to a "verbose"-level message in prim.c. The
address passed to mmap is only a hint -- it's normal for mmap() to
sometimes not respect the hint and return a different address.
|
| |
|
| |
Fix `unused function` warnings during mimalloc build on FreeBSD.
|
| | |
|
| |
|
| |
Include <unistd.h> to get sbrk() function.
|
|
|
* Add mimalloc v2.12
Modified src/alloc.c to remove include of alloc-override.c and not
compile new handler.
Did not include the following files:
- include/mimalloc-new-delete.h
- include/mimalloc-override.h
- src/alloc-override-osx.c
- src/alloc-override.c
- src/static.c
- src/region.c
mimalloc is thread safe and shares a single heap across all runtimes,
therefore finalization and getting global allocated blocks across all
runtimes is different.
* mimalloc: minimal changes for use in Python:
- remove debug spam for freeing large allocations
- use same bytes (0xDD) for freed allocations in CPython and mimalloc
This is important for the test_capi debug memory tests
* Don't export mimalloc symbol in libpython.
* Enable mimalloc as Python allocator option.
* Add mimalloc MIT license.
* Log mimalloc in Lib/test/pythoninfo.py.
* Document new mimalloc support.
* Use macro defs for exports as done in:
https://github.com/python/cpython/pull/31164/
Co-authored-by: Sam Gross <colesbury@gmail.com>
Co-authored-by: Christian Heimes <christian@python.org>
Co-authored-by: Victor Stinner <vstinner@python.org>
|
