Make vectorizer dumps more comparable

This avoids the file/location clutter in front of each line
in the vectorizer dump.  While this is useful for people
requesting -fvectorizer-verbose=N in dump files this makes
you unable to compare dumps for testcases on a branch and trunk.
It also makes lines excessively long because the testsuite
filename paths are so long.  Very annoying.

(I'd argue also that -fvectorizer-verbose=N dumps to the dump
file if available and not always to stderr is bogus, but well ...)

This patch has made my life a lot easier debugging the data dependence 
stuff.

Bootstrapped and tested on x86_64-unknown-linux-gnu, installed on trunk.

Richard.

2011-08-24  Richard Guenther  <rguenther@suse.de>

	* tree-vectorizer.c (vect_print_dump_info): Avoid the
	file and location clutter when dumping to dump files.

Hi,

On Wed, 24 Aug 2011, Richard Guenther wrote:

> This avoids the file/location clutter in front of each line in the 
> vectorizer dump.  While this is useful for people requesting 
> -fvectorizer-verbose=N in dump files this makes you unable to compare 
> dumps for testcases on a branch and trunk. It also makes lines 
> excessively long because the testsuite filename paths are so long.  
> Very annoying.

While the repetition is indeed annoying I put the location marker to good 
use for files with multiple loops.  Just searching for "123:" jumped you 
to the dump block where the interesting loop started to be analyzed.  Same 
for searching from the end, where it put you right at the final decision.

I would very much prefer if that would still be possible, possibly by 
using "start to analyze loop at file:123" and "finished with loop at 
file:123".


Ciao,
Michael.

On Wed, 24 Aug 2011, Michael Matz wrote:

> Hi,
> 
> On Wed, 24 Aug 2011, Richard Guenther wrote:
> 
> > This avoids the file/location clutter in front of each line in the 
> > vectorizer dump.  While this is useful for people requesting 
> > -fvectorizer-verbose=N in dump files this makes you unable to compare 
> > dumps for testcases on a branch and trunk. It also makes lines 
> > excessively long because the testsuite filename paths are so long.  
> > Very annoying.
> 
> While the repetition is indeed annoying I put the location marker to good 
> use for files with multiple loops.  Just searching for "123:" jumped you 
> to the dump block where the interesting loop started to be analyzed.  Same 
> for searching from the end, where it put you right at the final decision.
> 
> I would very much prefer if that would still be possible, possibly by 
> using "start to analyze loop at file:123" and "finished with loop at 
> file:123".

Yes, that would be nice.  Patches welcome ;)

Richard.