From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 464723858D1E; Fri, 29 Apr 2022 04:21:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 464723858D1E From: "zsojka at seznam dot cz" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: compile-time-hog, memory-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: zsojka at seznam dot cz X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2022 04:21:15 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105428 --- Comment #2 from Zdenek Sojka --- (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=20 > in the MPC inverse trigonometric and hyperbolic functions over the years,= =20 > though there may still be scope for substantial further improvements by=20 > choosing different algorithms for different ranges of inputs. If you're= =20 > using current MPC then this case should probably be reported to the MPC=20 > 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.=