public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/7753: Problems with <limit> (signaling_Nan()) Date: Wed, 28 Aug 2002 17:46:00 -0000 [thread overview] Message-ID: <20020829004601.16317.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/7753; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de> Cc: gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/7753: Problems with <limit> (signaling_Nan()) Date: 29 Aug 2002 02:32:50 +0200 Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de> writes: | System: Linux kiste 2.4.18 #8 Sat Mar 9 15:33:15 CET 2002 i686 unknown | Architecture: i686 | 2.13.90.0.3 20020809 | host: i686-pc-linux-gnu | build: i686-pc-linux-gnu | target: i686-pc-linux-gnu | configured with: ../gcc/configure --enable-shared --disable-nls --enable-threads=posix --enable-languages=c,c++,f77,objc --enable-__cxa_atexit | >Description: | gcc does not compile the file tnan.C. There are problems with the | functions returning the representations of SNANs, QNANs and | Infinity. This is odd, because I'm also using such an architecture and I'm not seeing the failure you're reporting. I have: % as --version GNU assembler 2.12.90 20020707 and % ld --version GNU ld version 2.12.90 20020707 % nm libstdc++.so | c++filt| grep _float_ 00099298 R std::__glibcpp_float_QNaN 0009929c R std::__glibcpp_float_SNaN 00099294 R std::__glibcpp_float_infinity 000992a0 R std::__glibcpp_float_denorm_min % nm libstdc++.so | c++filt| grep _double_ 000992b0 R std::__glibcpp_double_QNaN 000992b8 R std::__glibcpp_double_SNaN 000992a8 R std::__glibcpp_double_infinity 000992d4 R std::__glibcpp_long_double_QNaN 000992e0 R std::__glibcpp_long_double_SNaN 000992c0 R std::__glibcpp_double_denorm_min 000992c8 R std::__glibcpp_long_double_infinity 000992ec R std::__glibcpp_long_double_denorm_min What do you get? -- Gaby
next reply other threads:[~2002-08-29 0:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-28 17:46 Gabriel Dos Reis [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-09 18:26 ljrittle 2002-08-29 3:46 Gabriel Dos Reis 2002-08-29 2:06 Peter Schmid 2002-08-28 17:46 Peter Schmid
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=20020829004601.16317.qmail@sources.redhat.com \ --to=gdr@integrable-solutions.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).