public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "changpeng.fang at amd dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45022] No prefetch for the vectorized loop
Date: Mon, 01 Nov 2010 22:22:00 -0000 [thread overview]
Message-ID: <20101101222200.SyrlAof3FafHFgZnYAG-dCRwPruNCKMVjdR_SKmmvwg@z> (raw)
In-Reply-To: <bug-45022-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45022
Changpeng Fang <changpeng.fang at amd dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
--- Comment #6 from Changpeng Fang <changpeng.fang at amd dot com> 2010-11-01 22:21:56 UTC ---
Not surprise: Richard's check-in of the MISALIGNED_INDIRECT_REF removal
fixed the bug.
Surprise: only two prefetches are generated (which is right). However,
if we could align the references as the following case (PR 45021):
float a[1024], b[1024];
void foo(int beta)
{
int i;
for(i=0; i<1024; i++)
a[i] = a[i] + beta * b[i];
}
Three prefetches will be generated, one for b, one for load a, and one for
store a.
Anyway, I am closing this bug, and we should work on PR 45021.
next parent reply other threads:[~2010-11-01 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-45022-4@http.gcc.gnu.org/bugzilla/>
2010-11-01 22:22 ` changpeng.fang at amd dot com [this message]
2010-07-21 18:04 [Bug tree-optimization/45022] New: " changpeng dot fang at amd dot com
2010-07-21 18:06 ` [Bug tree-optimization/45022] " rguenth at gcc dot gnu dot org
2010-07-22 20:52 ` changpeng dot fang at amd dot com
2010-07-22 21:17 ` rakdver at kam dot mff dot cuni dot cz
2010-07-29 19:14 ` changpeng dot fang at amd dot com
2010-07-30 8:41 ` rguenther at suse dot de
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=20101101222200.SyrlAof3FafHFgZnYAG-dCRwPruNCKMVjdR_SKmmvwg@z \
--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).