public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/26420]  New: -ftree-vectorizer-verbose=1 prints unvectorized loops information
@ 2006-02-22 14:21 rguenth at gcc dot gnu dot org
  2006-02-22 14:34 ` [Bug tree-optimization/26420] " pinskia at gcc dot gnu dot org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: rguenth at gcc dot gnu dot org @ 2006-02-22 14:21 UTC (permalink / raw)
  To: gcc-bugs

tramp3d-v4.cpp:3740: note: vectorized 0 loops in function.

tramp3d-v4.cpp:3740: note: vectorized 0 loops in function.

tramp3d-v4.cpp:50941: note: vectorized 0 loops in function.

tramp3d-v4.cpp:3740: note: vectorized 0 loops in function.

tramp3d-v4.cpp:3740: note: vectorized 0 loops in function.

etc.

  if (vect_print_dump_info (REPORT_VECTORIZED_LOOPS))
    fprintf (vect_dump, "vectorized %u loops in function.\n",
             num_vectorized_loops);

here we should check if num_vectorized_loops is >0 or verbosity level
includes REPORT_UNVECTORIZED_LOOPS.  Though even in this case the
note does not provide any useful information.


-- 
           Summary: -ftree-vectorizer-verbose=1 prints unvectorized loops
                    information
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rguenth at gcc dot gnu dot org


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug tree-optimization/26420] -ftree-vectorizer-verbose=1 prints unvectorized loops information
  2006-02-22 14:21 [Bug tree-optimization/26420] New: -ftree-vectorizer-verbose=1 prints unvectorized loops information rguenth at gcc dot gnu dot org
@ 2006-02-22 14:34 ` pinskia at gcc dot gnu dot org
  2006-02-26 11:05 ` dorit at il dot ibm dot com
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2006-02-22 14:34 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from pinskia at gcc dot gnu dot org  2006-02-22 14:34 -------
Confirmed.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-02-22 14:34:10
               date|                            |


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug tree-optimization/26420] -ftree-vectorizer-verbose=1 prints unvectorized loops information
  2006-02-22 14:21 [Bug tree-optimization/26420] New: -ftree-vectorizer-verbose=1 prints unvectorized loops information rguenth at gcc dot gnu dot org
  2006-02-22 14:34 ` [Bug tree-optimization/26420] " pinskia at gcc dot gnu dot org
@ 2006-02-26 11:05 ` dorit at il dot ibm dot com
  2007-03-05 10:57 ` rguenth at gcc dot gnu dot org
  2007-03-05 10:57 ` rguenth at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: dorit at il dot ibm dot com @ 2006-02-26 11:05 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from dorit at il dot ibm dot com  2006-02-26 11:01 -------
For -ftree-vectorizer-verbose=1 the vectorizer reports each loop that got
vectorized, and also the total number of loops that got vectorized, even if
that number is zero. If preferable, we can report that 0 loops got vectorized
only under -ftree-vectorizer-verbose=2, or higher. The patch below makes the
"vectorized 0 loops" be reported for verbosity level 2 and higher. Shall I
suggest the patch for mainline?

Index: tree-vectorizer.c
===================================================================
*** tree-vectorizer.c   (revision 111450)
--- tree-vectorizer.c   (working copy)
*************** vectorize_loops (struct loops *loops)
*** 2047,2053 ****
        num_vectorized_loops++;
      }

!   if (vect_print_dump_info (REPORT_VECTORIZED_LOOPS))
      fprintf (vect_dump, "vectorized %u loops in function.\n",
             num_vectorized_loops);

--- 2047,2058 ----
        num_vectorized_loops++;
      }

!   if (num_vectorized_loops > 0
!       && vect_print_dump_info (REPORT_VECTORIZED_LOOPS))
!     fprintf (vect_dump, "vectorized %u loops in function.\n",
!            num_vectorized_loops);
!   else if (num_vectorized_loops == 0
!          && vect_print_dump_info (REPORT_UNVECTORIZED_LOOPS))
      fprintf (vect_dump, "vectorized %u loops in function.\n",
             num_vectorized_loops);


-- 


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug tree-optimization/26420] -ftree-vectorizer-verbose=1 prints unvectorized loops information
  2006-02-22 14:21 [Bug tree-optimization/26420] New: -ftree-vectorizer-verbose=1 prints unvectorized loops information rguenth at gcc dot gnu dot org
                   ` (2 preceding siblings ...)
  2007-03-05 10:57 ` rguenth at gcc dot gnu dot org
@ 2007-03-05 10:57 ` rguenth at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu dot org @ 2007-03-05 10:57 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from rguenth at gcc dot gnu dot org  2007-03-05 10:57 -------
Fixed.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |4.3.0


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug tree-optimization/26420] -ftree-vectorizer-verbose=1 prints unvectorized loops information
  2006-02-22 14:21 [Bug tree-optimization/26420] New: -ftree-vectorizer-verbose=1 prints unvectorized loops information rguenth at gcc dot gnu dot org
  2006-02-22 14:34 ` [Bug tree-optimization/26420] " pinskia at gcc dot gnu dot org
  2006-02-26 11:05 ` dorit at il dot ibm dot com
@ 2007-03-05 10:57 ` rguenth at gcc dot gnu dot org
  2007-03-05 10:57 ` rguenth at gcc dot gnu dot org
  3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu dot org @ 2007-03-05 10:57 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #4 from rguenth at gcc dot gnu dot org  2007-03-05 10:57 -------
Subject: Bug 26420

Author: rguenth
Date: Mon Mar  5 10:57:09 2007
New Revision: 122544

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=122544
Log:
2007-03-05  Richard Guenther  <rguenther@suse.de>
        Dorit Nuzman  <dorit@il.ibm.com>

        PR tree-optimization/26420
        * tree-vectorizer.c (vectorize_loops): Bail out early if there
        are no loops in the function.  Only print the number of
        vectorized loops if it is greater than zero or we are supposed
        to print information about unvectorized loops.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/tree-vectorizer.c


-- 


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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-03-05 10:57 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-02-22 14:21 [Bug tree-optimization/26420] New: -ftree-vectorizer-verbose=1 prints unvectorized loops information rguenth at gcc dot gnu dot org
2006-02-22 14:34 ` [Bug tree-optimization/26420] " pinskia at gcc dot gnu dot org
2006-02-26 11:05 ` dorit at il dot ibm dot com
2007-03-05 10:57 ` rguenth at gcc dot gnu dot org
2007-03-05 10:57 ` rguenth at gcc dot gnu dot 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).