On Fri, Sep 19, 2014 at 1:10 PM, Jason Ekstrand <ja...@jlekstrand.net> wrote: > The original vgrf splitting code was written assuming that with the > assumption that vgrfs came in two types: those that can be split into > single registers and those that can't be split at all It was very > conservative and bailed as soon as more than one element of a register was > read or written. This won't work once we start allowing a regular MOV or > ADD operation to operate on multiple registers. This rewrite allows for > the case where a vgrf of size 5 may appropreately be split in to one > register of size 1 and two registers of size 2.
Having read the later series I now understand why we need to improve this pass. I haven't followed all of the logic, but I trust it works as expected if you've successfully tested a 41 patch series on top of it. :) That's at least good enough for an Acked-by: Matt Turner <matts...@gmail.com> _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
