public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49749] Reassociation rank algorithm does not include all non-NULL operands
Date: Fri, 15 Jul 2011 20:16:00 -0000	[thread overview]
Message-ID: <bug-49749-4-qLeI6dcrKh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49749-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49749

--- Comment #6 from William J. Schmidt <wschmidt at gcc dot gnu.org> 2011-07-15 20:15:09 UTC ---
We ran some experiments attempting to restore the r161839 behavior, either by
lowering the rank of memory references or raising the rank of phi references. 
Although both experiments restored bwaves code generation to respectability,
several other benchmarks suffered, so this is not a general answer.  Any
thoughts on more limited heuristics that might help the bwaves scenario?

It seems that copyrename needs help from reassoc to find the opportunity;
perhaps reassoc can be tweaked to recognize situations that will help
copyrename downstream?


  parent reply	other threads:[~2011-07-15 20:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14 16:51 [Bug tree-optimization/49749] New: " wschmidt at gcc dot gnu.org
2011-07-14 19:23 ` [Bug tree-optimization/49749] " wschmidt at gcc dot gnu.org
2011-07-14 19:23 ` wschmidt at gcc dot gnu.org
2011-07-14 19:27 ` wschmidt at gcc dot gnu.org
2011-07-14 19:28 ` wschmidt at gcc dot gnu.org
2011-07-14 19:30 ` wschmidt at gcc dot gnu.org
2011-07-15 20:16 ` wschmidt at gcc dot gnu.org [this message]
2011-07-15 20:21 ` wschmidt at gcc dot gnu.org
2011-07-18  9:11 ` rguenth at gcc dot gnu.org
2011-07-20 16:30 ` wschmidt at gcc dot gnu.org
2011-07-20 16:39 ` wschmidt at gcc dot gnu.org
2011-07-20 19:02 ` wschmidt at gcc dot gnu.org
2011-07-21 12:07 ` rguenth at gcc dot gnu.org
2011-07-21 18:09 ` wschmidt at gcc dot gnu.org
2011-07-21 20:28 ` wschmidt at gcc dot gnu.org
2011-07-29 18:41 ` wschmidt at gcc dot gnu.org
2011-07-31 19:00 ` wschmidt at gcc dot gnu.org
2011-07-31 19:01 ` wschmidt at gcc dot gnu.org
2021-09-28 12:11 ` cvs-commit 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-49749-4-qLeI6dcrKh@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).