> In any case, this change causes a ton of conformance failures. Several
> piglit tests in the "general" category also fail.

Yes, sorry, I actually run piglit, but twice on the same binary...

The problem was that last_tile_addr must be invalidated on any change
including flushes.
This was automatic before since we stored it at last_tile->addr, but
now needs to be done explicitly.

I posted a new version that should actually not have regressions on piglit.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to