public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	tot@trema.com
Subject: Re: libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.
Date: Thu, 28 Mar 2002 14:47:00 -0000	[thread overview]
Message-ID: <20020328224710.14327.qmail@sources.redhat.com> (raw)

Synopsis: 3.1 pre libstdc++ number formatting is not mt-safe.

State-Changed-From-To: suspended->analyzed
State-Changed-By: bkoz
State-Changed-When: Thu Mar 28 14:47:09 2002
State-Changed-Why:
    Note that this is not a new problem. Before this, LANG settings that were not "C" would cause input to fail, unconditionally.
    
    The current code path is not optimal, admittedly. Tricks in the "C" library in the glibc-2.3 timeframe will remove this issue from impacting modern linux systems.
    
    All that is really needed here is some kind of hard-wired "C" locale strtold/sscanf function. Or, some elimination of this step (long threatened by some contributors.)
    
    I believe this defficiency can be improved in the future, without breaking the ABI, so this is really not "critical" to me. Can I downgrade this to serios with low priority?
    
    thanks,
    benjamin
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6015


             reply	other threads:[~2002-03-28 22:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-28 14:47 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-07 15:02 paolo
2002-04-01 11:12 bkoz
2002-03-23  6:37 paolo
2002-03-20  5:16 tot

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=20020328224710.14327.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=tot@trema.com \
    /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: link
Be 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).