public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/14412] Removal of sysdeps/x86_64/fpu/s_sincos.S causes regressions Date: Fri, 26 Apr 2013 15:07:00 -0000 [thread overview] Message-ID: <bug-14412-131-K4ir4mPv51@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14412-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14412 --- Comment #23 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2013-04-26 15:07:02 UTC --- It's only a limited subset of transcendental functions for which glibc is trying to be correctly rounding, and only for double for those functions; for most functions the aim is generally errors within "a few" ulps (and ISO C doesn't specify particular accuracy requirements), though correctly rounding would be some sort of ideal. Implementing the proposed TS 18661 bindings to IEEE 754-2008 would be a huge amount of work (and require compiler work as well), but if anyone gets the time for that work then I believe part 4 of the draft TS will reserve names such as crsin for correctly rounding functions (and crsinf128 for correctly rounding sine for _Float128, etc.), without requiring those functions, so it might make sense eventually to provide those names for correctly-rounding functions where available without making them the default versions. So far I'm still working on going through the accumulated libm bugs that don't require such huge amounts of work as DTS 18661 or ISO 24747 implementation - where one reported bug often shows up lots of related bugs not previously in Bugzilla, that also need to be fixed - rather than trying to find time for larger libm projects (and I'm also mostly leaving aside libm bugs in areas where others have shown interest in fixing them, such as performance or errno handling). (The present functions, producing correctly-rounded results only for round-to-nearest, would not of course meet the requirements for functions such as crsin, although it's probably possible to adapt them by just doing a little bit of final arithmetic in the original rounding mode, having done the intermediate computations to produce a higher-precision result in round-to-nearest.) -- 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:[~2013-04-26 15:07 UTC|newest] Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-26 21:08 [Bug math/14412] New: Removal of sysdeps/x86_64/fpu/s_sincos.S causes pdf rendering time regression markus at trippelsdorf dot de 2012-07-26 21:09 ` [Bug math/14412] " markus at trippelsdorf dot de 2012-07-26 21:14 ` markus at trippelsdorf dot de 2012-07-27 6:44 ` aj at suse dot de 2012-07-27 7:18 ` markus at trippelsdorf dot de 2012-07-27 12:33 ` markus at trippelsdorf dot de 2012-07-28 22:15 ` bugdal at aerifal dot cx 2012-08-03 3:51 ` carlos_odonell at mentor dot com 2012-08-09 10:14 ` markus at trippelsdorf dot de 2012-08-19 9:31 ` markus at trippelsdorf dot de 2012-08-19 9:37 ` [Bug math/14412] Removal of sysdeps/x86_64/fpu/s_sincos.S causes regressions markus at trippelsdorf dot de 2012-12-03 22:13 ` davem at davemloft dot net 2012-12-04 0:00 ` carlos at systemhalted dot org 2013-04-25 21:48 ` wbrana at gmail dot com 2013-04-25 23:35 ` carlos at redhat dot com 2013-04-25 23:58 ` bugdal at aerifal dot cx 2013-04-26 0:14 ` bugdal at aerifal dot cx 2013-04-26 2:55 ` siddhesh at redhat dot com 2013-04-26 3:08 ` bugdal at aerifal dot cx 2013-04-26 3:50 ` siddhesh at redhat dot com 2013-04-26 6:29 ` markus at trippelsdorf dot de 2013-04-26 6:40 ` jakub at redhat dot com 2013-04-26 10:00 ` siddhesh at redhat dot com 2013-04-26 11:31 ` joseph at codesourcery dot com 2013-04-26 11:33 ` joseph at codesourcery dot com 2013-04-26 11:42 ` siddhesh at redhat dot com 2013-04-26 13:52 ` bugdal at aerifal dot cx 2013-04-26 13:55 ` bugdal at aerifal dot cx 2013-04-26 15:07 ` joseph at codesourcery dot com [this message] 2013-04-26 15:20 ` wbrana at gmail dot com 2013-04-29 10:29 ` siddhesh at redhat dot com 2013-04-29 10:50 ` wbrana at gmail dot com 2013-04-29 11:55 ` bugdal at aerifal dot cx 2013-04-29 12:32 ` wbrana at gmail dot com 2013-04-29 13:21 ` Ondřej Bílka 2013-04-29 13:21 ` neleai at seznam dot cz 2013-04-29 13:28 ` bugdal at aerifal dot cx 2013-04-29 14:04 ` Ondřej Bílka 2013-04-29 13:32 ` bugdal at aerifal dot cx 2013-04-29 13:36 ` wbrana at gmail dot com 2013-04-29 13:44 ` siddhesh at redhat dot com 2013-04-29 13:51 ` bugdal at aerifal dot cx 2013-04-29 14:04 ` neleai at seznam dot cz 2013-04-29 14:19 ` siddhesh at redhat dot com 2013-04-29 14:29 ` markus at trippelsdorf dot de 2013-04-29 14:48 ` bugdal at aerifal dot cx 2013-04-29 16:29 ` Ondřej Bílka 2013-04-29 16:29 ` neleai at seznam dot cz 2013-04-29 17:30 ` bugdal at aerifal dot cx 2013-04-29 20:58 ` joseph at codesourcery dot com 2013-04-30 5:41 ` siddhesh at redhat dot com 2013-04-30 21:37 ` bugdal at aerifal dot cx 2013-05-01 22:25 ` bugdal at aerifal dot cx 2013-07-16 20:08 ` nshmyrev at yandex dot ru 2013-09-07 6:55 ` carlos at redhat dot com 2014-02-06 18:31 ` jsm28 at gcc dot gnu.org 2014-06-17 18:55 ` 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-14412-131-K4ir4mPv51@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).