This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/18970] 3.4 default memory allocator much slower than 3.3 allocator when large amounts of data are turned over
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Jan 2005 11:09:46 -0000
- Subject: [Bug libstdc++/18970] 3.4 default memory allocator much slower than 3.3 allocator when large amounts of data are turned over
- References: <20041213220807.18970.mj1@cog.brown.edu>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From pcarlini at suse dot de 2005-01-01 11:09 -------
> Yes, although you might want to revert to the 3.3 default allocator, as
> the 3.4 default allocator is considerably slower for large programs.
The default 3.4 ""allocator"", actually just forwards to new/delete. Of course,
there is a reason why we chose it as default: the new allocators we were
working on were not ready in time for 3.4.0; the old one not yet forward
ported to the new framework. The 3.4.x ABI is completely frozen, now, and we
cannot change the default anymore. For the forthcoming 4.0.0, as indicated by
Benjamin, we have a brand new allocator as default, optimized for MT (+ all the
old possibilities)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18970