public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/15268] exp (-7.4444006192138124e+02) missing underflow Date: Tue, 03 Dec 2013 00:36:00 -0000 [thread overview] Message-ID: <bug-15268-131-p0ETbU8szJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15268-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15268 Joseph Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Default SET_RESTORE_ROUND |exp |implementation hold |(-7.4444006192138124e+02) |exceptions |missing underflow --- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> --- I don't see that there's a bug in SET_RESTORE_ROUND here; libc_feresetround calls feupdateenv which should cause any exceptions that were raised after SET_RESTORE_ROUND to generate corresponding traps. It looks like the exp call only generates exact underflow but not inexact, even though this is a case of an inexact result; that's a bug in exp (and applies on x86_64 as well). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-12-03 0:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-11 13:35 [Bug math/15268] New: Default SET_RESTORE_ROUND implementation hold exceptions azanella at linux dot vnet.ibm.com 2013-03-11 20:04 ` [Bug math/15268] " azanella at linux dot vnet.ibm.com 2013-12-03 0:36 ` jsm28 at gcc dot gnu.org [this message] 2013-12-03 21:50 ` [Bug math/15268] exp (-7.4444006192138124e+02) missing underflow cvs-commit at gcc dot gnu.org 2013-12-03 21:51 ` jsm28 at gcc dot gnu.org 2014-06-13 10:10 ` fweimer 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=bug-15268-131-p0ETbU8szJ@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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).