https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43423
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43423
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43423
Andrew Pinski changed:
What|Removed |Added
Blocks||53947
--- Comment #12 from Andrew Pinski
--- Comment #11 from spop at gcc dot gnu dot org 2010-05-25 23:33 ---
This is not a IV type problem: the number of iterations may be zero when mid ==
0 or mid == n, so the number of iterations analysis has a condition under which
niter may_be_zero.
I sent out a patch that makes niter re
--- Comment #10 from spop at gcc dot gnu dot org 2010-05-24 23:02 ---
note: not vectorized: number of iterations cannot be computed.
Graphite has a problem with the generation of induction variables types
that makes the code harder to analyze after Graphite. I will try to get this
fixe
--- Comment #9 from changpeng dot fang at amd dot com 2010-05-24 22:47
---
(In reply to comment #8)
> -fgraphite-identity does iteration splitting for this case.
Do you know why it could not be vectorized after iteration
range splitting?
--
http://gcc.gnu.org/bugzilla/show_bug.cg
--- Comment #8 from spop at gcc dot gnu dot org 2010-05-24 22:44 ---
-fgraphite-identity does iteration splitting for this case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43423
--- Comment #7 from changpeng dot fang at amd dot com 2010-05-07 21:41
---
(In reply to comment #4)
> (In reply to comment #3)
> > Subject: Re: gcc should vectorize this loop
> > through "iteration range splitting"
> > You mean that the problem is the if-conversion of the stor
--- Comment #6 from spop at gcc dot gnu dot org 2010-04-08 17:47 ---
I changed the title of this bug to match the comments in the PR:
we should vectorize this loop using if-conversion, and not "iteration
range splitting".
Also note that in general, by doing an "iteration range splitting
