Re: [PATCH] [ping] Use single shared memory block pool for all pool allocators

2015-09-15 Thread Mikhail Maltsev
On 08/31/2015 02:44 PM, Richard Biener wrote: > Apart from Richards comments: > > +/* Return UNCAST_BLOCK to pool. */ > +inline void > +memory_block_pool::remove (void *uncast_block) > +{ > + block_list *block = reinterpret_cast (uncast_block); > + block->m_next = instance.m_blocks; > + instan

Re: [PATCH] [ping] Use single shared memory block pool for all pool allocators

2015-08-31 Thread Richard Biener
On Mon, Aug 17, 2015 at 8:44 AM, Mikhail Maltsev wrote: > Hi, all. > I'm pinging this patch: > https://gcc.gnu.org/ml/gcc-patches/2015-08/msg00030.html > > And adding some more changes to it (they are not complete yet - so they are > more > like an RFC). > In this patch I also try to make obstac

Re: [PATCH] [ping] Use single shared memory block pool for all pool allocators

2015-08-25 Thread Richard Sandiford
Mikhail Maltsev writes: > Hi, all. > I'm pinging this patch: > https://gcc.gnu.org/ml/gcc-patches/2015-08/msg00030.html A week and no reply, so FWIW: I really hope this goes in. malloc always shows up high in my profiles too. Just a couple of very minor things to show that I read the patch :-)

[PATCH] [ping] Use single shared memory block pool for all pool allocators

2015-08-16 Thread Mikhail Maltsev
Hi, all. I'm pinging this patch: https://gcc.gnu.org/ml/gcc-patches/2015-08/msg00030.html And adding some more changes to it (they are not complete yet - so they are more like an RFC). In this patch I also try to make obstacks use the same block pool as object pools. This seems rather easy to impl