This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Are these files used anywhere?
- From: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>
- To: libstdc++ at gcc dot gnu dot org
- Cc: pedwards at disaster dot jaj dot com
- Date: Tue, 27 Nov 2001 00:35:20 -0600 (CST)
- Subject: Re: Are these files used anywhere?
- Organization: Networks and Infrastructure Lab (IL02/2240), Motorola Labs
- References: <20011125010847.A28892@disaster.jaj.com>
>> We are currently using the stl_pthread_alloc.h files and underlying
>> implementation to get the best performance in our MT application.
> But you're not using them through the V3 headers, right?
> I think maybe I'll just move them into 'backward' instead of removing
> them altogether.
If you move them, seems that it should be 'ext' not 'backward'.
However, I think promoting the allocator provided by that header to
the same status as __malloc_alloc_template and __new_alloc, etc
>> [...] One idea would be to look into a modification of the standard
>> stl_alloc implementation so that this could be thread aware and
>> tries to do more alignment than it currently does.
stl_pthread_alloc.h uses only those features provided by gthr.h thus
it could be rolled into stl_alloc.h while being de-pthreaded (thread
support would remain just be mapped through the abstraction layer
instead of directly using pthreads - in general as long as you don't
want to start a thread, anything simple pthread can do, gthr.h
supports with the same API).
> Patches welcome. I'm /very/ keen on providing multiple options for users
> to tune memory management. We just need to find a coherent way of doing so.
We are of like mind.