http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39300
Richard Guenther changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39300
Richard Guenther changed:
What|Removed |Added
Blocks||53947
--- Comment #9 from Richard Guen
--- Comment #9 from jessiecute13 at aol dot com 2009-08-17 17:38 ---
$1.21
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39300
--- Comment #8 from matz at gcc dot gnu dot org 2009-07-22 15:40 ---
So, the immediate problem is now fixed, but I'd suggest leaving this
enhancement request open, in case anybody wants to work on extending the
vectorizer to deal with these loop-carried dependencies, because in that
case
--- Comment #7 from matz at gcc dot gnu dot org 2009-07-22 15:31 ---
Subject: Bug 39300
Author: matz
Date: Wed Jul 22 15:30:50 2009
New Revision: 149942
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149942
Log:
PR tree-optimization/35229
PR tree-optimization/393
--- Comment #6 from matz at gcc dot gnu dot org 2009-03-09 13:25 ---
It's also PRE that produces such patterns, so moving predcom behind
vectorization alone won't help this problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39300
--- Comment #5 from dorit at gcc dot gnu dot org 2009-03-08 14:25 ---
This is a known problem... Indeed when Zdenek introduced predictive-commoning
there was a discussion on whether to schedule it before or after vectorization.
AFAIR, it ended up getting scheduled before the vectorizer j
--- Comment #4 from irar at il dot ibm dot com 2009-02-25 14:08 ---
Looks similar to PR 35229.
We get here:
# pre.1 = PHI
..
load D.2
D.3 = D.2 + pre.1 + ...
store D.3
--
irar at il dot ibm dot com changed:
What|Removed |Added
--
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-02-25 14:07 ---
Simpler C testcase:
float res[1024], data[1024];
void foo(void)
{
int i;
float tmp = data[0];
for (i = 1; i < 1024; ++i)
{
float tmp2 = data[i];
res[i] = tmp + tmp2;
tmp = tmp2;
}
}
