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: Dump file usage patterns?

From: Bernd Schmidt <bernds at codesourcery dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Fri, 28 Jan 2011 17:12:26 +0100
Subject: Re: Dump file usage patterns?
References: <4C74F68B.6080009@codesourcery.com> <20100825111757.GT702@tyan-ft48-01.lab.bos.redhat.com>

On 08/25/2010 01:17 PM, Jakub Jelinek wrote:
> On Wed, Aug 25, 2010 at 12:55:07PM +0200, Bernd Schmidt wrote:
>> Should we print cselib
>> information only when given a specific flag - I don't find it very
>> useful and it clutters up the dump files?
> 
> For var-tracking issues it is very useful, but I guess I don't mind enabling
> it with an extra option.

How's this? Bootstrapped and tested on i686-linux.


Bernd

Attachment: dump-cselib.diff
Description: Text document

Follow-Ups:
- Re: Dump file usage patterns?
  - From: Richard Guenther

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