https://bugs.freedesktop.org/show_bug.cgi?id=35257 --- Comment #6 from Ionut Biru <biru.ionut@xxxxxxxxx> 2011-03-14 14:14:05 PDT --- @Ian (In reply to comment #5) > (In reply to comment #4) > > Like Marek said, this isn't a bug it is a hardware limitation. The only way > > this could work is with changes to Gnome Shell, so you should contact the Gnome > > Shell developers, although they might tell your hardware is unsupported. > my problem was fixed by gnome-shell developers by reducing the number of shader. http://git.gnome.org/browse/gnome-shell/commit/?id=43cf60f5636e7883bd5012e4c89ed5d57e28200c > Since we know there's a lot of work still to be done in the compiler's higher > level optimization passes, I always feel like this is a bit of a cop out > answer. The TGSI input is 125 instructions, and it looks like a nightmare of > lowered if-statements. There are way more CMP/SEQ/MUL sequences than any > program should generate. Unsurprisingly, the driver chokes on it. I'm sure > the i915 driver, which has limitations similar to r300, would choke even worse. > > Comparing the GLSL to the generated TGSI might reveal some high-level > optimization opportunities that we're missing. It may also help us give some > suggestions to the gnome-shell folks to make the shader more friendly to older > hardware. There are, after all, a lot of i915s and r300s out there. > > Just for giggles, could we get the output of MESA_GLSL=dump too? Use the same > procedure as for RADEON_DEBUG=fp. sure. i would do it -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
