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/14273] cosh() returns incorrect results
Date: Thu, 21 Jun 2012 16:37:00 -0000 [thread overview]
Message-ID: <bug-14273-131-vc1j4eVlGo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14273-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14273
--- Comment #5 from Carlos O'Donell <carlos_odonell at mentor dot com> 2012-06-21 16:37:28 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > If the concern is about possibly introducing a new bug, I can see holding off
> > on this. But if it's just that fixing the bug imposes an excessive maintainer's
> > burden due to policy, then what you're effectively saying is that policy tells
> > you to make a buggy release even though you know the change would be safe... To
> > me, that seems like buggy policy.
>
> The policy in this case is to keep the test results from regressing, which is
> an important policy to have for a stable branch. Do we agree on that?
>
> I would accept the patch, but such a patch would have to show it passes on all
> machines that use this code (as opposed to the trunk criteria which would
> probably be less strict), and update ULPs on all of those machines (more strict
> than trunk again). It's a lot of work, but I guess if someone is willing to do
> the work and show the test results, then I see no reason why not to backport
> the patch.
... or just fix the bug and leave out the testcase changes :-)
--
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.
next prev parent reply other threads:[~2012-06-21 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 13:25 [Bug math/14273] New: " pdemarco at maplesoft dot com
2012-06-21 14:27 ` [Bug math/14273] " jsm28 at gcc dot gnu.org
2012-06-21 14:37 ` carlos_odonell at mentor dot com
2012-06-21 15:06 ` bugdal at aerifal dot cx
2012-06-21 16:31 ` carlos_odonell at mentor dot com
2012-06-21 16:37 ` carlos_odonell at mentor dot com [this message]
2012-06-21 19:30 ` jsm28 at gcc dot gnu.org
2012-06-22 3:27 ` bugdal at aerifal dot cx
2012-06-22 13:49 ` carlos_odonell at mentor dot com
2012-06-26 18:55 ` jsm28 at gcc dot gnu.org
2012-06-28 2:25 ` carlos_odonell at mentor dot com
2012-06-28 12:15 ` jsm28 at gcc dot gnu.org
2012-07-03 17:08 ` jsm28 at gcc dot gnu.org
2014-06-13 14:04 ` 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-14273-131-vc1j4eVlGo@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).