luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-24 11:12:11 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'system-alloc' into 'master'

Browse Source 
gmem: clarify that g_malloc always uses the system allocator

See merge request GNOME/glib!1099
This commit is contained in:
Sebastian Dröge 2019-09-16 13:50:22 +00:00
commit 96a1e35e62
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
glib/gmem.c
View File

@ -77,6 +77,9 @@ static GMemVTable glib_mem_vtable = {
* new with delete and new[] with delete[]. Otherwise bad things can happen,
* since these allocators may use different memory pools (and new/delete call
* constructors and destructors).
*
* Since GLib 2.46 g_malloc() is hardcoded to always use the system malloc
* implementation.
*/
/* --- functions --- */
@ -457,7 +460,7 @@ g_try_realloc_n (gpointer mem,
*
* Checks whether the allocator used by g_malloc() is the system's
* malloc implementation. If it returns %TRUE memory allocated with
* malloc() can be used interchangeable with memory allocated using g_malloc().
* malloc() can be used interchangeably with memory allocated using g_malloc().
* This function is useful for avoiding an extra copy of allocated memory returned
* by a non-GLib-based API.
*