bpo-40602: _Py_hashtable_new() uses PyMem_Malloc()#20046
Merged
vstinner merged 1 commit intopython:masterfrom May 12, 2020
vstinner:hashtable_alloc
Merged
bpo-40602: _Py_hashtable_new() uses PyMem_Malloc()#20046vstinner merged 1 commit intopython:masterfrom vstinner:hashtable_alloc
vstinner merged 1 commit intopython:masterfrom
vstinner:hashtable_alloc
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
_Py_hashtable_new() now uses PyMem_Malloc/PyMem_Free allocator by
default, rather than PyMem_RawMalloc/PyMem_RawFree.
PyMem_Malloc is faster than PyMem_RawMalloc for memory blocks smaller
than or equal to 512 bytes.
https://bugs.python.org/issue40602