From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D7278385BF92; Wed, 1 Apr 2020 13:38:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D7278385BF92 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585748308; bh=r4lG2F95brasozgVcBOhG2Vc0BgX8EtZTbiOHa+SV50=; h=From:To:Subject:Date:In-Reply-To:References:From; b=cFTlAVh3EtizaPGPI6Rj01+g10CbJIwGk7zs6mjiViVLr2Rm36xsXX887ogJmAWnI XGUNHtakpiCfhMjyg3WUIcaLvpDhThUTTtbP9nuXurrVlVWfOmjLkHaEWEtWM7Jj1V O20d4t76nnximLqvCfdHVJOAtwBlUPxPp0gYfwC0= From: "rguenther at suse dot de" 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 13:38:28 +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: rguenther at suse dot de 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 13:38:28 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D91858 --- Comment #9 from rguenther at suse dot de --- On Wed, 1 Apr 2020, vincent-gcc at vinc17 dot net wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D91858 >=20 > --- Comment #7 from Vincent Lef=C3=A8vre = --- > (In reply to Richard Biener from comment #6) > > I guess there's only one limb, the rest looks garbage. >=20 > Yes, and 11258999068426240000 with _mpfr_exp =3D 14 corresponds to 10000 = as > expected (11258999068426240000 =3D 10000*2^50). >=20 > And even when reusing the input >=20 > mpc_init2 (x, 24); > mpc_set_ui_ui (x, 10000, 10000, MPC_RNDNN); > mpc_tan (x, x, 0); >=20 > the program terminates immediately. >=20 > I'm going to look at this more closely with gdb. But I confirm I can see > mpc_tan in the backtrace. It's likely by us doing mpfr_set_emin (-32990); mpfr_set_emax (32766); during startup to work around a similar bug in MPC (IIRC it also was tan ...).=