History log of /external/deqp/modules/gles2/functional/es2fFboRenderTest.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
ba28bddbe8d98a056ce54a7278b673222e32e628 12-Jan-2016 Mika Isojärvi <misojarvi@google.com> Increase GLES2 fbo comparison threshold to 0.03 am: 3f450ecc23 am: c509a7f078
am: 837a58e9b7

* commit '837a58e9b7161576b567b93bf203d32db5f15054':
Increase GLES2 fbo comparison threshold to 0.03
3f450ecc233b3f3b38e61b4a37c76600a90f5c26 11-Jan-2016 Mika Isojärvi <misojarvi@google.com> Increase GLES2 fbo comparison threshold to 0.03

Bug: 26422231
Change-Id: I8c7304bbf479e4e848974fc913c564f7378f9c1d
/external/deqp/modules/gles2/functional/es2fFboRenderTest.cpp
3dae1ed6c5dfe64fc4d487df2f926aff4162c442 06-Jun-2015 Mika Isojärvi <misojarvi@google.com> am c255b711: am aa143d2e: Always read pixels from fbo in fbo recreate.no_rebind tests

* commit 'c255b711bf345603beeef9ff5d425b65c7586799':
Always read pixels from fbo in fbo recreate.no_rebind tests
aa143d2e95600cb90e9fe423328e23bcfd267787 04-Jun-2015 Mika Isojärvi <misojarvi@google.com> Always read pixels from fbo in fbo recreate.no_rebind tests

Instead of rendering texture to screen and verifying result, read texture
attachments pixels using fbo. This changes texture tests to work same way as
renderbuffer tests work and avoids triggering some bugs in reference context.

Bug: 21526068
Change-Id: I3009703a947e1a11327cf8f49585dce2a3270a04
/external/deqp/modules/gles2/functional/es2fFboRenderTest.cpp
1cc61b7d03cad727bbddd00cea8d78f4f6cc9047 30-May-2015 Jarkko Pöyry <jpoyry@google.com> Fix clang string literal conversion warnings.

- Add DE_FATAL(MSG) macro to replace DE_ASSERT(!"MSG") pattern used in
code.

Bug: 21161908
Change-Id: I96414b9ecfbb953b1c5236753c21c5c2d08d3f59
/external/deqp/modules/gles2/functional/es2fFboRenderTest.cpp
8cc4650120c587d5c00ad08cd1e0d81e804d7578 04-Nov-2014 Pyry Haulos <phaulos@google.com> Create repro cases for FBO clear bug

Color clears typically enjoy special handling in drivers, especially on
tile-based renderers, where fullscreen clears are typically just state
that gets processed when tile is initialized. That requires further
special handling when the clear is the only command issued to a render
target.

Sure enough there appears to be some devices where following doesn't
work as expected:

Repeat N times:
Clear FBO A with some iteration-specific color
Bind FBO B
Sample from FBO A

The result is that sampling might not return color of that iteration,
but instead for example the claer color of first, or previous iteration.

These tests attempt to reproduce that implementation bug.

Bug: 18169662
Change-Id: I869138c5108d66fdf0cf497f730b2b3518d1686d
/external/deqp/modules/gles2/functional/es2fFboRenderTest.cpp
3c827367444ee418f129b2c238299f49d3264554 02-Sep-2014 Jarkko Poyry <jpoyry@google.com> Import dEQP.

Import drawElements Quality Program from an internal repository.

Bug: 17388917
Change-Id: Ic109fe4a57e31b2a816113d90fbdf51a43e7abeb
/external/deqp/modules/gles2/functional/es2fFboRenderTest.cpp