public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <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 15:53:10 +0000	[thread overview]
Message-ID: <bug-91858-4-zA4bVofe2w@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 #12 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
(In reply to Vincent Lefèvre from comment #11)
> (In reply to Vincent Lefèvre from comment #10)
> > Paul Zimmermann says that this bug is fixed in the MPC development version.
> 
> 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 10000,
> 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).

  parent reply	other threads:[~2020-04-01 15:53 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
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 [this message]
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-zA4bVofe2w@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).