Skip to content

[3.7] bpo-37732: Fix GCC warning in _PyObject_Malloc() (GH-15333) (GH-15342) #15343

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 20, 2019
Merged

[3.7] bpo-37732: Fix GCC warning in _PyObject_Malloc() (GH-15333) (GH-15342) #15343

merged 1 commit into from
Aug 20, 2019

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Aug 20, 2019 •
edited by bedevere-bot
Loading

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

@vstinner
bpo-37732: Fix GCC warning in _PyObject_Malloc() (GH-15333) (GH-15342)
a410f02 
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)
@bedevere-bot bedevere-bot mentioned this pull request Aug 20, 2019
Merged
@vstinner vstinner merged commit c9a484a into python:3.7 Aug 20, 2019
@vstinner vstinner deleted the pymalloc_alloc_warn37 branch August 20, 2019 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
skip news
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@vstinner @the-knights-who-say-ni @bedevere-bot