public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/47354] [4.3 Regression] bitmap_allocator free_list::_M_get never locks mutex Date: Wed, 19 Jan 2011 09:54:00 -0000 [thread overview] Message-ID: <bug-47354-4-LOOPN7JhDd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47354-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47354 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.4.6, 4.5.3 Summary|[4.3/4.4/4.5 Regression] |[4.3 Regression] |bitmap_allocator |bitmap_allocator |free_list::_M_get never |free_list::_M_get never |locks mutex |locks mutex --- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-01-19 08:56:51 UTC --- fixed for 4.4.6 and 4.5.3 too
next prev parent reply other threads:[~2011-01-19 8:57 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-18 23:16 [Bug libstdc++/47354] New: " greed at pobox dot com 2011-01-19 0:59 ` [Bug libstdc++/47354] " redi at gcc dot gnu.org 2011-01-19 1:25 ` paolo.carlini at oracle dot com 2011-01-19 1:31 ` redi at gcc dot gnu.org 2011-01-19 1:45 ` paolo.carlini at oracle dot com 2011-01-19 1:49 ` redi at gcc dot gnu.org 2011-01-19 2:27 ` redi at gcc dot gnu.org 2011-01-19 3:31 ` [Bug libstdc++/47354] [4.3/4.4/4.5/4.6 Regression] " redi at gcc dot gnu.org 2011-01-19 3:59 ` redi at gcc dot gnu.org 2011-01-19 4:37 ` [Bug libstdc++/47354] [4.3/4.4/4.5 " redi at gcc dot gnu.org 2011-01-19 9:00 ` redi at gcc dot gnu.org 2011-01-19 9:09 ` redi at gcc dot gnu.org 2011-01-19 9:54 ` redi at gcc dot gnu.org [this message] 2011-01-27 14:44 ` [Bug libstdc++/47354] [4.3 " paolo.carlini at oracle dot com 2011-01-27 15:41 ` greed at pobox dot com
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-47354-4-LOOPN7JhDd@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).