public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/32373]  New: not vectorized: can't determine dependence (equivalence)
@ 2007-06-17 14:07 tprince at computer dot org
  2007-06-17 14:11 ` [Bug fortran/32373] " tprince at computer dot org
                   ` (2 more replies)
  0 siblings, 3 replies; 7+ messages in thread
From: tprince at computer dot org @ 2007-06-17 14:07 UTC (permalink / raw)
  To: gcc-bugs

gfortran -O3  -ftree-vectorize -ftree-vectorizer-verbose=2 -c k90.f90
Shows missed vectorization at source lines 125,332,380, 638
These problems appear to be associated with the EQUIVALENCE (source line 92),
which names one or more of the arrays involved.


-- 
           Summary: not vectorized: can't determine dependence (equivalence)
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tprince at computer dot org
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32373


^ permalink raw reply	[flat|nested] 7+ messages in thread
[parent not found: <bug-32373-4@http.gcc.gnu.org/bugzilla/>]

end of thread, other threads:[~2012-02-06 21:25 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-06-17 14:07 [Bug fortran/32373] New: not vectorized: can't determine dependence (equivalence) tprince at computer dot org
2007-06-17 14:11 ` [Bug fortran/32373] " tprince at computer dot org
2007-06-18  3:09 ` pinskia at gcc dot gnu dot org
2007-07-03 10:22 ` fxcoudert at gcc dot gnu dot org
     [not found] <bug-32373-4@http.gcc.gnu.org/bugzilla/>
2012-02-05 21:50 ` tkoenig at gcc dot gnu.org
2012-02-05 21:50 ` tkoenig at gcc dot gnu.org
2012-02-06 21:25 ` tkoenig at gcc dot gnu.org

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).