From: Richard Guenther <rguenther@suse.de>
To: Ira Rosen <IRAR@il.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Make vectorizer dumps more comparable
Date: Thu, 01 Sep 2011 07:33:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1109010932010.2130@zhemvz.fhfr.qr> (raw)
In-Reply-To: <OF81FD7184.88F3B5C4-ONC22578FE.0028D474-C22578FE.0029508B@il.ibm.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 3044 bytes --]
On Thu, 1 Sep 2011, Ira Rosen wrote:
>
>
> gcc-patches-owner@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 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.
>
>
> 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 investigate from vectorize_loops () where we
call find_loop_location () instead?
Richard.
> Index: tree-vectorizer.c
> ===================================================================
> --- tree-vectorizer.c (revision 178374)
> +++ tree-vectorizer.c (working copy)
> @@ -149,16 +149,12 @@ vect_print_dump_info (enum vect_verbosit
> if (!current_function_decl || !vect_dump)
> return false;
>
> - if (dump_file)
> - fprintf (vect_dump, "\n");
> -
> - else if (vect_location == UNKNOWN_LOC)
> - fprintf (vect_dump, "\n%s:%d: note: ",
> - DECL_SOURCE_FILE (current_function_decl),
> + if (vect_location == UNKNOWN_LOC)
> + fprintf (vect_dump, "\nline %d: ",
> DECL_SOURCE_LINE (current_function_decl));
> else
> - fprintf (vect_dump, "\n%s:%d: note: ",
> - LOC_FILE (vect_location), LOC_LINE (vect_location));
> + fprintf (vect_dump, "\nline %d: ",
> + LOC_LINE (vect_location));
>
> return true;
> }
>
> Ira
>
> >
> > Index: gcc/tree-vectorizer.c
> > ===================================================================
> > --- gcc/tree-vectorizer.c (revision 178028)
> > +++ gcc/tree-vectorizer.c (working copy)
> > @@ -149,7 +149,10 @@ vect_print_dump_info (enum vect_verbosit
> > if (!current_function_decl || !vect_dump)
> > return false;
> >
> > - if (vect_location == UNKNOWN_LOC)
> > + if (dump_file)
> > + fprintf (vect_dump, "\n");
> > +
> > + else if (vect_location == UNKNOWN_LOC)
> > fprintf (vect_dump, "\n%s:%d: note: ",
> > DECL_SOURCE_FILE (current_function_decl),
> > DECL_SOURCE_LINE (current_function_decl));
> >
>
>
--
Richard Guenther <rguenther@suse.de>
SUSE / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer
next prev parent reply other threads:[~2011-09-01 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 13:07 Richard Guenther
2011-08-24 14:40 ` Michael Matz
2011-08-24 16:14 ` Richard Guenther
2011-09-01 7:31 ` Ira Rosen
2011-09-01 7:33 ` Richard Guenther [this message]
2011-09-01 7:51 ` Ira Rosen
2011-09-01 8:06 ` Richard Sandiford
2011-09-01 13:41 ` Michael Matz
2011-09-01 14:41 ` Richard Sandiford
2011-09-01 8:13 ` Richard Guenther
2011-09-01 9:22 ` Ira Rosen
2011-09-01 9:26 ` Richard Guenther
2011-09-01 10:51 ` Ira Rosen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1109010932010.2130@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=IRAR@il.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).