public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/57996] New: Fold more standard complex functions Date: Fri, 26 Jul 2013 19:34:00 -0000 [thread overview] Message-ID: <bug-57996-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57996 Bug ID: 57996 Summary: Fold more standard complex functions Product: gcc Version: 4.9.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: glisse at gcc dot gnu.org Hello, we don't seem to try any optimization on the cpow function (and many other complex functions). In particular, if the arguments are complex_expr<x,0.>, we don't take advantage of it. Note that the C++ library has overloads for mixed pow calls and some code to detect when operands are real, but that isn't the best place for it, ideally it would just convert all to complex, call __builtin_cpow and let the middle-end handle it. Related to PR libstdc++/56106. Some of the optimizations should be limited to the unsafe-math case, but not all (and the exact list may depend on whether your libc provides a correctly rounded cpow or not). cpow requires some special code, but the test for real arguments could be shared by several unary functions (csin, ccos, cexp, ...).
reply other threads:[~2013-07-26 19:34 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-57996-4@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).