http://bugs.freedesktop.org/show_bug.cgi?id=26933
--- Comment #4 from Török Edwin <edwinto...@gmail.com> 2010-03-08 04:22:27 PST --- (In reply to comment #3) > > These failures are all in common Mesa code and are not specific to r600. > There > are already bugs reported for most, if not all, of them. Search bugzilla for > "glslparser", and it will turn up quite a few. > I compared my r600 piglit results with swrast (LIBGL_ALWAYS_SOFTWARE=1), and here are the tests that failed in r600, but passed with swrast (there are tests that fail with swrast but pass with r600, or are skipped, I don't list those below): fbo/fbo-copyteximage fbo/fbo-readpixels general/linestipple glean/fbo glean/logicOp glean/paths glean/pointAtten shaders/fp-indirections2 shaders/glsl-bug-22603 shaders/glsl-deriv-varyings shaders/glsl-vs-arrays shaders/glsl-vs-mov-after-deref shaders/vp-address-01 shaders/vp-bad-program shaders/vpfp-generic/vp-arl-constant-array-huge-offset-neg shaders/vpfp-generic/vp-arl-neg-array texturing/depth-tex-modes texturing/texdepth texturing/tfp I also compared with the r300/r500 on the piglit site, and here are the tests that passed for those, but not for r600: glean/logicOp glean/pointAtten shaders/vp-bad-program (this one segfaults!) texturing/texdepth texturing/tfp Should I open bugreports for these, and make them block this one? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
