[Mesa-dev] [Bug 78842] New: [swrast] piglit fcc-read-after-clear copy rb regression
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat May 17 16:09:15 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=78842
Priority: medium
Bug ID: 78842
Keywords: regression
CC: chrisf at ijw.co.nz, eric at anholt.net,
kenneth at whitecape.org
Assignee: mesa-dev at lists.freedesktop.org
Summary: [swrast] piglit fcc-read-after-clear copy rb
regression
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: vlee at freedesktop.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Mesa core
Product: Mesa
mesa: 5646319f25c7880b3706bb7590e24c84fd8de0fc (master 10.3.0-devel)
$ ./bin/fcc-read-after-clear copy rb -auto
Probe color at (0,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 0.000000 0.000000
PIGLIT: {'result': 'fail' }
bd44ac8b5ca08016bb064b37edaec95eccfdbcd5 is the first bad commit
commit bd44ac8b5ca08016bb064b37edaec95eccfdbcd5
Author: Kenneth Graunke <kenneth at whitecape.org>
Date: Sun May 11 17:20:08 2014 -0700
i965: Don't _swrast_BlitFramebuffer when doing CopyTexSubImage.
The point of copytexsubimage_using_blit_framebuffer is to use a hardware
accelerated BlitFramebuffer path. If that fails, we shouldn't do a
swrast blit---we should try our CTSI fallback code.
This is especially important for i965 and GLES, where we don't even
create a swrast context.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=77705
Signed-off-by: Kenneth Graunke <kenneth at whitecape.org>
Reviewed-by: Eric Anholt <eric at anholt.net>
Reviewed-by: Chris Forbes <chrisf at ijw.co.nz>
Cc: "10.2" <mesa-stable at lists.freedesktop.org>
:040000 040000 313ba4b4dcbf69457b565f9ce2988355431d461f
128c89746f13726404560571fe5d8a7a69df1d0b M src
bisect run success
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20140517/0f5fc176/attachment.html>
More information about the mesa-dev
mailing list