[3.7] bpo-37732: Fix GCC warning in _PyObject_Malloc() (GH-15333) (GH-15342)#15343
Merged
vstinner merged 1 commit intopython:3.7from Aug 20, 2019
vstinner:pymalloc_alloc_warn37
Merged
[3.7] bpo-37732: Fix GCC warning in _PyObject_Malloc() (GH-15333) (GH-15342)#15343vstinner merged 1 commit intopython:3.7from vstinner:pymalloc_alloc_warn37
vstinner merged 1 commit intopython:3.7from
vstinner:pymalloc_alloc_warn37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
pymalloc_alloc() now returns directly the pointer, return NULL on
memory allocation error.
allocate_from_new_pool() already uses NULL as marker for "allocation
failed".
(cherry picked from commit 18f8dcf)
(cherry picked from commit 30e5aff)
https://bugs.python.org/issue37732