On Wed, Oct 18, 2017 at 4:59 PM, Kenneth Graunke wrote:
> Commit a73116ecc60414ade89802150b tried to make add_barrier_deps()
> walk to the next barrier, and stop. To accomplish that, it added an
> is_barrier flag. Unfortunately, this only works half of the time.
>
> The issue is that add_barrier
typo in subject "is_barier" -> "is_barrier"
Quoting Kenneth Graunke (2017-10-18 16:59:12)
> Commit a73116ecc60414ade89802150b tried to make add_barrier_deps()
> walk to the next barrier, and stop. To accomplish that, it added an
> is_barrier flag. Unfortunately, this only works half of the time.
Commit a73116ecc60414ade89802150b tried to make add_barrier_deps()
walk to the next barrier, and stop. To accomplish that, it added an
is_barrier flag. Unfortunately, this only works half of the time.
The issue is that add_barrier_deps() walks both backward (to the
previous barrier), and forward
