Michael Matz writes:
>> Ira Rosen writes:
>> >> How about, as Micha suggested, print the location of the loop
>> >> we currently investigate from vectorize_loops () where we
>> >> call find_loop_location () instead?
>> >
>> > The problem is that a dump of a single loop can be pretty long, and "st
Hi,
On Thu, 1 Sep 2011, Richard Sandiford wrote:
> Ira Rosen writes:
> >> How about, as Micha suggested, print the location of the loop
> >> we currently investigate from vectorize_loops () where we
> >> call find_loop_location () instead?
> >
> > The problem is that a dump of a single loop can
Richard Guenther wrote on 01/09/2011 12:26:25 PM:
> > > Well, it seems to be different what everybody else does and it's
> > > highly redundant for a whole bunch of lines.
> > >
> > > But, it solves my diff issue and the overly long lines as well.
> > >
> > > Your patch changes both dump-file a
On Thu, 1 Sep 2011, Ira Rosen wrote:
>
>
> Richard Guenther wrote on 01/09/2011 11:13:29 AM:
>
> > > > > IMO it's a bad idea. It's now impossible to find anything when
> > > compiling a
> > > > > big file. How about only removing the file name?
> > > >
> > > > How about, as Micha suggested, pr
Richard Guenther wrote on 01/09/2011 11:13:29 AM:
> > > > IMO it's a bad idea. It's now impossible to find anything when
> > compiling a
> > > > big file. How about only removing the file name?
> > >
> > > How about, as Micha suggested, print the location of the loop
> > > we currently investig
On Thu, 1 Sep 2011, Ira Rosen wrote:
>
>
> Richard Guenther wrote on 01/09/2011 10:33:23 AM:
>
> > On Thu, 1 Sep 2011, Ira Rosen wrote:
> >
> > >
> > >
> > > gcc-patches-ow...@gcc.gnu.org wrote on 24/08/2011 02:20:50 PM:
> > > >
> > > > This avoids the file/location clutter in front of each li
Ira Rosen writes:
>> How about, as Micha suggested, print the location of the loop
>> we currently investigate from vectorize_loops () where we
>> call find_loop_location () instead?
>
> The problem is that a dump of a single loop can be pretty long, and "start
> to analyze loop..."/"finish to ana
Richard Guenther wrote on 01/09/2011 10:33:23 AM:
> On Thu, 1 Sep 2011, Ira Rosen wrote:
>
> >
> >
> > gcc-patches-ow...@gcc.gnu.org wrote on 24/08/2011 02:20:50 PM:
> > >
> > > This avoids the file/location clutter in front of each line
> > > in the vectorizer dump. While this is useful for p
On Thu, 1 Sep 2011, Ira Rosen wrote:
>
>
> gcc-patches-ow...@gcc.gnu.org wrote on 24/08/2011 02:20:50 PM:
> >
> > 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 make
gcc-patches-ow...@gcc.gnu.org wrote on 24/08/2011 02:20:50 PM:
>
> 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 b
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 unab
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 tru
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 testsuit
13 matches
Mail list logo
