Paul Berry stereotype...@gmail.com writes:
Previous to this patch, the _mesa_{Begin,Resume}TransformFeedback
functions were using ctx-Shader.CurrentProgram[MESA_SHADER_VERTEX]
I see that this commit was nominated for the stable branch when it was
committed.
However, it appears to depend at
On 28 January 2014 13:15, Carl Worth cwo...@cworth.org wrote:
Paul Berry stereotype...@gmail.com writes:
Previous to this patch, the _mesa_{Begin,Resume}TransformFeedback
functions were using ctx-Shader.CurrentProgram[MESA_SHADER_VERTEX]
I see that this commit was nominated for the stable
On 01/28/2014 01:26 PM, Paul Berry wrote:
On 28 January 2014 13:15, Carl Worth cwo...@cworth.org
mailto:cwo...@cworth.org wrote:
Paul Berry stereotype...@gmail.com
mailto:stereotype...@gmail.com writes:
Previous to this patch, the _mesa_{Begin,Resume}TransformFeedback
Previous to this patch, the _mesa_{Begin,Resume}TransformFeedback
functions were using ctx-Shader.CurrentProgram[MESA_SHADER_VERTEX] to
find the program that would be the source of transform feedback data.
This isn't correct--if there's a geometry shader present it should be
On 01/22/2014 06:07 AM, Paul Berry wrote:
Previous to this patch, the _mesa_{Begin,Resume}TransformFeedback
functions were using ctx-Shader.CurrentProgram[MESA_SHADER_VERTEX] to
find the program that would be the source of transform feedback data.
This isn't correct--if there's a geometry
On 22 January 2014 08:20, Kenneth Graunke kenn...@whitecape.org wrote:
On 01/22/2014 06:07 AM, Paul Berry wrote:
@@ -376,25 +376,48 @@ _mesa_compute_max_transform_feedback_vertices(
**/
+/**
+ * Figure out which stage of the pipeline is the source of transform
feedback
+ * data
