Bug 62920 - [softpipe] piglit getteximage-targets S3TC CUBE_ARRAY regression
Summary: [softpipe] piglit getteximage-targets S3TC CUBE_ARRAY regression
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-03-30 01:25 UTC by Vinson Lee
Modified: 2014-01-01 04:59 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Vinson Lee 2013-03-30 01:25:15 UTC 
mesa: c34bbe110d1e562b1594a9a4f2e83a2ab5630036 (master)

$ ./bin/getteximage-targets S3TC CUBE_ARRAY -auto
Testing S3TC.
Testing GL_TEXTURE_CUBE_MAP_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 Vinson Lee 2013-07-04 20:54:04 UTC 
mesa: f3bbf65929e395360e5565d08d015977dd5b79fa (master)

This regression is still present with latest master.
Comment 2 Vinson Lee 2014-01-01 04:59:47 UTC 
mesa: 5a51c1b01a16d3256f9769a76d8293fea5853b1f (master)

piglit getteximage-targets S3TC CUBE_ARRAY passes on softpipe 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.