| Message ID | 4C74F68B.6080009@codesourcery.com |
|---|---|
| State | New |
| Headers | show |
On Wed, Aug 25, 2010 at 12:55 PM, Bernd Schmidt <bernds@codesourcery.com> wrote: > 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? With the patch the naming of the option doesn't make much sense. The flag is also not used too often - maybe it's more useful to dump UIDs than addresses, for example from DF. Your suggestion about cselib info is good. Richard. > > Bernd >
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. Jakub
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