On Mon, Apr 4, 2011 at 9:34 AM, Vladimir Makarov <vmaka...@redhat.com> wrote:
> On 04/04/2011 11:07 AM, Bernd Schmidt wrote:
>>
>> I eventually managed to reproduce it, and even figured out what I'd
>> stupidly been doing wrong with my bootstraps which caused me not to see
>> this.
>>
>> There were a few places where last_scheduled_insn wasn't just examined
>> on its own, but code wanted to walk backwards and forwards from it. This
>> patch adapts them. I've also included Steven's patch from the bugzilla.
>>
>> Bootstrapped on i686-linux. Also tested, but I need to rerun those since
>> there were other changes in the tree which were causing some failures.
>> I've also built a powerpc-linux cross compiler, and compiled my set of
>> examples with "-fsched-stalled-insns-dep=4 -msched-costly-dep=all
>> -fsched-stalled-insns", with both patches included and with both patches
>> removed, and found no code generation differences. I also did a run
>> using "-fdbg-cnt=sched_insn:20", which exposed a preexisting bug in
>> schedule_block (avoiding a requeue for the first insn, but not placing
>> it back in the ready list).
>>
>> Ok after retest?
>>
> Ok, thanks.
>
>

I bootstrapped it on Linux/x86-64 and checked it in.

Thanks.

-- 
H.J.

Reply via email to