[Bug 108088] glBlitFramebuffer issue with max possible buffer sizes

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Feb 6 10:26:57 UTC 2019


--- Comment #1 from Sergii Romantsov <sergii.romantsov at globallogic.com> ---
Assume that a size of framebuffer is 160*160
We have a read-buffer and write-buffer.
In general: reading of pixels of any region-size and writing them into
region-size that greater or equal to 160 should give us the same results (whole
area of write-buffer should be filled by color of read-buffer). That is
satisfied except we are using some big pixel-values (dstX1, dstY1) starting
from 0x7ffffff.
I haven't found any restrictions in minimum/maximum values for parameters
(dstX0, dstY0) and (dstX1, dstY1), they are integers so looks like they could
be any valid integer.

Test shows that for big dest-region a draw performed incorrectly.
Correct blit of 160*160 region to dest (0xffffff, 0xffffff):
Incorrect blit of 160*160 region to dest (0x7fffffff, 0x7fffffff):
Incorrect blit of INT_MAX*INT_MAX region to dest (INT_MAX, INT_MAX):

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

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