This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug math/14273] cosh() returns incorrect results
- From: "carlos_odonell at mentor dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Thu, 21 Jun 2012 16:37:28 +0000
- Subject: [Bug math/14273] cosh() returns incorrect results
- Auto-submitted: auto-generated
- References: <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.