> If it were not approved yet by an insn scheduler maintainer, it is ok for
> me. As Uros wrote that he rubberstamps the patch if a scheduler maintainer
> approves it, so you can commit it into the mainline.
Checked in: http://gcc.gnu.org/ml/gcc-cvs/2012-10/msg00965.html
K
On 10/23/2012 07:38 AM, Yuri Rumyantsev wrote:
Hi All,
This fix is aimed to remove stability issues with using pre-reload
scheduler for x86 targets caused by cross-block motion of function
arguments passed in likely-spilled HW registers. We found one more
issue in a process of more detail testin
On Tue, Oct 23, 2012 at 1:38 PM, Yuri Rumyantsev wrote:
> This fix is aimed to remove stability issues with using pre-reload
> scheduler for x86 targets caused by cross-block motion of function
> arguments passed in likely-spilled HW registers. We found one more
> issue in a process of more detai
Hi All,
This fix is aimed to remove stability issues with using pre-reload
scheduler for x86 targets caused by cross-block motion of function
arguments passed in likely-spilled HW registers. We found one more
issue in a process of more detail testing pre-reload scheduler for all
x86 platforms.
Th
