<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - glBlitFramebuffer issue with max possible buffer sizes" href="https://bugs.freedesktop.org/show_bug.cgi?id=108088#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - glBlitFramebuffer issue with max possible buffer sizes" href="https://bugs.freedesktop.org/show_bug.cgi?id=108088">bug 108088</a> from <a class="email" href="mailto:sergii.romantsov@globallogic.com" title="Sergii Romantsov <sergii.romantsov@globallogic.com>"> Sergii Romantsov</a> <pre>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): read160_to0xffffff.png Incorrect blit of 160*160 region to dest (0x7fffffff, 0x7fffffff): read160_to0x7fffffff.png Incorrect blit of INT_MAX*INT_MAX region to dest (INT_MAX, INT_MAX): readIntMax_toIntMax.png</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>