public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/40168] missing unrolling/scalarization/reassoc/free
Date: Fri, 29 Mar 2013 10:51:00 -0000 [thread overview]
Message-ID: <bug-40168-4-60fJ4NICU4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40168-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40168
Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2009-12-18 14:45:13 |2013-03-29
CC| |Joost.VandeVondele at mat
| |dot ethz.ch
--- Comment #21 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 2013-03-29 10:50:49 UTC ---
So, the testcase in comment #14 is indeed still (4.9.0) yielding the 324
multiplies for subroutine S2, instead of the more optimal 192 as shown in S1.
Ifort also results in 324 multiplies, but is able to do a couple of them with
mulpd instead of mulsd. So the common subexpressions are still not found.
next parent reply other threads:[~2013-03-29 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-40168-4@http.gcc.gnu.org/bugzilla/>
2013-03-29 10:51 ` Joost.VandeVondele at mat dot ethz.ch [this message]
2021-12-25 7:01 ` [Bug tree-optimization/40168] finding common subexpressions pinskia at gcc dot gnu.org
2009-05-16 9:35 [Bug middle-end/40168] New: missing unrolling/scalarization/reassoc/free jv244 at cam dot ac dot uk
2009-12-18 14:45 ` [Bug tree-optimization/40168] " rguenth at gcc dot gnu dot 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-40168-4-60fJ4NICU4@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).