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 tree-optimization/48092] associative property of builtins is not exploited on GIMPLE Date: Fri, 05 Aug 2011 08:35:00 -0000 [thread overview] Message-ID: <bug-48092-4-Xq7FEYyOEr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48092-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48092 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011.08.05 08:33:59 CC| |rguenth at gcc dot gnu.org Component|rtl-optimization |tree-optimization Summary|missing optimization |associative property of |(associative property of |builtins is not exploited |sqrt) |on GIMPLE Ever Confirmed|0 |1 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-08-05 08:33:59 UTC --- The reason is we handle this only from the frontend folder which doesn't see builtins when using std::sqrt. A C testcase like double foo (double x, double y) { return __builtin_sqrt (x) * __builtin_sqrt (y); } is optimized. For C++ (thus, optimizing the above when wrapping the sqrt inside an inline function) these optimizations have to be replicated at the GIMPLE level. Which today means in, for example, tree-ssa-forwprop.c. Same issue for std::exp and other associative builtins.
next prev parent reply other threads:[~2011-08-05 8:35 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-12 14:57 [Bug tree-optimization/48092] New: associative property of sqrt vincenzo.innocente at cern dot ch 2011-08-05 8:17 ` [Bug rtl-optimization/48092] missing optimization (associative property of sqrt) vincenzo.innocente at cern dot ch 2011-08-05 8:35 ` rguenth at gcc dot gnu.org [this message] 2011-09-08 10:14 ` [Bug tree-optimization/48092] associative property of builtins is not exploited on GIMPLE vincenzo.innocente at cern dot ch 2011-09-08 11:59 ` rguenther at suse dot de 2021-07-21 2:46 ` pinskia at gcc dot gnu.org 2023-05-12 5:46 ` pinskia 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-48092-4-Xq7FEYyOEr@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).