[Bug 65416] r300g does not eliminate unread varyings

2013-07-13 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=65416 Marek Ol??k changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 65416] r300g does not eliminate unread varyings

2013-07-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=65416 Marek Olšák changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 65416] r300g does not eliminate unread varyings

2013-06-13 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #6 from Stefan D?singer --- I guess that's ok for wined3d's purposes. We don't use either extension right now, and if we ever use one of them we'll probably go with the ARB one anyway. -- You are receiving this mail because: You are

[Bug 65416] r300g does not eliminate unread varyings

2013-06-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #6 from Stefan Dösinger --- I guess that's ok for wined3d's purposes. We don't use either extension right now, and if we ever use one of them we'll probably go with the ARB one anyway. -- You are receiving this mail because: You are

[Bug 65416] r300g does not eliminate unread varyings

2013-06-12 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #5 from Marek Ol??k --- I have implemented it, but there is a problem. If I enable the optimization, EXT_separate_shader_objects must be disabled. Is it okay with you? This is a valid sequence with EXT_sso: glUseProgram(prog_with_vs_

[Bug 65416] r300g does not eliminate unread varyings

2013-06-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #5 from Marek Olšák --- I have implemented it, but there is a problem. If I enable the optimization, EXT_separate_shader_objects must be disabled. Is it okay with you? This is a valid sequence with EXT_sso: glUseProgram(prog_with_vs_

[Bug 65416] r300g does not eliminate unread varyings

2013-06-06 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #4 from Stefan D?singer --- Cool, thanks! -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL:

[Bug 65416] r300g does not eliminate unread varyings

2013-06-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #4 from Stefan Dösinger --- Cool, thanks! -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.

[Bug 65416] r300g does not eliminate unread varyings

2013-06-06 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #3 from Marek Ol??k --- I think the GLSL compiler only eliminates unused user-defined varyings, unused legacy varyings are not eliminated. I'm taking this task. -- You are receiving this mail because: You are the assignee for the bu

[Bug 65416] r300g does not eliminate unread varyings

2013-06-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #3 from Marek Olšák --- I think the GLSL compiler only eliminates unused user-defined varyings, unused legacy varyings are not eliminated. I'm taking this task. -- You are receiving this mail because: You are the assignee for the bu

[Bug 65416] r300g does not eliminate unread varyings

2013-06-05 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #2 from Alex Deucher --- Couldn't this be done in a device independent manner in mesa when linking shaders? Drop outputs if there is no matching input in the subsequent shader stage? -- You are receiving this mail because: You are

[Bug 65416] r300g does not eliminate unread varyings

2013-06-05 Thread bugzilla-dae...@freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #1 from Stefan D?singer --- Fwiw, I don't know if r600g is affected. The HW has enough varyings to run the unoptimized shaders, and the applications affected by this performance wise are CPU limited on my r600g system. Wine has some

[Bug 65416] r300g does not eliminate unread varyings

2013-06-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #2 from Alex Deucher --- Couldn't this be done in a device independent manner in mesa when linking shaders? Drop outputs if there is no matching input in the subsequent shader stage? -- You are receiving this mail because: You are

[Bug 65416] r300g does not eliminate unread varyings

2013-06-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=65416 --- Comment #1 from Stefan Dösinger --- Fwiw, I don't know if r600g is affected. The HW has enough varyings to run the unoptimized shaders, and the applications affected by this performance wise are CPU limited on my r600g system. Wine has some