public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/17780] New: std::allocator vs. static init Date: Fri, 01 Oct 2004 16:48:00 -0000 [thread overview] Message-ID: <20041001164801.17780.bkoz@gcc.gnu.org> (raw) 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
next reply other threads:[~2004-10-01 16:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-01 16:48 bkoz at gcc dot gnu dot org [this message] 2004-10-01 16:48 ` [Bug libstdc++/17780] " bkoz at gcc dot gnu dot org 2004-10-01 16:49 ` bkoz at gcc dot gnu dot org 2004-10-01 16:51 ` bkoz at gcc dot gnu dot org 2004-10-01 16:52 ` pinskia at gcc dot gnu dot org 2004-10-01 17:00 ` bkoz at redhat dot com 2004-10-01 17:05 ` pinskia at gcc dot gnu dot org 2004-10-06 4:22 ` cvs-commit at gcc dot gnu dot org 2004-10-06 16:31 ` cvs-commit at gcc dot gnu dot org 2004-10-28 21:53 ` bkoz at gcc dot gnu dot org 2004-10-28 21:56 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20041001164801.17780.bkoz@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).