[Mesa-dev] Mesa (master): mesa/st: Fill in native program limits.
Brian Paul
brianp at vmware.com
Thu May 6 09:23:04 PDT 2010
Xavier Chantry wrote:
>> On Tue, 2010-05-04 at 07:41 -0700, Jose Fonseca wrote:
>>> Module: Mesa
>>> Branch: master
>>> Commit: dad962bafe8ffd7fdb35c28cfb8bbd5a297c8083
>>> URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=dad962bafe8ffd7fdb35c28cfb8bbd5a297c8083
>>>
>>> Author: José Fonseca <jfonseca at vmware.com>
>>> Date: Tue May 4 15:41:19 2010 +0100
>>>
>>> mesa/st: Fill in native program limits.
>>>
>>> In the lack of more fine grained capabilities in Gallium, assume that if
>>> the pipe driver supports GLSL then native limits match Mesa software
>>> limits.
>>> (cherry picked from commit 40a90cd11234a09c2477f5c9984dd6d9fac3f52c)
>>>
>
> This also broke shaders/fp-long-alu on nv50g , do drivers need to be
> adjusted after that commit ?
>
> Max (native) ALU instructions: 16384
> Testing: alu_depth = 1
> Testing: alu_depth = 2
> Testing: alu_depth = 3
> Testing: alu_depth = 4
> Testing: alu_depth = 5
> Testing: alu_depth = 6
> Testing: alu_depth = 7
> Testing: alu_depth = 8
> Testing: alu_depth = 11
> Testing: alu_depth = 17
> Testing: alu_depth = 29
> Testing: alu_depth = 53
> Testing: alu_depth = 101
> Testing: alu_depth = 197
> Testing: alu_depth = 389
> Testing: alu_depth = 773
> Testing: alu_depth = 1541
> Testing: alu_depth = 3077
> Probe at (16,16)
> Expected: 0.312500 0.000000 0.750000 0.000000
> Observed: 0.000000 0.000000 0.000000 0.000000
> Failure in alu_depth = 3077
> PIGLIT: {'result': 'fail' }
As I wrote in bug report
https://bugs.freedesktop.org/show_bug.cgi?id=27989, there's something
funny with that test. Even with NVIDIA's driver, it sometimes passes
and sometimes fails from one run to another. I'm hoping to get to
that today.
-Brian
More information about the mesa-dev
mailing list