public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <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 12:41:31 +0000 [thread overview] Message-ID: <bug-91858-4-mOJ7ghLgEI@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 #6 from Richard Biener <rguenth at gcc dot gnu.org> --- mpc_tan (m, m, 0) with (gdb) p *m $14 = {re = {{_mpfr_prec = 24, _mpfr_sign = 1, _mpfr_exp = 14, _mpfr_d = 0x3713c48}}, im = {{_mpfr_prec = 24, _mpfr_sign = 1, _mpfr_exp = 14, _mpfr_d = 0x3710278}}} (gdb) p *m->re._mpfr_d@4 $36 = {11258999068426240000, 32, 81, 57753152} (gdb) p *m->im._mpfr_d@4 $37 = {11258999068426240000, 32, 81, 57738592} I guess there's only one limb, the rest looks garbage. We're using mpfr_set_str on the re/im part from "0x0.9c4p+14" here.
next prev parent reply other threads:[~2020-04-01 12:41 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 [this message] 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 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-mOJ7ghLgEI@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).