On Tue 12 Sep 2017, Jason Ekstrand wrote:
> The old code made a new miptree that referenced the same BO as the
> renderbuffer and just trusted in the memory aliasing to work. There are
> only two ways in which the new miptree is liable to differ from the one
> in the renderbuffer and neither of
Jason Ekstrand writes:
> The old code made a new miptree that referenced the same BO as the
> renderbuffer and just trusted in the memory aliasing to work. There are
> only two ways in which the new miptree is liable to differ from the one
> in the renderbuffer and neither
On Tue, Sep 12, 2017 at 04:23:04PM -0700, Jason Ekstrand wrote:
> The old code made a new miptree that referenced the same BO as the
> renderbuffer and just trusted in the memory aliasing to work. There are
> only two ways in which the new miptree is liable to differ from the one
> in the
The old code made a new miptree that referenced the same BO as the
renderbuffer and just trusted in the memory aliasing to work. There are
only two ways in which the new miptree is liable to differ from the one
in the renderbuffer and neither of them matter:
1) It may have a different target.