Bug 62922 - [softpipe] piglit arb_seamless_cubemap regression
Summary: [softpipe] piglit arb_seamless_cubemap regression
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (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 03:49 UTC by Vinson Lee
Modified: 2013-07-04 20:51 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Vinson Lee 2013-03-30 03:49:27 UTC
mesa: c34bbe110d1e562b1594a9a4f2e83a2ab5630036 (master)

$ ./bin/arb_seamless_cubemap -auto
Probe at (80,20)
  Expected: 0.500000 0.000000 0.500000
  Observed: 1.000000 0.000000 0.000000
Probe at (110,20)
  Expected: 0.500000 0.000000 0.500000
  Observed: 0.000000 0.000000 1.000000
PIGLIT: {'result': 'fail' }

6a3d77e13dbae17000e35ce16023532200e68d09 is the first bad commit
commit 6a3d77e13dbae17000e35ce16023532200e68d09
Author: José Fonseca <jfonseca@vmware.com>
Date:   Thu Mar 14 11:44:21 2013 +0000

    softpipe: Shrink context size.
    
    - each softpipe_tex_tile_cache 50*64*64*4*4 = 3,276,800 bytes
    - each softpipe_context has 3*32 softpipe_tex_tile_cache, i.e, each softpipe
      context is 314,572,800 bytes, i.e, 300MB
    
    That is, in a 32bits process (around 3GB virtual memory max), we can
    only fit 10 contexts.
    
    This change is a short-term hack to shrink the context size.  Longer
    term we'll need to change how the texture cache works.
    
    Reviewed-by: Brian Paul <brianp@vmware.com>

:040000 040000 64ff15d9847673c6545754f29cba7bcbdd4be457 727f8e3f8b282c58978ca3c4a9d637ebc4f7f21e M	src
bisect run success
Comment 1 Vinson Lee 2013-07-04 20:51:09 UTC
mesa: f3bbf65929e395360e5565d08d015977dd5b79fa (master)

piglit arb_seamless_cubemap now passes on softpipe with latest master.


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.