public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alasdairrr at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/41495] libstdc++ --enable-clocale=ieee_1003.1-2001 fails Date: Mon, 23 May 2011 19:08:00 -0000 [thread overview] Message-ID: <bug-41495-4-7wEVBrxWeR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-41495-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41495 --- Comment #10 from Alasdair Lumsden <alasdairrr at gmail dot com> 2011-05-23 18:36:29 UTC --- (In reply to comment #9) > I only work on libstdc++ in my spare time and I lack the time, not the > motivation :) Alrighty! > There are some others who expressed an interest in improving the locale code > for Darwin and they might be interested. See the libstdc++ mailing list > archives for December 2010, January, February and May 2011 for various threads > on the subject. I'll check this out, thanks for the info. > > > I think a better long term plan is to write a new locale model based on the > > > POSIX 2008 API, as that could be common to more platforms and would provide > > > thread-safety and the other advantages of the GNU/Linux code. > > > > Would this be a significant volume of work? > > I don't *think* so, the GNU locale model already uses those APIs as they've > been in glibc for ages, so a good starting point would be copying the GNU code > and fixing it up a bit to replace anything GNU-specific with the POSIX.1-2008 > equivalent. Someone already started doing that for Darwin earlier this month. Great, again thanks for the info. I'll make contact with the darwin folks. Cheers, Alasdair
next prev parent reply other threads:[~2011-05-23 19:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-41495-4@http.gcc.gnu.org/bugzilla/> 2011-03-19 22:15 ` paolo.carlini at oracle dot com 2011-03-20 15:30 ` redi at gcc dot gnu.org 2011-05-20 16:54 ` alasdairrr at gmail dot com 2011-05-20 18:02 ` redi at gcc dot gnu.org 2011-05-23 14:10 ` alasdairrr at gmail dot com 2011-05-23 16:45 ` redi at gcc dot gnu.org 2011-05-23 19:08 ` alasdairrr at gmail dot com [this message] 2014-08-17 17:43 ` vhaisman at gmail dot com 2024-04-16 11:33 ` redi at gcc dot gnu.org 2009-09-28 23:28 [Bug libstdc++/41495] New: " ian at airs dot com 2009-09-29 18:09 ` [Bug libstdc++/41495] " ro at gcc dot gnu dot org 2009-10-02 17:46 ` ro at gcc dot gnu dot org 2009-10-02 17:48 ` ro 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=bug-41495-4-7wEVBrxWeR@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).