This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [lno] [patch] vectorizer update - loop bound





> I could rewrite the normalization pass if you want, it was done right
> before major SSA changes, and i never got around to rewriting it.

I'm not sure we're talking about the same thing. After reading the
responses from Richard and Paul - do you still think your loop
normalization solves this problem?

thanks,

dorit




                                                                                                                                   
                      Daniel Berlin                                                                                                
                      <dberlin@dberlin.        To:       Dorit Naishlos/Haifa/IBM@IBMIL                                            
                      org>                     cc:       pop@gauvain.u-strasbg.fr, gcc-patches@gcc.gnu.org, Geoff Keating          
                                                <geoffk@geoffk.org>, Toon Moene <toon@moene.indiv.nluug.nl>                        
                      19/01/2004 18:22         Subject:  Re: [lno] [patch] vectorizer update - loop bound                          
                                                                                                                                   




> I figured out what the problem was, but now that the vectorizer passes
> that
> stage, it fails on an alignment check, which currently tries to make
> sure
> that the array base and the first access to the array are aligned
> (which is
> over conservative on purpose). The first access however is at index 1,
> which leads the vectorizer to conclude that the accesses to this array
> are
> not aligned. Shouldn't the array accesses be normalized to start from 0
> when the Fortran program is translated to the trees? If not, can I
> query
> what was the source language and treat Fortran programs differently
> than C
> (e.g., consider accesses to index i as accesses to index (i-1) in case
> it's
> Fortran)?
>

I could rewrite the normalization pass if you want, it was done right
before major SSA changes, and i never got around to rewriting it.
My only concern is whether it will make the evolutions too complex to
be "simple" evolutions.
--Dan




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]