public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/40384] [4.5 regression] Revision 148277 failed gcc.dg/tree-ssa/prefetch-5.c
Date: Wed, 10 Jun 2009 20:15:00 -0000	[thread overview]
Message-ID: <20090610201454.1186.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40384-682@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from hjl dot tools at gmail dot com  2009-06-10 20:14 -------
(In reply to comment #2)
> The new cost model added in revision 148277 supresses prefetching in a loop
> when it is unlikely to be profitable. One such non-profitable case is a loop
> with an unknown trip count and a high prefeching cost. The prefetching cost is
> modeled by the ratio between the prefetch count and the total instruction count
> in a loop. When this ratio is greater than 1/10 in a loop with an unknown trip
> count, prefetching is considered non-profitable and no prefetches are issued.
> The first two loops in this test case fall under this category, where the trip
> count is not known and the prefetch-to-insn ratio is 1/5. Possible fixes are:
> 
> 1. Add more computation to the loop bodies in the test case to reduce the
> prefetch-to-insn ratios and hence make the loops profitable from the cost
> model's point of view.
> 2. Use a commad line option to set the maximum profitable prefetch-to-insn
> ratio to 1/5. The syntax is --param min-insn-to-prefetch-ratio=5
> 3. Change the expected output such that it does not expect prefetches in this
> case.
> 

I prefer #2 since this is a prefetch test.


-- 

hjl dot tools at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hjl dot tools at gmail dot
                   |                            |com


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


  parent reply	other threads:[~2009-06-10 20:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 10:23 [Bug middle-end/40384] New: [4.5 regression] Revision 148277 failed 148277 hjl dot tools at gmail dot com
2009-06-09 10:24 ` [Bug middle-end/40384] " hjl dot tools at gmail dot com
2009-06-09 14:19 ` [Bug tree-optimization/40384] [4.5 regression] Revision 148277 failed gcc.dg/tree-ssa/prefetch-5.c rguenth at gcc dot gnu dot org
2009-06-09 22:37 ` gshobaki at gcc dot gnu dot org
2009-06-10 20:15 ` hjl dot tools at gmail dot com [this message]
2009-06-12  5:00 ` hjl dot tools at gmail dot com
2009-06-12 13:16 ` [Bug testsuite/40384] " hjl dot tools at gmail dot com
2009-06-12 13:24 ` hjl dot tools at gmail dot com
2009-06-12 13:38 ` hjl at gcc dot gnu dot org
2009-06-13  0:09 ` hjl dot tools at gmail dot com

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=20090610201454.1186.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).