public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: paolo@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: libstdc++/8949 Date: Thu, 19 Dec 2002 03:46:00 -0000 [thread overview] Message-ID: <20021219114603.1780.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/8949; it has been noted by GNATS. From: paolo@gcc.gnu.org To: gcc-gnats@gcc.gnu.org Cc: Subject: libstdc++/8949 Date: 19 Dec 2002 11:44:31 -0000 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-3_3-branch Changes by: paolo@gcc.gnu.org 2002-12-19 03:44:31 Modified files: libstdc++-v3 : ChangeLog libstdc++-v3/testsuite/18_support: numeric_limits.cc libstdc++-v3/include/std: std_limits.h Log message: 2002-12-19 Paolo Carlini <pcarlini@unitus.it> PR libstdc++/8949 * include/std/std_limits.h (struct numeric_limits<short>, struct numeric_limits<unsigned short>, struct numeric_limits<int>, struct numeric_limits<unsigned int>, struct numeric_limits<long>, struct numeric_limits<unsigned long>, struct numeric_limits<long long>, struct numeric_limits<unsigned long long>): According to 18.2.1.2,53 and 18.2.1.5,1 is_iec559 shall be false. * testsuite/18_support/numeric_limits.cc: Add test04. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.1464.2.1&r2=1.1464.2.2 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/testsuite/18_support/numeric_limits.cc.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.18&r2=1.18.4.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/include/std/std_limits.h.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.19&r2=1.19.4.1
next reply other threads:[~2002-12-19 11:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-19 3:46 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-16 11:56 libstdc++/8949 paolo
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=20021219114603.1780.qmail@sources.redhat.com \ --to=paolo@gcc.gnu.org \ --cc=gcc-prs@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).