[Bug tree-optimization/18441] Vectorizer: add a command line for simple vectorizer report

["leehod at il dot ibm dot com" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From leehod at il dot ibm dot com  2004-12-22 18:59 -------
I am working with Dorit on cleaning up the vectorizer dumps. We'd also like to 
try to address this PR - here are some preliminary thoughts/questions:

1) The 'inform' utility doesn't look very suitable because it prints the line 
information of the function and we want the line info of the loop, so a typical 
printout would look like this:
loop at trees.c:499: Success! loop vectorized.
Also, it only prints to stderr, and we want to be able to print the same 
information also to a dump-file. Maybe we want a 'vect_inform' that (1) would 
not print the function line-number but some other line-number passed as 
argument (the loop line-number), and (2) could be made to print either to 
stderr or to a dump-file?

2) How about using a mechanism like -fsched-verbose? If -ftree-vect-verbose=x 
is used and a dump-file is available, then the output will be printed into the 
dump-file; otherwise, it will be printed into stderr. If -ftree-vect-verbose=x 
is used then there will be no difference between -fdump-tree-vect-details and -
fdump-tree-vect-stats (they will both use the same verbosity level x).  If -
ftree-vect-verbose is not specified, then -fdump-tree-vect-details could use 
the highest verbosity level as default, and -fdump-tree-vect-stats could use 
the lowest verbosity level.

3) We could use the different verbosity levels to prune the number of non-
vectorized-loops we report about, not just the amount of detail we report. For 
example:
level 0: no diagnostic information.
level 1: report vectorized loops only
level 2: report vectorized loops and non-vectorized inner-most loops that 
passed the first analysis phase (vect_analyze_loop_form).
level 3: report vectorized loops and non-vectorized inner-most loops
level 4: report vectorized loops and all non-vectorized loops
level 5: full debug information (vectorized/non-vectorized loops, data-
dependence/scalar-evolution dumps)

4) Is there a mechanism in the testsuite to analyze output to stderr?

thanks,
Leehod


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dorit at il dot ibm dot com,
                   |                            |leehod at il dot ibm dot com


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