public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zimmerma+gcc at loria dot fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/16353] expm1 missing underflows
Date: Fri, 07 Feb 2014 14:35:00 -0000 [thread overview]
Message-ID: <bug-16353-131-C5pPGb9miJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16353-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16353
Paul Zimmermann <zimmerma+gcc at loria dot fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|expm1 missing/spurious |expm1 missing underflows
|underflows |
--- Comment #6 from Paul Zimmermann <zimmerma+gcc at loria dot fr> ---
(In reply to joseph@codesourcery.com from comment #5)
> Missing and spurious underflows are separate bugs, please restore this bug
> to its original scope and file a separate bug for the spurious underflow.
sorry, done, new bug for spurious underflow is 16539
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-07 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 18:09 [Bug math/16353] New: " jsm28 at gcc dot gnu.org
2014-01-29 11:48 ` [Bug math/16353] " zimmerma+gcc at loria dot fr
2014-01-29 16:38 ` joseph at codesourcery dot com
2014-01-29 16:46 ` zimmerma+gcc at loria dot fr
2014-02-07 7:54 ` [Bug math/16353] expm1 missing/spurious underflows zimmerma+gcc at loria dot fr
2014-02-07 14:35 ` zimmerma+gcc at loria dot fr [this message]
2014-06-13 11:23 ` [Bug math/16353] expm1 missing underflows fweimer at redhat dot com
2014-06-23 20:21 ` cvs-commit at gcc dot gnu.org
2014-06-24 21:01 ` cvs-commit at gcc dot gnu.org
2015-06-22 21:07 ` cvs-commit at gcc dot gnu.org
2015-06-22 21:07 ` jsm28 at gcc dot gnu.org
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-16353-131-C5pPGb9miJ@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: link
Be 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).