public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "changpeng dot fang at amd dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44794] pre- and post-loops should not be unrolled.
Date: Thu, 15 Jul 2010 01:50:00 -0000	[thread overview]
Message-ID: <20100715015013.21927.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44794-18740@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from changpeng dot fang at amd dot com  2010-07-15 01:50 -------
Created an attachment (id=21205)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21205&action=view)
Do not unroll pre and post loops

I did a quick test on polyhedron before and after applying the preliminary
patch. Tests are based on -O3 -fprefetch-loop-arrays -funroll-loops.

               timing (s)      |     size (B)
         before after   %deduc | before after   %deduc          
cacacita 14.35  10.88   24.18  | 90715  72843   19.7
gas_dyn  34.68  21.58   37.77  | 149608 100936  32.53
nf       33.91  19.32   43.03  | 139150 83054   40.31
protein  51.35  33.23   35.29  | 163672 122808  24.97
rnflow   60.9   43.28   28.93  | 268784 169152  37.07
test_fpu 52.61  30.35   42.31  | 234045 144285  38.35


-- 


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


  parent reply	other threads:[~2010-07-15  1:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 23:54 [Bug tree-optimization/44794] New: " changpeng dot fang at amd dot com
2010-07-03 10:48 ` [Bug tree-optimization/44794] " rguenth at gcc dot gnu dot org
2010-07-06 17:59 ` changpeng dot fang at amd dot com
2010-07-06 18:36 ` changpeng dot fang at amd dot com
2010-07-15  1:50 ` changpeng dot fang at amd dot com [this message]
     [not found] <bug-44794-4@http.gcc.gnu.org/bugzilla/>
2023-03-09  8:06 ` rguenth at gcc dot gnu.org
2023-04-19 11:51 ` cvs-commit at gcc dot gnu.org
2023-04-19 11:53 ` rguenth at gcc dot gnu.org
2023-04-19 11:55 ` 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=20100715015013.21927.qmail@sourceware.org \
    --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).