On 10/22/2015 09:38 AM, Nikolai Bozhenov wrote:
Hi!Currently -fsched-verbose option redirects debugging dumps to stderr if there is no dump_file for the current pass. It would be fine if there were the only scheduling pass. But for example for AArch64 there are 3 scheduling passes in the default pipeline: sched1, fusion and sched2. So, when passing options like -fsched-verbose=7 -fdump-rtl-sched1 to GCC I get a neat dump for sched1 in the file and a mess of fusion/sched2 logs in the console. In fact, currently there's no way to tell GCC that I want extremely verbose logs for sched1 and I want no logs for all other passes. Especially to the console. I suggest disabling such redirection in the scheduler and omitting debugging output for passes without dump_file. I believe a better way to redirect printing to the stderr is to use options like -fdump-rtl-sched=stderr. The attached patch implements the suggestion. Anyway, the old behavior may be reproduced with options -fsched-verbose=7 -fdump-rtl-sched1 -fdump-rtl-{sched_fusion,sched2}=stderr if it is really necessary. The patch has been bootstrapped and regtested on x86_64. Thanks, Nikolai patch.diff 2015-10-22 Nikolai Bozhenov<n.bozhe...@samsung.com> * haifa-sched.c (setup_sched_dump): Don't redirect output to stderr. * common.opt (-fsched-verbose): Set default value to 1. * invoke.texi (-fsched-verbose): Update the option's description.
OK for the trunk. jeff
