public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <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 04:21:15 +0000 [thread overview] Message-ID: <bug-105428-4-2N4hueP4DB@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 #2 from Zdenek Sojka <zsojka at seznam dot cz> --- (In reply to joseph@codesourcery.com from comment #1) > What MPC version are you using? Thank you for the reply. If I understand the backtrace correctly I am using the libraries downloaded by the contrib/download_prerequisites script: mpc-1.2.1, mpfr-4.1.0; the same behavior can be observed with system libraries as well, which are the same version + gentoo patches. > There have been a few fixes for slowness > in the MPC inverse trigonometric and hyperbolic functions over the years, > though there may still be scope for substantial further improvements by > choosing different algorithms for different ranges of inputs. If you're > using current MPC then this case should probably be reported to the MPC > maintainers. Similar to PR105384 and PR105385 - if you tell me to open a PR against MPC / MPRF, I will try to do. But I can't tell if this is a bug in the library, or expected behavior and gcc shouldn't use the library to evaluate the value at compilation time.
next prev parent reply other threads:[~2022-04-29 4:21 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 [this message] 2022-04-29 13:57 ` marxin at gcc dot gnu.org 2022-04-29 19:20 ` joseph at codesourcery 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-105428-4-2N4hueP4DB@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).