This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [v3] Mt_alloc: use __bin._M_free[0]

From: Paolo Carlini <pcarlini at suse dot de>
To: Dhruv Matani <dhruvbird at gmx dot net>
Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>
Date: Sun, 16 May 2004 21:57:32 +0200
Subject: Re: [v3] Mt_alloc: use __bin._M_free[0]
References: <40A78650.8010705@suse.de> <1084737983.2045.8.camel@localhost.localdomain>

Dhruv Matani wrote:

Ok, maybe the 2nd one will have these, but just in case.

No, the 2nd one deals with another, completely unrelated issue.

Looking at this part of the code, you could make the operation O(1), if the number of free blocks in the global free list is <= those required. Just reset the pointer to NULL for the global list, and set the next pointer of the current free list to the one of the global free list's old value.

I see what you mean: nice idea. Are you willing to prepare and test
a patch implementing this?

Thanks,
Paolo.

Follow-Ups:
- Re: [v3] Mt_alloc: use __bin._M_free[0]
  - From: Dhruv Matani
- Re: [v3] Mt_alloc: use __bin._M_free[0]
  - From: Dhruv Matani

References:
- [v3] Mt_alloc: use __bin._M_free[0]
  - From: Paolo Carlini
- Re: [v3] Mt_alloc: use __bin._M_free[0]
  - From: Dhruv Matani

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]