This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/17780] New: std::allocator vs. static init
- From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Oct 2004 16:48:03 -0000
- Subject: [Bug libstdc++/17780] New: std::allocator vs. static init
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
Real QoI issue. First reported here:
http://gcc.gnu.org/ml/libstdc++/2004-07/msg00038.html
Seeing other reports in Red Hat's bugzilla.
This is not a libsupc++ issue, but rather an issue with the default allocator.
For 3.4.0, this is fixed because std::allocator uses new_allocator. However,
current incarnations of __mt_alloc and __pool_alloc have issues.
Working on a fix.
-benjamin
--
Summary: std::allocator vs. static init
Product: gcc
Version: 3.3.3
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bkoz at gcc dot gnu dot org
CC: adah at netstd dot com,gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17780