From patchwork Wed Aug 25 10:55:07 2010
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Dump file usage patterns?
Date: Wed, 25 Aug 2010 00:55:07 -0000
From: Bernd Schmidt <bernds@codesourcery.com>
X-Patchwork-Id: 62670
Message-Id: <4C74F68B.6080009@codesourcery.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>

How are people using dump files?  I find myself adding -fdump-noaddr to
every command line with -da, as I often run diff on dumps from two
different compilers.  How about the patch below?  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?


Bernd


Index: common.opt
===================================================================
--- common.opt	(revision 162821)
+++ common.opt	(working copy)
@@ -493,7 +493,7 @@ Common RejectNegative Joined Var(flag_du
 -fdump-final-insns=filename	Dump to filename the insns at the end of translation
 
 fdump-noaddr
-Common Report Var(flag_dump_noaddr)
+Common Report Var(flag_dump_noaddr) Init(1)
 Suppress output of addresses in debugging dumps
 
 fdump-unnumbered