public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos_odonell at mentor dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug math/14048] fmod() incorrectly returns NaN for (some?) denormalized inputs
Date: Mon, 25 Jun 2012 22:22:00 -0000	[thread overview]
Message-ID: <bug-14048-131-mydLkDF73b@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14048-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14048

--- Comment #11 from Carlos O'Donell <carlos_odonell at mentor dot com> 2012-06-25 22:22:18 UTC ---
(In reply to comment #10)
> On Mon, 25 Jun 2012, carlos_odonell at mentor dot com wrote:
> 
> > Shall we drop the testsuite addition from the backport?
> 
> The most conservative backport would be just patch 1/3, without the 
> testsuite addition - 1/3 is fixing the regression in 2.15 (a regression 
> introduced by the addition of the wordsize-64 version), the other patches 
> are fixing a failure that showed up for powerpc with the new testcases but 
> as far as I know that powerpc failure is not a regression.

The Power failure is still a failure and should be fixed.

Please checkin all three patches *without* the testsuite addition.

I want to avoid people working with a stable branch having testsuite failures
show up out of thin air because we fixed a bug. That's OK for trunk, but not OK
for a stable branch. The new testsuite failure is difficult and time-consuming
for non-experts to diagnose. We hide this by fixing the bug, and using the
regression test to verify the fix, but then dropping the testcase from the
backport.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-06-25 22:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02  9:10 [Bug math/14048] New: " jkummerow at chromium dot org
2012-05-02 15:32 ` [Bug math/14048] " bugdal at aerifal dot cx
2012-05-03 20:39 ` jkummerow at chromium dot org
2012-06-01 19:10 ` jsm28 at gcc dot gnu.org
2012-06-02 12:56 ` jkummerow at chromium dot org
2012-06-08 10:35 ` jsm28 at gcc dot gnu.org
2012-06-25 21:39 ` jsm28 at gcc dot gnu.org
2012-06-25 21:41 ` jsm28 at gcc dot gnu.org
2012-06-25 21:43 ` jsm28 at gcc dot gnu.org
2012-06-25 21:52 ` carlos_odonell at mentor dot com
2012-06-25 22:09 ` joseph at codesourcery dot com
2012-06-25 22:22 ` carlos_odonell at mentor dot com [this message]
2012-06-25 23:16 ` jsm28 at gcc dot gnu.org
2014-02-16 19:32 ` jackie.rosen at hushmail dot com
2014-05-28 19:46 ` schwab at sourceware dot org
2014-06-25 11:08 ` 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-14048-131-mydLkDF73b@http.sourceware.org/bugzilla/ \
    --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: 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).