From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BF0C9385DC02; Wed, 1 Apr 2020 15:53:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BF0C9385DC02 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585756390; bh=cqAAnnIsWykPtMOA6LENIraon4OHu1xZeNbxpwLXzoY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZUH+sT1YnGa3UpsR2yYfFjkzOAwg9VbTbAar+Z/CKdPLoXswHfHMuJDUYdyDnDRsY 1BDxzeO3Q84za8LzYw99doT+GBkUwKFMJQY/4D6ZHpG0GMpLX9y73wDUDavfcJAPVC QkvnYrk6sxJq5gtg+lSH8i/+b5gAmaibMCYDa4YY= From: "vincent-gcc at vinc17 dot net" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/91858] [9/10 Regression] Compile time hog w/ complex float trigonometric functions Date: Wed, 01 Apr 2020 15:53:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: compile-time-hog X-Bugzilla-Severity: normal X-Bugzilla-Who: vincent-gcc at vinc17 dot net X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 9.4 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: Wed, 01 Apr 2020 15:53:10 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D91858 --- Comment #12 from Vincent Lef=C3=A8vre -= -- (In reply to Vincent Lef=C3=A8vre from comment #11) > (In reply to Vincent Lef=C3=A8vre from comment #10) > > Paul Zimmermann says that this bug is fixed in the MPC development vers= ion. >=20 > I could check that the bug is actually fixed, but the does not solve the = GCC > issue, as the time complexity is too large. With 10000000 instead of 1000= 0, > you'll still notice that it takes too much time. But as Paul says, keeping the exponent range reduced as above allows an immediate answer. So the solution will be to upgrade to the next MPC version (not released yet) and do not increase the exponent range (this allows early underflow/overflow checking, thus may avoid costly computations in some domains).=