This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.
- From: bkoz at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tot at trema dot com
- Date: 28 Mar 2002 22:47:10 -0000
- Subject: Re: libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.
- Reply-to: bkoz at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, tot at trema dot com, gcc-gnats at gcc dot gnu dot org
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