public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjmunroe at us dot ibm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug math/5768] New: isnan() will throw SIGFPE with signalling NaN Date: Mon, 18 Feb 2008 23:05:00 -0000 [thread overview] Message-ID: <20080218230428.5768.sjmunroe@us.ibm.com> (raw) On powerpc the default implementation uses: savedstate = fegetenv_register (); reset_fpscr_bit (FPSCR_VE); result = !(x == x); fesetenv_register (savedstate); return result; But with GCC-4.1+ there is no dependency to prevent GCC from moving the fesetenv_register() [mtfsf] ahead of the (x==x) [fcmpu f1,f1]. In the default mode this is not a problem. but if FE_INVALID is enabled and a signaling NaN is passed to isnan() we will get a SIGFPE. -- Summary: isnan() will throw SIGFPE with signalling NaN Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P3 Component: math AssignedTo: aj at suse dot de ReportedBy: sjmunroe at us dot ibm dot com CC: glibc-bugs at sources dot redhat dot com GCC build triplet: powerpc64-*-linux GCC host triplet: powerpc64-*-linux GCC target triplet: powerpc64-*-linux and powerpc-*-linux http://sourceware.org/bugzilla/show_bug.cgi?id=5768 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2008-02-18 23:05 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-18 23:05 sjmunroe at us dot ibm dot com [this message] 2008-02-18 23:08 ` [Bug math/5768] " sjmunroe at us dot ibm dot com 2008-02-18 23:12 ` sjmunroe at us dot ibm dot com 2008-02-18 23:21 ` sjmunroe at us dot ibm dot com 2008-02-22 21:38 ` sjmunroe at us dot ibm dot com 2008-04-10 14:18 ` drepper at redhat 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=20080218230428.5768.sjmunroe@us.ibm.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).