Bug 62919 - piglit getteximage-targets S3TC 2D_ARRAY regression
Summary: piglit getteximage-targets S3TC 2D_ARRAY regression
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-03-30 01:04 UTC by Vinson Lee
Modified: 2014-03-02 03:30 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Vinson Lee 2013-03-30 01:04:28 UTC 
mesa: c34bbe110d1e562b1594a9a4f2e83a2ab5630036 (master)

$ ./bin/getteximage-targets S3TC 2D_ARRAY -auto
Testing S3TC.
Testing GL_TEXTURE_2D_ARRAY
GetTexImage() returns incorrect data in byte 0 for layer 1
    corresponding to (0,0), channel 0
    expected: 8
    got: 123
PIGLIT: {'result': 'fail' }

3e10ab6b22341c06a9352b1e029b923f4d8405b9 is the first bad commit
commit 3e10ab6b22341c06a9352b1e029b923f4d8405b9
Author: Marek Olšák <maraeo@gmail.com>
Date:   Thu Mar 14 17:18:43 2013 +0100

    gallium,st/mesa: don't use blit-based transfers with software rasterizers
    
    The blit-based paths for TexImage, GetTexImage, and ReadPixels aren't very
    fast with software rasterizer. Now Gallium drivers have the ability to turn
    them off.
    
    Reviewed-by: Brian Paul <brianp@vmware.com>
    Tested-by: Brian Paul <brianp@vmware.com>

:040000 040000 73beb3047ac1c1f7fd5dd78f8ff219aed4970165 7af39a7d024dd235ed553fc91f231682d90bcb85 M	src
bisect run success
Comment 1 Marek Olšák 2013-03-30 01:45:18 UTC 
The commit turned off the decompression with a blit for software rasterizers, so we're hitting a code path we never used for years. I think this uncovers an existing old bug instead of introducing a new one.
Comment 2 Vinson Lee 2014-03-02 03:30:30 UTC 
mesa: fc25956badb8e1932cc19d8c97b4be16e92dfc65 (master 10.2.0-devel)

getteximage-targets S3TC 2D_ARRAY passes on swrast now.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.