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] Add -fdump-rtl-<pass>-quiet


On Thu, Apr 19, 2012 at 5:58 AM, Andrew Stubbs <ams@codesourcery.com> wrote:
> On 18/04/12 22:09, Xinliang David Li wrote:
>>
>> Flags in category 1)
>> --------------------------
>> There are four types of information that can be dumped (should be
>> controlled by flag set 1) ):
>> ? 1.a) transformation decisions -- such as
>> -fdump-tree-vectorize-transformations (to be added)
>> ? 1.b) Intermediate representations --> ?related to what you propose
>> ? 1.c) debug traces (flag to be added)
>> ? 1.d) stats (memory usage, etc).
>
>
> That's all very nice, but apart from name bikeshedding, it shouldn't
> interfere with my patch at all.

No -- I just want to let you know there is similar effort planed for
better coordination. The maintainer will make a call on your patch.

>
> The same goes for most of the rest of your categories: the patches may

>
> To me, the existing "(default), verbose, details" option set makes sense,
> and adding "quiet" to that set seemed appropriate. I'm not sure I like the
> idea of renaming existing options, even if they aren't likely to break much.
>

It is confusing. 'verbose' applies to IR, while 'details' applies to
debug traces.

>
>> These are new proposed flags: To control IR dump before the pass or
>> after the pass.
>
>
> Why? Is there a case where the dump from after the previous pass is not the
> same as the dump before the next?


For productivity -- without it, you either need to remember all pass
ordering, or always dump-all --> the latter can be prohibitive for
very large files.

thanks,

David


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