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/45021] Redundant prefetches for the vectorized loop Date: Wed, 21 Jul 2010 18:27:00 -0000 [thread overview] Message-ID: <20100721182700.14209.qmail@sourceware.org> (raw) In-Reply-To: <bug-45021-18740@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from changpeng dot fang at amd dot com 2010-07-21 18:26 ------- The direct reason is that prefetching could not differentiate the base addresses of the vectorized load and store (of a[i]): *vect_pa.6_24 *vect_pa.19_37 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45021
next prev parent reply other threads:[~2010-07-21 18:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-21 17:46 [Bug tree-optimization/45021] New: " changpeng dot fang at amd dot com 2010-07-21 18:27 ` changpeng dot fang at amd dot com [this message] 2010-07-24 20:32 ` [Bug tree-optimization/45021] Redundant prefetches for some loops (vectorizer produced ones too) pinskia at gcc dot gnu dot org 2010-07-24 20:42 ` rakdver at kam dot mff dot cuni dot cz 2010-07-28 18:23 ` changpeng dot fang at amd dot com 2010-07-28 18:28 ` changpeng dot fang at amd 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=20100721182700.14209.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: linkBe 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).