On 11 June 2014 10:48, Zack Rusin <[email protected]> wrote:
> To be honest I still don't like it. While the tgsi_exec specific paths in 
> draw_gs don't matter to me and can be as ugly as they need to be, they can't 
> be polluting the draw_pt_emit code, in other words the primitive_lengths 
> can't be bogus at that point - prim_info can't lie about the amount of data 
> that it's holding.

Thanks for following me on this journey! I think I got it now,
tgsi_exec wasn't bounding to the max output vertices, and causing
subsequent fallout.

I'll send that patch next!

Dave.
_______________________________________________
mesa-dev mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

Reply via email to