[Bug 77312] wine's d3d8/9 visual tests fail on i965

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 26 09:51:51 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=77312

--- Comment #8 from asimiklit <andrey.simiklit at gmail.com> ---
(In reply to andrii simiklit from comment #7)
> I made a mistake, this isn't a mesa issue.
> According to ARB_framebuffer_object spec:
> 
>   "- If the attachment sizes are not all identical, rendering will be
>    limited to the largest area that can fit in all of the
>    attachments (i.e. an intersection of rectangles having a lower
>    left of (0,0) and an upper right of (width,height) for each
>    attachment)
> 
>    - If the attachment sizes are not all identical, the values of
>    pixels outside the common intersection area after rendering are
>    undefined."
> 
> So this is rather a wine issue.
> ************************
> *   depth              *
> *                      *
> ***********            *
> * color   *            *
> *         *            *
> *         *            *
> ************************
> Because it does not expect that depth buffer will be
> modified outside the scissors area which is equal
> to intersection area.
> 
> But Mesa feels free to do everything with pixels(depth)
> outside the intersection area even to clean them.
> 
> Gallium behaves here in another way it just leaves
> a depth buffer outside the intersection untouched.

Based on opengl calls the original wine test makes the following steps:
1. creates a fbo (FA)
2. creates a depth buffer (DA) with size 640x480
3. creates a color buffer (CA) with the same size 640x480
4. attaches (CA) and (DA) to (FA)
5. calls a glClear  with depth 1.0 and blue color using (FA)
6. creates another fbo (FB)
7. creates a color buffer (CB) with size 320x240
8. attaches (CB) and (DA) to (FB)
9. setups a scissors area for 320x240
10. calls a glClear with depth 0.0 and white color using (FB)

Test expects that the depth outside 320x240 area
is not modified and there is still 1.0 but according
to spec which was mentioned above this is undefined behavior.

I suggest to close this issue as a not mesa issue.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20190326/e64fc79a/attachment-0001.html>


More information about the intel-3d-bugs mailing list