public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, sbeasley@cs.uic.edu Subject: Re: libstdc++/7920: std::numeric_limits<char>::digits10 is incorrect (7, not 3) Date: Sun, 29 Sep 2002 00:44:00 -0000 [thread overview] Message-ID: <20020929074440.10793.qmail@sources.redhat.com> (raw) Synopsis: std::numeric_limits<char>::digits10 is incorrect (7, not 3) State-Changed-From-To: open->analyzed State-Changed-By: paolo State-Changed-When: Sun Sep 29 00:44:39 2002 State-Changed-Why: This is already fixed for 3.3. Confirmed, but not a regression, for 3.2. The correct value, however, is 2 not 3, since - according to 18.2.1.2,9 - digits10 is "number of base10 digits that can be represented without change" and definitely for char on your system this is impossible for, say, 500! http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7920
next reply other threads:[~2002-09-29 7:44 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-29 0:44 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-11 13:21 gdr 2002-09-14 20:46 sbeasley
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=20020929074440.10793.qmail@sources.redhat.com \ --to=paolo@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=sbeasley@cs.uic.edu \ /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).