public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105428] compilation never (?) finishes with __builtin_casinl() and __builtin_csqrtl() with -O -mlong-double-128 Date: Fri, 29 Apr 2022 19:20:18 +0000 [thread overview] Message-ID: <bug-105428-4-201NKHVRo9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105428-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105428 --- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- If you can identify specific arguments passed to mpc_asin for which it is excessively slow, that should be reported as an MPC bug. Computing correctly rounded mpc_asin shouldn't need to be that slow - provided the algorithm used is appropriate to the input value. See for example how glibc implements casin / casinh / cacos / cacosh. Or https://dl.acm.org/doi/10.1145/275323.275324 (Hull et al, Implementing the complex arcsine and arccosine functions using exception handling, ACM TOMS vol. 23 no. 3 (Sep 1997) pp 299-335). That may require several different algorithms to be implemented, but each such algorithm is straightforward. That's different from the case of Bessel functions of high order - for which there is some literature about computational techniques that shouldn't take time proportional to the order, but where the algorithms are certainly a lot more complicated.
prev parent reply other threads:[~2022-04-29 19:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-28 19:37 [Bug target/105428] New: " zsojka at seznam dot cz 2022-04-28 21:53 ` [Bug target/105428] " joseph at codesourcery dot com 2022-04-29 4:21 ` zsojka at seznam dot cz 2022-04-29 13:57 ` marxin at gcc dot gnu.org 2022-04-29 19:20 ` joseph at codesourcery dot com [this message]
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-105428-4-201NKHVRo9@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).