public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
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 [thread overview]
Message-ID: <bug-91858-4-7eeDbKTZwj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91858-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91858
--- Comment #9 from rguenther at suse dot de <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=91858
>
> --- Comment #7 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
> (In reply to Richard Biener from comment #6)
> > I guess there's only one limb, the rest looks garbage.
>
> Yes, and 11258999068426240000 with _mpfr_exp = 14 corresponds to 10000 as
> expected (11258999068426240000 = 10000*2^50).
>
> And even when reusing the input
>
> mpc_init2 (x, 24);
> mpc_set_ui_ui (x, 10000, 10000, MPC_RNDNN);
> mpc_tan (x, x, 0);
>
> the program terminates immediately.
>
> 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 ...).
next prev parent reply other threads:[~2020-04-01 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91858-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` jakub at gcc dot gnu.org
2020-04-01 12:28 ` vincent-gcc at vinc17 dot net
2020-04-01 12:41 ` rguenth at gcc dot gnu.org
2020-04-01 13:17 ` vincent-gcc at vinc17 dot net
2020-04-01 13:33 ` vincent-gcc at vinc17 dot net
2020-04-01 13:38 ` rguenther at suse dot de [this message]
2020-04-01 14:17 ` vincent-gcc at vinc17 dot net
2020-04-01 14:33 ` vincent-gcc at vinc17 dot net
2020-04-01 15:53 ` vincent-gcc at vinc17 dot net
2020-04-03 12:23 ` rguenth at gcc dot gnu.org
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-91858-4-7eeDbKTZwj@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: link
Be 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).