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++/42491] performance/30_threads/future/polling.cc fails at compile time Date: Wed, 06 Jan 2010 22:58:00 -0000 [thread overview] Message-ID: <20100106225811.26579.qmail@sourceware.org> (raw) In-Reply-To: <bug-42491-16141@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from bkoz at gcc dot gnu dot org 2010-01-06 22:58 ------- Sure. We can fix this by adding -std=gnu++0x for all compiles, and then marking up the testcase appropriately. Sadly, this results in widespread observance of: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42634 These are in the pb_ds test cases. However, once that is fixed this will be all taken care of. -- bkoz at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |bkoz at gcc dot gnu dot org |dot org | Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2010-01-06 22:58:11 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42491
next prev parent reply other threads:[~2010-01-06 22:58 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-24 16:06 [Bug libstdc++/42491] New: " paolo dot carlini at oracle dot com 2010-01-06 22:56 ` [Bug libstdc++/42491] " bkoz at gcc dot gnu dot org 2010-01-06 22:58 ` bkoz at gcc dot gnu dot org [this message] 2010-01-06 22:58 ` bkoz at gcc dot gnu dot org 2010-01-06 23:46 ` paolo dot carlini at oracle dot com 2010-01-14 16:34 ` paolo dot carlini at oracle 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=20100106225811.26579.qmail@sourceware.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).