Reviewed-by: Connor Abbott
FWIW, in this area, another place where we unnecessarily introduce
dependencies between instructions is when multiple instructions write
to different parts of a virtual register, for example when setting up
message headers. Instead of tracking dependencies per-vgrf, we
On Mon, Feb 8, 2016 at 11:31 AM, Kenneth Graunke wrote:
> There are never render target reads, so there are no scheduling hazards.
>
> Giving the extra flexibility to the scheduler makes it possible to do
> FB writes as soon as their sources are available, reducing register
> pressure. It also ma
There are never render target reads, so there are no scheduling hazards.
Giving the extra flexibility to the scheduler makes it possible to do
FB writes as soon as their sources are available, reducing register
pressure. It also makes it possible to do the payload setup for more
than one FB write
