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++/52015] std::to_string does not work under MinGW Date: Sun, 03 Nov 2013 20:11:00 -0000 [thread overview] Message-ID: <bug-52015-4-DCPCKqoCrE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52015-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52015 --- Comment #31 from Jonathan Wakely <redi at gcc dot gnu.org> --- Or to put it another way, this bug only affects MinGW users, is blocked by a limitation in MinGW, and noone from MinGW has offered to do anything about it, but you're pointing fingers at GCC devs and saying there's a GCC clique? Who is preventing MinGW devs joining this clique? If you want to improve the situation I suggest not throwing around words like abuse, and instead gently correcting misunderstandings by demonstrating that this can indeed be fixed in MinGW. But that fix probably has to come from MinGW.
next prev parent reply other threads:[~2013-11-03 20:11 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-27 9:29 [Bug libstdc++/52015] New: " zeratul976 at hotmail dot com 2012-01-27 10:55 ` [Bug libstdc++/52015] " paolo.carlini at oracle dot com 2012-02-27 17:11 ` zeratul976 at hotmail dot com 2012-02-27 17:21 ` redi at gcc dot gnu.org 2012-02-27 18:07 ` paolo.carlini at oracle dot com 2012-02-27 18:14 ` paolo.carlini at oracle dot com 2012-02-27 18:42 ` ktietz at gcc dot gnu.org 2012-02-27 18:51 ` paolo.carlini at oracle dot com 2012-09-13 17:31 ` eXpl0it3r@my-gate.net 2012-09-13 17:34 ` eXpl0it3r@my-gate.net 2012-09-13 22:15 ` paolo.carlini at oracle dot com 2012-10-23 12:44 ` earnie at users dot sourceforge.net 2012-10-23 13:06 ` manu at gcc dot gnu.org 2012-10-23 13:11 ` redi at gcc dot gnu.org 2012-10-31 11:20 ` redi at gcc dot gnu.org 2012-11-29 14:18 ` ktietz at gcc dot gnu.org 2012-11-29 14:25 ` paolo.carlini at oracle dot com 2012-11-29 14:30 ` ktietz at gcc dot gnu.org 2012-11-29 14:41 ` redi at gcc dot gnu.org 2013-01-05 21:24 ` i.nixman at gmail dot com 2013-01-06 1:44 ` redi at gcc dot gnu.org 2013-01-06 2:08 ` zeratul976 at hotmail dot com 2013-01-06 11:31 ` redi at gcc dot gnu.org 2013-10-21 16:49 ` tom at kera dot name 2013-11-01 8:42 ` matanshukry at gmail dot com 2013-11-01 10:39 ` redi at gcc dot gnu.org 2013-11-03 13:20 ` m8r-iv55ri at mailinator dot com 2013-11-03 13:50 ` paolo.carlini at oracle dot com 2013-11-03 14:00 ` ktietz at gcc dot gnu.org 2013-11-03 14:16 ` m8r-iv55ri at mailinator dot com 2013-11-03 19:55 ` redi at gcc dot gnu.org 2013-11-03 20:11 ` redi at gcc dot gnu.org [this message] 2013-11-04 9:16 ` redi at gcc dot gnu.org 2013-11-11 11:36 ` redi at gcc dot gnu.org 2014-02-26 5:50 ` roman.vasiliev at gmail dot com 2014-02-26 10:00 ` redi at gcc dot gnu.org 2014-02-27 7:16 ` roman.vasiliev at gmail dot com 2014-02-27 7:20 ` roman.vasiliev at gmail dot com 2014-02-27 7:21 ` roman.vasiliev at gmail 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-52015-4-DCPCKqoCrE@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).