public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51673] undefined references / libstdc++-7.dll Date: Sat, 24 Dec 2011 15:55:00 -0000 [thread overview] Message-ID: <bug-51673-4-DsLuwy2QPW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51673-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51673 --- Comment #3 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-12-24 14:37:23 UTC --- I don't have a strong opinion, but it's a bit hard to make a choice: the legacy HP/SGI pool still makes sense; mt too, has some problems, but we spent quite a bit of time on it, works decently well in a few circumstances (still, I have to tell Pawel, enabling it as default allocator isn't something one should do with light heart); bitmap I would not include, actually I would deprecate and remove it completely, you know that already.
next prev parent reply other threads:[~2011-12-24 14:37 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-24 13:02 [Bug libstdc++/51673] New: " pluto at agmk dot net 2011-12-24 13:37 ` [Bug libstdc++/51673] " paolo.carlini at oracle dot com 2011-12-24 14:12 ` redi at gcc dot gnu.org 2011-12-24 15:55 ` paolo.carlini at oracle dot com [this message] 2011-12-27 9:41 ` pluto at agmk dot net 2011-12-27 10:42 ` paolo.carlini at oracle dot com 2011-12-28 16:20 ` pluto at agmk dot net 2011-12-28 19:54 ` pluto at agmk dot net 2011-12-28 22:06 ` ktietz at gcc dot gnu.org 2012-01-09 23:41 ` bkoz at gcc dot gnu.org 2012-01-09 23:42 ` bkoz at gcc dot gnu.org 2012-01-10 19:56 ` pluto at agmk dot net 2012-03-04 19:36 ` pluto at agmk dot net 2012-03-06 11:49 ` ktietz at gcc dot gnu.org 2012-03-06 18:36 ` pluto at agmk dot net 2012-03-06 18:44 ` redi at gcc dot gnu.org 2012-03-06 20:19 ` joseph at codesourcery dot com 2012-03-06 21:04 ` pluto at agmk dot net 2012-03-22 22:19 ` pluto at agmk dot net
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=bug-51673-4-DsLuwy2QPW@http.gcc.gnu.org/bugzilla/ \ --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).