On Fri, Sep 19, 2014 at 1:10 PM, Jason Ekstrand 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
On Fri, Sep 19, 2014 at 5:31 PM, Matt Turner wrote:
> On Fri, Sep 19, 2014 at 1:10 PM, Jason Ekstrand
> 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
>
> s/ with the assumption that//
>
> >
On Fri, Sep 19, 2014 at 1:10 PM, Jason Ekstrand 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
s/ with the assumption that//
> single registers and those that can't be split at all
Period
> It
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. Th