Fixed warning about strange position of be_Keeps in the schedule.
The warning arises from the removal of the barrier before peephole optimization. An operand of the barrier is now kept by a new be_Keep which is scheduled directly after the operand.
Please register or sign in to comment