Sebastien Caty wrote:
On March 3, 2013 12:14:54 AM Vadim Girlin wrote:
On 03/02/2013 10:06 AM, Sebastien Caty wrote:
On March 1, 2013 06:24:01 PM Matt Turner wrote:
On Fri, Mar 1, 2013 at 5:15 PM, Sebastien Caty <sc...@dcinformatique.com>
wrote:
Trying to dig more and found out which shader is causing trouble but I
haven't found out how to run a specific test with piglit. Documentation
isn't to friendly...Id appreciate some help with this.
If you click the test {pass,fail,crash} in the generated html summary
it will contain the command used to run the test.
Doh! Thanks that will do. All the piglit regression I had found so far
pass
when I run them alone, one by one.
Went back to Serious Sam 3 to isolate a shader that's causing problems.
Found one, shader 35. I get several errors like this :
error at : DOT4 __, t113@R14.x, t114F@R125.x
: expected operand value t113@R14.x, gpr contains R11.x.3||FP@R14.x
error at : DOT4 __, t85@R14.x, t86F@R124.x
: expected operand value t85@R14.x, gpr contains R11.x.3||FP@R14.x
error at : DOT4 __, t87@R13.y, t88F@R124.y
: expected operand value t87@R13.y, gpr contains R12.x.5||FP@R13.y
I've pushed the fix for this issue.
Confirmed and it works like a charm. No errors, no graphic annomalies and a
far better frame rate with Serious Sam 3. I'll try some more piglit run and
other games but so far so good on RV790 hardware.
Things also better for me with rv790 testing with nexuiz, xonotic and etqw.
The one exception is vdpau hardware mpeg2 decode using llvm, this still
locks GPU, with R600_LLVM=0 it now renders correctly without issue.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
