Re: g_malloc overhead

2009-01-22 Thread Maciej Piechotka
Martín Vales writes: > hi: > > I working with visual c++ in Windows and i find glib very useful for > many C task, but i am worry about the g_malloc overhead. > > We really need a new malloc?? > > gpointer > g_malloc (gsize n_bytes) > { > if (G_UNLIKELY (!g_mem_initialized)) >g_mem_init_nome

Re: examples/list.c

2009-01-22 Thread Brian J. Tarricone
Hi Deron, Please don't reply to me directly. The entire list should be able to benefit from this discussion. Deron Kazmaier wrote: I'm sure he know that, but is it available or not? I would think it should still be functional otherwise it would not be binary compatible with existing applic

Re: g_malloc overhead

2009-01-22 Thread BJörn Lindqvist
2009/1/21 Liam R E Quin : > On Mon, 2009-01-19 at 18:43 +0100, BJörn Lindqvist wrote: >> Actually, a custom allocator could be useful even in the general case. >> Malloc is a system call and has quite bad performance on certain >> platforms (windows in particular i think). Something like the gslice