This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Fix PR/18179 and use get_inner_reference in vectorizer: part 4

From: Richard Henderson <rth at redhat dot com>
To: Dorit Naishlos <DORIT at il dot ibm 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 02:39:01 -0800
Subject: Re: [patch] Fix PR/18179 and use get_inner_reference in vectorizer: part 4
References: <20050101203414.GB17037@redhat.com> <OF867426C9.8DC092E9-ONC2256F7E.0049277D-C2256F7F.0037C2FF@il.ibm.com>

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.


r~

Follow-Ups:
- Re: [patch] Fix PR/18179 and use get_inner_reference in vectorizer: part 4
  - From: Dorit Naishlos

References:
- Re: [patch] Fix PR/18179 and use get_inner_reference in vectorizer: part 4
  - From: Richard Henderson
- Re: [patch] Fix PR/18179 and use get_inner_reference in vectorizer: part 4
  - From: Dorit Naishlos

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]