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
Please commit if it is OK for trunk.
Thanks,
Nikolai
On 10/22/2015 06:38 PM, 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
On 11/05/2015 09:11 AM, Nikolai Bozhenov wrote:
Please commit if it is OK for trunk.
Hmm, do you have a copyright assignment on file?
Bernd
On 11/05/2015 12:26 PM, Bernd Schmidt wrote:
On 11/05/2015 09:11 AM, Nikolai Bozhenov wrote:
Please commit if it is OK for trunk.
Hmm, do you have a copyright assignment on file?
Yes I do have a copyright assignment for all past and future changes
to GCC (RT:828836).
Thanks,
Nikolai
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
On 10/22/2015 05:38 PM, Nikolai Bozhenov wrote:
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
On 10/22/2015 06:56 PM, Bernd Schmidt wrote:
On 10/22/2015 05:38 PM, Nikolai Bozhenov wrote:
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
