Bug 130219 - gcc / libstdc++ allocator
Summary: gcc / libstdc++ allocator
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michael Matz
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-24 05:29 UTC by Dirk Mueller
Modified: 2005-10-24 09:28 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Mueller 2005-10-24 05:29:47 UTC 
Hi,   
  
it seems some distributions configure with  --enable-libstdcxx-allocator=mt.  
apparently this is to speed up highly memory intensive / multithreaded C++  
apps (OOffice?). dunno actual numbers offhand. 
  
did we think about this?
Comment 1 Paolo Carlini 2005-10-24 09:02:24 UTC 
(In reply to comment #0)

> did we think about this?

It is not an option, according to our policy wrt binary compatibility: we 
even have a PR about this, libstdc++/21072, which includes a straightforward testcase: basically you cannot allocate with an allocator and deallocate with
a different one.

Those distributions broke binary compatibility. We want to do that?

Also, in retrospect, we are "lucky" because that allocator is still not
stable (see libstdc++/22309, 23591, 24469) and is affected by most of the
usual problems of pooled allocators - e.g., memory is not released until
the exit of the program - we discussed that on the list and we don't want
it by default if only because of this.
Comment 2 Dirk Mueller 2005-10-24 09:28:02 UTC 
ok, then, I guess.