This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] Fix PR/18179 and use get_inner_reference in vectorizer: part 4
- From: Dorit Naishlos <DORIT at il dot ibm dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Ira Rosen <IRAR at il dot ibm dot com>, Leehod Baruch <LEEHOD at il dot ibm dot com>
- Date: Tue, 4 Jan 2005 13:21:08 +0200
- Subject: Re: [patch] Fix PR/18179 and use get_inner_reference in vectorizer: part 4
Richard Henderson <rth@redhat.com> wrote on 04/01/2005 12:39:01:
> On Tue, Jan 04, 2005 at 12:09:03PM +0200, Dorit Naishlos wrote:
> > (along with appropriate 'dg-final ...' for all other testcases).
> > Shall I prepare something along these lines?
>
> Yes please.
>
> > We're actually working on cleaning-up the vectorizer reports in general
-
> > see PR18441 - http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18441), and
> > would be happy to get comments. This cleanup includes adding verbosity
> > levels, more accurate printing of the loop line-number, more
informative
> > reports.
> > Would such a cleanup be acceptable for mainline?
>
> Most probably. The loop line number thing would be *very* welcome.
> Vectorized loops are essentially non-debuggable at the moment.
>
can you please elaborate? we can copy the EXPR_LOCATION of a stmt to the
vectorized stmt that replaces it. would that help? anything else we can do?
thanks
dorit
>
> r~