public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/39802] std::num_get fails to parse negative zero input correctly Date: Sat, 18 Apr 2009 19:29:00 -0000 [thread overview] Message-ID: <20090418192854.3275.qmail@sourceware.org> (raw) In-Reply-To: <bug-39802-17593@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from paolo at gcc dot gnu dot org 2009-04-18 19:28 ------- Subject: Bug 39802 Author: paolo Date: Sat Apr 18 19:28:40 2009 New Revision: 146323 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=146323 Log: 2009-04-18 Paolo Carlini <paolo.carlini@oracle.com> PR libstdc++/39802 * include/bits/locale_facets.tcc (num_get<>::_M_extract_int (_InIter, _InIter, ios_base&, ios_base::iostate&, _ValueT&)): Always accept negative values, for unsigned types too. * testsuite/22_locale/num_get/get/char/39802.cc: New. * testsuite/22_locale/num_get/get/wchar_t/39802.cc: Likewise. Added: trunk/libstdc++-v3/testsuite/22_locale/num_get/get/char/39802.cc trunk/libstdc++-v3/testsuite/22_locale/num_get/get/wchar_t/39802.cc Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/bits/locale_facets.tcc -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39802
next prev parent reply other threads:[~2009-04-18 19:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-17 22:26 [Bug libstdc++/39802] New: std::num_get fails to pase " ritter at roguewave dot com 2009-04-18 1:17 ` [Bug libstdc++/39802] std::num_get fails to parse " paolo dot carlini at oracle dot com 2009-04-18 19:29 ` paolo at gcc dot gnu dot org [this message] 2009-04-18 19:31 ` paolo dot carlini at oracle dot com 2009-04-21 20:27 ` paolo at gcc dot gnu dot org 2009-04-21 20:27 ` 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=20090418192854.3275.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).